24 docs tagged with "openid-connect"

Manage OAuth2/OIDC applications and clients in cidaas, including app settings, advanced configuration, and API references.

OAuth2/OIDC application types (client_type values), recommended flows, and configuration availability by type in cidaas.

cidaas is an OAuth 2.0 and OpenID Connect authorization server — authorization server basics, standard grants, tokens, and how to secure your apps.

After a user signs in with OpenID Connect, your application may need to periodically check if the user is still authenticated. While you can use prompt=none with the authorization endpoint for this purpose, the Check Session iFrame provides a more efficient, real-time solution.

cidaas can act as an OpenID Connect (OIDC) Identity Provider (IdP) for external applications.

Claim consent in cidaas — let users authorise the release of identity claims such as name, email or roles to an application before a token is issued.

Manage and customize communication templates to deliver consistent, branded messages to users across multiple channels.

Consents and consent groups in cidaas — straightforward organisation of consents in groups and versioning.

Protect cidaas integrations against CSRF and replay attacks — how the OAuth 2.0 state and OIDC nonce parameters work and how to implement them.

When a user logs out of your application, you need to properly end their session with cidaas to ensure they're logged out from all applications using the same cidaas instance. This guide explains how to implement logout using OpenID Connect specifications.

Identity providers in cidaas — connect SAML, OAuth 2.0, OpenID Connect, and LDAP/AD for enterprise and social SSO.

Integrating cidaas with your business is simple and can be done for the Admin and User Service portals.

cidaas supports LDAP (Lightweight Directory Access Protocol) and Active Directory for authentication and user synchronization. You can configure cidaas to act as an Identity Provider (IdP) or as a Service Provider (SP).

The cidaas login hosted page — learn how to set it up, add login providers, and connect the login success page that follows a successful sign-in.

cidaas supports OAuth2 and OpenID Connect (OIDC) for Single Sign-On (SSO) authentication. You can configure cidaas to act as an Identity Provider (IdP) or as a Service Provider (SP).

cidaas lets you get data from your customers each time they interact with your product instead of requesting their profile information all at once during registration.

Implementing the Pushed Authorization Request (PAR) Flow

Scope consent in cidaas — pause the authentication flow to obtain explicit user authorization for scopes such as email or profile.

Learn how scopes work in OAuth2/OIDC and how to configure and manage scopes and scope groups in cidaas.

Session management lets users stay signed in across applications and devices. This guide explains how sessions relate to OAuth 2.0 and OpenID Connect in cidaas, and points you to the right flows for validation, logout, and native-to-web handoff.

Validate cidaas tokens — check authenticity, expiry and audience of access, ID and refresh tokens, with a practical validation checklist.

Domain- and user-based redirection in cidaas — use webfinger to send users straight to their own identity provider, bring-your-own-identity style.

After an authentication, cidaas approves the correctness of provided information with a token. OAuth2 and OpenID Connect work with different tokens. Either way, cidaas will provide an access token based on OAuth2 standard. The token is built up as a JWT (JSON Web Token), which is essentially a base64-encoded JSON format. Optionally, in a user authentication, cidaas can also provide an ID token, which is based on OIDC standard and also built up as a JWT.

Today's competitive landscape calls for better security implementation for user accounts. With customers becoming more demanding and applications becoming critical, a seasoned and reliable CIMS helps manage both optimally.