コンテンツにスキップ
Onetime SecretOnetime Secret - Docsdocs

Single Sign-On (SSO)

このコンテンツは、現在ご利用の言語ではまだ提供されていません。

Status: This page is a work in progress. SSO is part of our team-oriented capabilities. The interactive demos linked below are live today and walk through real authentication flows step by step.

What is SSO?

Section titled “What is SSO?”

Single Sign-On (SSO) lets your team access Onetime Secret using the accounts they already have with your identity provider (IdP) — such as Microsoft Entra ID, Okta, Auth0, Google, or Keycloak — instead of separate Onetime Secret credentials. Authentication and account lifecycle stay centralized in your IdP, which is where most organizations want them.

When to use SSO

Section titled “When to use SSO”
  • You want employees to sign in with their existing corporate accounts.
  • You need centralized control over who can access Onetime Secret.
  • You want to enforce your organization’s authentication policy (MFA, conditional access, deprovisioning) from one place.

Setup overview

Section titled “Setup overview”

A typical SSO integration follows the same shape regardless of provider:

  1. Register Onetime Secret as an application in your identity provider.
  2. Exchange the connection details (issuer/metadata, client credentials, or SAML assertion settings).
  3. Map identities so your IdP users resolve to the right access in Onetime Secret.
  4. Test the round trip and roll the integration out to your team.

A common pattern is to put a gateway in front of the application so the app itself only ever receives an already-authenticated request — “my app doesn’t touch SAML, the gateway does.”

Try it: interactive SSO demos

Section titled “Try it: interactive SSO demos”

We’ve built step-by-step, interactive visualizations of real SSO flows — every redirect, cookie, and token exchange — using Onetime Secret as the example application:

Section titled “Related features”

Questions or Need Support?

Section titled “Questions or Need Support?”

We’re here to help.