Authentication
3 min
Overview
Authorization Sources allow third party Oauth2 identity management systems (such as: Okta, GitLab, Entra ID, Google) for user authentication in your tenant.
While OAuth2 is a standard specification, different implementations will vary. This page provides generalized instructions for configuring a third-party OAuth Source to be used for UI authentication. Specific fields and settings will differ depending on the selected driver (Google, Entra ID, Okta, etc.). Consult specific OAuth source documentation for information on particular options.
OIDC Application Benefits
The platform provides OIDC functionality to allow centralized identity management for multiple systems and/or tenants.
- Ability to establish your system as an identity provider (with or without an upstream provider such as Google, Entra ID, etc.)
- Same app/token in an upstream authorization provider can be used for multiple physical environments and tenants rather than creating a separate one for each
- Provides single sign-on (SSO) capabilities across all systems
- MSPs/providers can have central login linked back to their environment for all tenants
- OIDC delivers a standardized, widely supported protocol with built-in security features
- Less administrative burden for user/group management across systems/tenants
General Operational Flow:
- User attempts to log in to the UI
- The request is redirected to the identity provider system
- When there is a third-party provider configured, the request is redirected upstream as needed (e.g. Google Auth)
- Tokens containing user information are sent back to the initial system
- Tokens are verified and a user session is created