BrowserStack SSO with ADFS | SAML

Integrate your ADFS directory with BrowserStack to set up Single Sign-on

Introduction

Single Sign-on (SSO) integrates an external user directory with your BrowserStack Group. This document describes how to configure Single Sign-on when Azure Directory Federated System (ADFS) is your identity provider.

In this tutorial, you’ll learn how to integrate BrowserStack with ADFS (ADFS). When you integrate BrowserStack with ADFS, you can:

  • Control in ADFS who has access to BrowserStack.
  • Enable your users to be automatically signed-in to BrowserStack with their ADFS accounts.
  • Manage your accounts in one central location - the ADFS portal.

Prerequisites

To set-up and use ADFS and BrowserStack Single Sign-on (SSO) feature:

  • An ADFS Server Access.
  • You need to have administrator access to your organization’s ADFS Server.
  • You need to have an Enterprise plan with BrowserStack
  • To access the configuration/set-up on BrowserStack, you need to be Owner for your BrowserStack Group

Supported Features

The OneLogin & BrowserStack Single Sign-on integration currently supports the following features:

  • SP-initiated SSO
  • IdP-initiated SSO

Configuration Steps

A. BrowserStack Setup

  1. Sign-In to BrowserStack account as Owner.

  2. Go to Account -> Settings & Permissions page and select the Security tab. Click Configure under Single Sign On (SSO). Go to Account and click on Settings & Permissions and select the Security tab. Under Single Sign On (SSO), click Configure

  3. On the next screen, you will be shown all the Authentication services that BrowserStack supports, select SAML 2.0 and click Next. Choose SAML 2.0 in authentication services

  4. Choose ADFS from the list of Identity Providers, and click Next. Choosing from list of identifiers during setup

  5. Copy the following, will be needed for the next steps on ADFS server a. SP initiated ACS URL
    b. IdP initiated ACS URL
    c. Entity ID Copy SP initiated ACS URL, IdP initiated ACS URL and Entity ID from the list as the will be needed for the next steps on ADFS server

B. Configuring ADFS Server

  1. Go to your ADFS machine and add new Relying Party Trust. Add relying party trust

  2. Select Claims Aware. 6-adfs-configuringserver-2

  3. Check Enter data about the relying party manually and click next. Enter data about the relying party manually

  4. Give the connector a Name and click next. ADFS configure server - connector name

  5. Click Next on Configure Certificate. Click next on configure certificate

  6. Check Enable support for the SAML 2.0 WEB SSO Protocol
    • Paste the copied IdP initiated ACS URL in the text box and click next. Add reply party wizard focused at replying part saml 2.0 sso service url
  7. On Configure Identifier, enter the copied Entity ID in Relying party trust Identifier. Click next. Adding entity id in relying party trust identifier

  8. Choose your Access Control Policy, and click next Selecting access control policy

  9. Click next on Ready to Add Trust Ready to Add Trust

  10. Finish Click on Close button once finished

  11. Choose your added Relying Party Trust (list will contain the name you gave to the connector) and double click Choose Added Relying Party Trust

  12. Go to Endpoints tab and Choose the URL added and click Edit From the Endpoints tab choose the added URL and click on Edit button
    • Check the “Set the trust URL as default” and click OK Checked Set the trust URL as default in BrowserStack properties
    • Click on Add SAML to add another URL. Add SAML endpoint
    • Choose Bindings as POST, index 1, paste the copied SP Initiated URL in Trusted URL and click OK.
    • Click on Apply. Click on Apply button after adding the details
  13. Click on Edit Claim issuance Policy on right sidebar.
    • Click on Add Rule and choose the Claim rule template as “Transform an Incoming Claim” and click next. Transform an incoming claim inside edit claim issuance policy
    • Fill the form as following.
      • Claim rule name should be Name ID
      • Incoming claim type should be UPN
      • Incoming name id format should be Unspecified
      • Outgoing claim type should be Name ID
      • Outgoing name id format should be Email
      • Select Pass through all claim values
      • Click Finish. Transform an Incoming Claim form
    • Add another Rule. Select Claim rule template as Send LDAP Attributes as Claim and click next. Add rule & select claim rule template as Send LDAP Attributes Adding another claim rule during config
    • Fill the form as follows:
      • Claim rule name should be emailaddress
      • Attribute store should be Active Directory
      • Map the LDAP Attributes as following Configure the rule and map LDAP attributes
    • To get metadata from ADFS machine.
      • Go to YourADFSmachineURL/FederationMetadata/2007-06/FederationMetadata.xml
      • Download the Metadata file
    • For Sign-in URL search for the SingleSignOnService: Copy the Location attribute of this tag. (Make sure that Binding attribute value should be HTTP-POST) For Sign-in URL search for the SingleSignOnService and copy the Location attribute of the tag

    • For Sign-out URL search for the SingleLogoutService: copy the Location attribute of this tag. (Make sure that Binding attribute value should be HTTP-POST) ADFS configure SingleLogoutService

    • For Public Certificate search for the KeyDescriptor with use attribute as signing: Copy the X509Certificate tag value Copy X509Certificate tag value

