Single sign-on with OneLoginPublic preview

A domain is the portion of an email address after the @ symbol (such as kavholm.com). You must configure SSO for Stripe for each of your business’s email domains. To verify domain ownership:

1. Navigate to User authentication in the Stripe Dashboard, and click + New domain to view your account’s unique verification code.
       stripe-verification=4242424242424242424242
   

2. Add the verification code as a TXT record to your Domain Name System (DNS) provider.
3. 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.
4. After successful verification, don’t delete the TXT record 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.

1. Create a new application to represent the relationship between OneLogin and the Stripe Dashboard. To do so, navigate to the Applications page, and select Add App.
2. Find the SAML Test Connector (IdP w/ attr w/ sign response) app.

1. Select Save, and navigate 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
2. Select SSO on the side panel, and set the Signature Algorithm to SHA-256.
3. 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.

1. Navigate 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.
2. 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 supports the following roles. Some of these roles are only available if your account uses the applicable Stripe product. For more information, see User roles supported by Stripe.

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 Profile.

1. Navigate 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.
2. Select the User you want to edit. Then, navigate to Applications on the side panel.
3. 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 analyst and the developer role when they sign in.

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.

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.

After you finish configuring SSO, you can inform your users to sign in with any of these methods:

Stripe’s sign in page

Users can navigate to the Stripe sign in page, enter their email, then select Use single sign-on (SSO).

If a user has access to multiple accounts, Stripe authenticates them with the default account connected to the user. If a user only has access to SAML merchants, or doesn’t have access to any merchants, Stripe redirects them to the IdP, regardless of the contents in the password field.

IdP-initiated login

To use IdP-initiated login, your IdP needs to support Service Provider-initiated login. Verify if this is possible using your IdP’s documentation.

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}}