Authentication protocols
What is OIDC?
Also known as: OpenID Connect
OpenID Connect (OIDC) adds an identity layer to OAuth 2.0 so a client can verify an end user’s authentication and receive identity claims. It is one option for web and mobile sign-in; choosing between OIDC and SAML depends on the applications and identity provider.
More terms in Authentication protocols
- SAMLSAML 2.0 is an XML-based standard for exchanging authentication assertions between an identity provider and a service provider. It is used for enterprise single sign-on. Cremit Platform supports SAML 2.0 SSO; confirm metadata, attribute mapping and sign-in behavior when connecting a particular identity provider.
- SSOAuthentication scheme that lets a user log in once and access multiple applications without re-entering credentials. Typically implemented via SAML 2.0 or OIDC. In NHI context, SSO applies to human access into management tools; machine-to-machine auth uses service accounts, not SSO.
- SCIMSCIM is a standard HTTP protocol for provisioning and updating users and groups across identity systems. An identity provider can send a deactivation change to a connected application, but timing and actual access removal depend on the integration and the application’s session handling.
- OAuthOAuth 2.0 is an authorization framework for granting a client limited access to a resource without giving it the resource owner’s password. A token may represent a person’s delegated access or a client acting on its own behalf. Review the token’s issuer, scope, lifetime and owner before treating it as a non-human identity credential.
- JWTJSON Web Token (JWT) is a compact format for carrying claims between parties. A JWT may be signed or encrypted, and its format alone does not grant access. If a service accepts a JWT as a bearer credential, exposure may permit access until the token expires or the service rejects it.