C. Finishing Setup on BrowserStack

  1. Paste these values in the corresponding fields on ADFS configuration screen on Browserstack Paste values in the corresponding fields on ADFS configuration screen on Browserstack

  2. Click Next, opt for Advanced options (if needed) and Submit opt for Advanced options (if needed) and Submit

Test & Enable

  1. Test the integration via Test Setup Test SSO setup by clicking on Test Setup button

  2. You will be prompted towards Service Provider flow and your user will be authenticated via ADFS. The test is successful upon completion of the SSO Authentication flow.

  3. Upon a successful test, you can enable the Single Sign-on feature for your Organization.
    You have the option of sending out a mail to all Group members on BrowserStack, to inform them about this change, and link to the new login URL.
    Click Enable to enable the feature. Enable single sign-on for your organization

  4. You will automatically be logged out of the BrowserStack, and redirected to log-in via SSO.

Note: You will need to assign the Group Owner’s email address on BrowserStack’s ADFS app before you can test and enable it.

Troubleshooting

Incorrect ACS URL or Entity ID URL

If you are facing this error this means you configured wrong ACS URL or Entity ID URL in Relaying party trust SSO request is not able to find the correct configuration to complete.

Resolution: Please make sure that you configured the correct ACS URL and Entity ID in ADFS Relaying party Trust.

ADFS SSO Troubleshooting

Incorrect ACS URL

If you are facing this error this means you configured wrong ACS URL Relaying party trust.

Resolution: Please make sure that you configured the correct ACS URL in ADFS Relaying party Trust.

Incorrect ACS URL error occured while SSO

Email ID mismatch

If you are facing this error means you are logged in ADFS with different email Address and testing the setup with a different email.

Resolution: Please make sure that you are logged in with same email ID in ADFS and Browserstack.

Email ID in ADFS and Browserstack should be same

Incorrect configuration

This means you have misconfigured the app. ADFS is redirected to a different configuration. Please check the configuration on ADFS.

Resolution: Please check the configuration.

Troublsehooting ADFS configuration error in Account settings page on BrowserStack

Internal error

This means we found an internal error.

Resolution: If this problem persists, please connect with us via support@browserstack.com

Contact support for problems or errors

Note: Please connect with support@browserstack.com for any escalations or support.

We're sorry to hear that. Please share your feedback so we can do better







Contact our Support team for immediate help while we work on improving our docs.

We're continuously improving our docs. We'd love to know what you liked






Thank you for your valuable feedback

Is this page helping you?

Yes
No

We're sorry to hear that. Please share your feedback so we can do better







Contact our Support team for immediate help while we work on improving our docs.

We're continuously improving our docs. We'd love to know what you liked






Thank you for your valuable feedback!

Talk to an Expert
Talk to an Expert