Single sign-on with OktaPublic 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.

Create an app in Okta to represent the relationship between the Stripe Dashboard and Okta:

1. Open and log in to the Okta admin portal.
2. In the left navigation pane, navigate to Dashboard > Applications > Add Application.
3. Click Create App Integration > SAML 2.0 > Next.
4. Enter an App name (for example Stripe Integration), then click Next.
5. Configure your SAML settings in Okta:
   • For Single sign-on URL, add the value: https://dashboard.stripe.com/login/saml/consume.
   • For Audience URI, add the value: https://dashboard.stripe.com/saml/metadata.
   • For Name ID format, select EmailAddress.
   • For Application username, select Email.
6. Next, click Show Advanced Settings:
   • For Signature Algorithm, select RSA-SHA256.
   • For Digest Algorithm, select SHA256.
7. Click Next, then select This is an internal app that we created for App type.
8. Click Finish.

Assign Stripe roles for your users by creating attribute statements in your Stripe app in Okta. Stripe roles give users different degrees of access to the Stripe Dashboard. An attribute statement consists of two components. The name represents the Stripe account where you want to assign roles. The value represents the roles you want to assign to the Stripe account. Users can have different roles in a single account or across multiple accounts in an organization.

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.

Create a custom role attribute

1. In the left navigation pane, navigate to Directory > Profile Editor.
2. Click the name of your Stripe app, then click Add Attribute.
3. Set Data type to String Array.
4. For Display name, enter Stripe Roles.
5. For Variable name, enter stripe_roles.
6. Select Define enumerated list of values, then add an attribute member for each Stripe role you want to assign to your users. For example, Display name: Administrator, Value: admin.

   Warning

   Make sure to assign at least one user or group the super_admin role. This ensures your organization receives important notifications about your account health. Only users with the Super Admin role can make changes to your account structure, close the account, or change the default bank account.

7. For Attribute required, select Yes.
8. For Attribute type, select Group.
9. For Group Priority, select Combine values across groups. Select this if you want to assign a user multiple roles across multiple Stripe accounts.
10. Click Save, and copy the variable name of the attribute you created for later use.

Create a group of users

1. In the left navigation pane, navigate to Directory > Groups.
2. Click Add group, enter a group name (such as Super Admins in Stripe), then click Save.
3. In the group list, click the name of your group, then click Assign people.
4. Add users by searching for their first name, primary email address, or username.

Grant the group access to the Stripe app

1. Click the Applications tab > Assign applications.

2. Next to the name of your Stripe app, click Assign.

3. Select any Stripe roles you want to give to the group, then click Save and go back > Done. This assigns the roles to all the users in this group. All the users in this group can log into Stripe, and their role is automatically set to the value you set.

   

   If a user belongs to multiple groups, Okta combines the roles assigned across all the groups. For example, if a user belongs to the following groups:

   • IAM Group
   • Stripe Admin Group
   • Stripe Developer Group

   Then, they’re assigned the roles from all of the groups:

   

Update the value of your attribute statement

1. In the left navigation pane, navigate to Applications, then click your Stripe app.
2. Click the General tab > SAML settings > Edit.
3. In the Attribute Statements section, assign a dynamic role to a user:
   • For Name, enter the Stripe account ID. Use the format Stripe-Role-<account-id>. For example, if the account ID is acct_1JgxGwHIzIlFIyZf, enter the name Stripe-Role-acct_1JgxGwHIzIlFIyZf. For a list of account ids, navigate to the Accounts section in your Personal details settings in the Stripe Dashboard.
   • For Name format, select Basic.
   • For Value, enter appuser.<variable-name>. If you didn’t save the variable name, navigate to Directory > Profile Editor, click your Stripe app, and use the variable name next to the applicable attribute. For example, appuser.stripe_roles.
4. Click Save. This tells Okta to send an attribute statement with each assertion for the account and role.

(Optional) Assign roles in multiple Stripe accounts

To assign roles across multiple Stripe accounts, create a separate attribute statement in your app for each of your accounts.

(Optional) Assign roles in your organization

If you use Organizations, grant team members access to your organization by assigning roles in your organization. Organization-level roles grant access to the Organization, as well as all of the accounts within it.

1. Find your organization-id in Stripe by account switching to your organizations and navigating to Settings > Organizations management.
2. In Okta, in your app’s list of Attribute Statements, create an attribute statement using the format Stripe-Role-<organization-id>.

To configure Stripe with SSO:

Retrieve the following values from Okta

1. Open the Okta admin portal.
2. In the left navigation pane, navigate to Applications, then select your Stripe app.
3. Click the Sign On tab > View SAML Setup Instructions to open a page that displays the following values:
   • Identity provider Issuer: An identifier of your identity provider.
   • Identity provider single Sign-On URL: The URL of your identity provider that your users are redirected to, so they can authenticate.
   • X.509 Certificate: The X.509 certificate that your identity provider uses to sign assertions.

Configure your Stripe account to connect with Okta

1. In the Stripe Dashboard, navigate to Settings > Team and security > User authentication.

2. Next to the domain name, click the overflow button () > Manage SSO settings.

3. Click Test your configuration > Next.

4. Provide info for your identity provider:

   • For Issuer ID, enter the value for Identity provider Issuer in Okta.
   • For Identity provider URL, enter the value for Identity provider single Sign-On URL in Okta.
   • For Identity provider certificate, enter the value for X.509 Certificate in Okta.

5. Click Test configuration to open a new window to test your configuration. Exit this window, and return to the original window.

6. If you pass the test, click Done.

   If the test fails, refer to Troubleshoot SSO, and address the reported issues in your Stripe app in Okta.

7. Select SSO enforcement. You can choose between Off, Optional, or Mandatory. You can change enforcement type in the future.

8. Click Save settings > Done.

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