SSO

Single sign-on (SSO) lets people sign in to Buttons with the account they already have at your organization's identity provider, instead of a separate Buttons password. Buttons supports Google, Microsoft Entra ID, GitHub, Okta, any OpenID Connect (OIDC) provider, and LDAP or Active Directory. SSO needs an Enterprise license.

These pages are for administrators who connect Buttons to an identity provider. Start with getting started, then follow the page for your provider, and finish by mapping the provider's groups or claims to Buttons roles.

Get started with SSO

Configure an identity provider, test single sign-on, and keep local administrator access available.

Connect a generic OIDC provider

Register Buttons with an OpenID Connect provider, configure the connection, and test sign-in and access.

Connect LDAP or Active Directory

Configure directory authentication, map groups to roles, and test sign-in and access.

Map identity claims to roles

How role mappings turn identity provider claims into Buttons roles, and what happens on every sign-in, manual override or removed connection.

Was this helpful?

0 of 0 users found this page helpful

Loading...

SSO

View as Markdown