Single sign-on with OneLogin
Learn how to setup single sign-on in the Dashboard with OneLogin.
Stripe supports Single Sign-On (SSO), allowing you to manage your team’s access and roles through your identity provider (IdP). This means your team can access Stripe without needing separate passwords. When SSO is configured, users (team members) are automatically redirected to your IdP for authentication when they sign in to Stripe.
Your IdP verifies if they have a valid role assignment to your Stripe accounts or organization, and generates a SAML assertion used by Stripe to assign the proper roles in the Stripe Dashboard. When your account requires SSO, you must update team roles through your Identity Provider (IdP) for security. Changes to a team member’s roles only appear in Stripe after they sign in to the Dashboard again using the updated SAML assertion.
Set up SSO
To integrate your Stripe account with your IdP, you’ll need to complete three steps:
- Prove ownership of the domains that your team will use to sign in to the Dashboard.
- Configure OneLogin to work with Stripe.
- Configure Stripe to work with OneLogin.
Proving Domain Ownership
A domain is the portion of an email address after the @ symbol (such as kavholm.). You must configure SSO for Stripe for each of your business’s email domains. To verify domain ownership:
- Go to Single sign-on (SSO) in the Stripe Dashboard, and click + New domain to view your account’s unique verification code.
stripe-verification=4242424242424242424242 - Add the verification code as a
TXTrecord to your Domain Name System (DNS) provider. - Return to the Stripe Dashboard, and click Save and verify. Depending on your DNS provider, it can take 24 hours or more to verify your domain.
- After successful verification, don’t delete the
TXTrecord from your DNS provider. If you delete it, you might lose access to the Dashboard because Stripe frequently checks the DNS records of your domain.
Multiple Stripe accounts support
If you’re configuring SSO for multiple Stripe accounts, you must create an organization to centrally configure SSO across all of your accounts. Alternatively, contact Stripe support to verify your domain across separate accounts with one shared verification code.
Configuring OneLogin
Avertissement
There isn’t an official Stripe SAML connector in OneLogin yet. The only available Stripe app is for password-based authentication. Don’t use the password-based authentication for SAML.
- Create a new application to represent the relationship between OneLogin and the Stripe Dashboard. To do so, go to the Applications page, and select Add App.
- Find the SAML Test Connector (IdP w/ attr w/ sign response) app.
- Select Save, and go to the Configuration section. Then, enter the following values:
- Audience:
https://dashboard.stripe. com/saml/metadata - Recipient:
https://dashboard.stripe. com/login/saml/consume - Consumer URL Validator:
https://dashboard.stripe. com/login/saml/consume - Consumer URL:
https://dashboard.stripe. com/login/saml/consume
- Audience:
- Select SSO on the side panel, and set the Signature Algorithm to
SHA-256. - Save your configuration changes by selecting Save.
Assign roles to your team
To authenticate a team member to Stripe and assign them roles, configure OneLogin to send the roles in the SAML assertions.
- Go to the Parameters section, and create a new Field
- Set the Field name to
Stripe-Role-. This identifies which account you sign in to. - Select Include in SAML assertion.
- Set the Field name to
- In the next form, select the Dashboard role you want your users to have by default. Select Macro, and input the desired default role in the field below

Stripe prend en charge les rôles suivants. Certains rôles ne sont disponibles que si votre compte utilise le produit Stripe applicable. Pour en savoir plus, consultez la rubrique Rôles utilisateur pris en charge par Stripe.
| Role | Value |
|---|---|
| Administrator | admin |
| Analyst | analyst |
| Cardholder | cardholder |
| Connect Onboarding Analyst | connect_ |
| Connect Risk Analyst | connect_ |
| Data Migration Specialist | data_ |
| Developer | developer |
| Dispute Analyst | dispute_ |
| Financial Connections Specialist | financial_ |
| IAM Admin | iam_ |
| Identity Analyst | identity_ |
| Identity View only | identity_ |
| Issuing Support Agent | issuing_ |
| Opal View only | opal_ |
| Sandbox Administrator | sandbox_ |
| Sandbox User | sandbox_ |
| Super Administrator | super_ |
| Support Associate | support_ |
| Support Communications | support_ |
| Support only | support_ |
| Support Specialist | support_ |
| Refund Analyst | refund_ |
| Tax Analyst | tax_ |
| Terminal Specialist | terminal_ |
| Topups only | topups_ |
| Top-up Specialist | topup_ |
| Transfer Analyst | transfer_ |
| View only | view_ |
Support for multiple Stripe accounts
Repeat the previous step and add a parameter for each additional Stripe account. Select Add parameter, use the current account’s token for the Field name and choose the role you want your users to have by default.
The list of account tokens can be found in the Accounts section of your Personal details settings.

- Go to the Users tab. Here, you can assign team members to your application. You can also configure which Roles a user obtains upon log in.
- Select the User you want to edit. Then, go to Applications on the side panel.
- In the next modal that opens, you can configure the roles that a user obtains when they log in. To use multiple roles, add a semicolon after each role. In the following example, the user obtains the
analystand thedeveloperrole when they sign in.

