Authentication

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