Set up single sign-on
Federate console access to Okta, Azure AD, or any OIDC provider.
Single sign-on lets your team reach the console through your identity provider instead of a Bidirection password. Owners and Admins only — the panel does not appear for anyone else.
Before you start#
You need two things:
- A domain you have proven is yours, with a DNS record. Open Settings · Domains, press Prove ownership on the domain, add the TXT record it shows with your DNS provider, and press Check. When it passes, the domain reads Active · owner proven. Single sign-on is the only place Bidirection asks for this proof — the widget runs on any domain you add, without it. See Add your domain.
- Your secret already in AWS Secrets Manager. Bidirection stores a reference, never the credential itself.
Configure it#
- Open Settings · Workspace and find the Single sign-on card.
- Choose your protocol — SAML 2.0 for enterprise IdPs like Okta or Azure AD, or OIDC for OpenID Connect providers.
Fill in the fields for that protocol:
For SAML 2.0:
Field Example IdP entity ID https://idp.acme.com/metadataIdP SSO URL https://idp.acme.com/ssoSigning certificate reference arn:aws:secretsmanager:…:saml-certFor OIDC:
Field Example Issuer https://idp.acme.comClient ID bidirection-consoleClient secret reference arn:aws:secretsmanager:…:oidc-secret- Tick Enable SSO for this workspace.
- Press Save SSO configuration.
When it is live, the card header shows Enabled.
After it is on#
Members still need a membership in the workspace — SSO controls how they authenticate, not whether they belong. Add them first on Settings · Team. See Invite your team.