Configuring Stripe
Enter values from your identity provider
Next, configure your Stripe account to connect to your identity provider from the User authentication page.
To configure Stripe to connect to your identity provider you need:
- Issuer ID: An identifier of your identity provider.
- Identity provider URL: The URL of your identity provider that your team members are redirected to, so they can authenticate.
- Identity provider certificate: The X.509 certificate that your identity provider signs assertions with.
How to find these values in your identity provider
In OneLogin, you can find these values by navigating to the SSO tab of your application.
| Name of property in Stripe | Name of property in OneLogin |
|---|---|
| Issuer ID | Issuer URL |
| Identity provider URL | SAML 2.0 Endpoint (HTTP) |
| Identity provider certificate | X.509 certificate (click View Details) |

Test your configuration
Before saving your settings, a test runs to validate your SSO integration. After you click the Test button, a window opens in your browser that redirects to your identity provider to sign in. After you sign in, the window automatically closes and test results display on the original page.
If the test succeeds, you can save the settings, and select an enforcement mode. If the test fails, modify your configuration to address the issues reported and test the integration again.
Select an enforcement mode for SSO
When using SSO, there are three separate enforcement modes that you can choose from. These affect which methods of authentication your team members can use.
| Mode | SSO authentication allowed | Regular authentication allowed |
|---|---|---|
| Off | No | Yes |
| Optional | Yes | Yes |
| Required | Yes | No |
S'authentifier avec l'authentification unique
Une fois que vous avez terminé de configurer l’authentification unique, vous pouvez demander à vos utilisateurs de se connecter avec l’une des méthodes suivantes :
Stripe’s sign in page
Users can go to the Stripe sign in page, enter their email, then select Use single sign-on (SSO).
Si un utilisateur a accès à plusieurs comptes, Stripe l’authentifie avec le compte par défaut associé à l’utilisateur. Si un utilisateur n’a accès qu’aux marchands SAML ou n’a accès à aucun marchand, Stripe le redirige vers le fournisseur d’identité, quel que soit le contenu du champ de mot de passe.
IdP-initiated login
Pour utiliser la connexion effectuée par le fournisseur d’identité, votre fournisseur d’identité doit prendre en charge la connexion lancée par le prestataire de services. Vérifiez si cela est possible à l’aide de la documentation de votre fournisseur d’identité.
SSO URL
Use the following login URL with your domain to directly sign in to your account with SSO. This URL includes the domain and account you want to use for SSO authentication. If you change the account token at the end of the URL, it authenticates you against a different account.
https://dashboard.stripe.com/login/saml_direct/domain/{{YOUR_DOMAIN}}/merchant/{{STRIPE_ACCOUNT_ID}}
Support for multiple Stripe accounts
If you’re configuring SSO for multiple Stripe accounts, first create an organization to centrally configure SSO across all of your accounts. You can change the account token at the end of the SSO URL to authenticate against another account. You can find the list of account tokens in the Accounts section of your Personal details settings.
Connexions IdP multiples : Si vous avez plusieurs entreprises Stripe avec plusieurs paramètres IdP (par exemple, des points de terminaison SAML ou des ID d’émetteur différents), mais qui partagent le même domaine, nous vous recommandons d’utiliser des URL de connexion.
Révoquer l’accès des membres de l’équipe
Vous pouvez révoquer l’accès d’un membre de l’équipe à l’aide de méthodes actives ou passives.
Révoquer activement l’accès à l’aide d’une assertion
Envoyez à Stripe une assertion de votre fournisseur d’identité pour permettre à un membre de l’équipe d’accéder à des comptes Stripe spécifiques. Cela vous permet également de révoquer l’accès d’un membre de l’équipe. Pour révoquer l’accès d’un membre d’une équipe, attribuez-lui le rôle none pour l’accès du compte Stripe que vous souhaitez révoquer. Par exemple :
<saml2:attribute name="Stripe-Role-STRIPE-ACCOUNT-ID" NameFormat="urn:oasis:names:tc:SAML:2.0:attrname-format:basic"> <saml2:attributevalue>none </saml2:attributevalue> </saml2:attribute>
Avertissement
Vous ne pouvez pas révoquer l’accès d’un compte Stripe à son propriétaire.
Révoquer l’accès de manière passive à l’aide d’un mode d’application
Lorsque le mode d’application est défini à obligatoire, seuls les membres de l’équipe qui peuvent s’authentifier auprès de votre fournisseur d’identité peuvent accéder à votre compte Stripe. En mode obligatoire, vous pouvez révoquer l’accès d’un membre de l’équipe à un compte Stripe en empêchant votre fournisseur d’identité de l’authentifier. Dans le Dashboard Stripe, définissez l’authentification unique à requise dans l’authentification utilisateur.