The Jet Admin OpenID Connect integration lets your app authenticate users against any standards-based identity provider your organization already runs, driven by the same roles and permissions you already manage in Jet. Whether that provider is Okta, Azure AD, a custom identity service or something else entirely, the whole sign-in flow runs through OIDC, and access stays in sync with the provider's own groups and claims.

That covers what teams build with OpenID Connect first: internal tools that need to plug into whatever identity provider IT already standardized on, without a bespoke integration for each one. Because Jet maps claims from the ID token to app roles, a person's permissions update automatically as their provider-side group membership changes.

Key benefits

• Works with any OIDC provider. Connect once to a standards-based protocol instead of a specific vendor's API.
• Automatic role sync. Permissions update from the claims your identity provider sends on every login.
• Centralized offboarding. Removing someone at the identity provider removes their access to the app.
• Fewer passwords, less risk. No separate password to phish, forget or reuse.
• Standards-based security. Tokens are validated and refreshed automatically behind the scenes.

How to connect Jet Admin with OpenID Connect

1. In your identity provider, register a new OIDC application and note the client ID, client secret and issuer URL.
2. In Jet Admin, open your app's authentication settings and choose Custom OIDC as the sign-in method.
3. Enter the client ID, client secret and issuer URL from your provider.
4. Map the claims you want to use to roles inside your Jet app.
5. Test sign-in with a user in each claim group to confirm roles apply correctly.
6. Roll out the login link to your team.