Skip to main content
Use the Corbado Management Console to configure Connect and review passkey adoption, login errors and individual users. Your account must be invited and have access to the relevant project. Check the selected project before changing rollout rules or copying integration settings, especially when you have separate development and production projects.

​
Enterprise single sign-on

For enterprise customers, the Management Console supports SAML 2.0 SSO with Microsoft Entra ID, Okta or another SAML 2.0-compatible identity provider. Your organization can use its existing IdP to authenticate the team members who administer Connect. Contact your Corbado representative to configure enterprise SSO for your organization and invite the administrators who need access. Confirm the identity provider and the people who need console access as part of your deployment planning. On-premises Microsoft Active Directory requires a SAML identity provider, such as Active Directory Federation Services (AD FS). Active Directory Domain Services alone does not provide SAML SSO.

​
Console SSO and end-user authentication

Console SSO controls how your team signs in to Corbado’s administrative interface. Your application’s users authenticate through the Connect integration, with your backend verifying passkey results and creating sessions in your existing identity system. Continue to the Management Console overview for analytics, debugging and rollout tools.