Skip to main content
BrowserStack is a cloud platform for testing web and mobile apps across real browsers and devices. Connect your BrowserStack account to Oleria to bring user access into your identity and access graph, without a dedicated BrowserStack-specific integration.

​
What Oleria discovers

User accounts and profile attributes synced from BrowserStack’s directory. Oleria uses this data for dormant account detection and access reviews, refreshed on BrowserStack’s standard SCIM provisioning schedule.

​
Prerequisites

  • Admin access in BrowserStack with permission to enable SCIM provisioning and generate a bearer token.
  • Admin access on the Oleria platform to add a new integration.
The exact location of these settings can change over time. If the steps below don’t match what you see, refer to BrowserStack’s own SCIM provisioning documentation.

​
Get your SCIM credentials from BrowserStack

1

Enable SCIM provisioning in BrowserStack

Sign in to BrowserStack as an admin and enable SCIM provisioning in Settings.
2

Copy your SCIM Base URL and Authentication token

BrowserStack generates a SCIM base URL and a bearer token when you enable provisioning. Copy both values before you leave the page - you’ll paste them into Oleria in the next section:
  • SCIM Base URL - the HTTPS SCIM endpoint for your BrowserStack account.
  • Authentication token - the bearer token BrowserStack generates for provisioning.
BrowserStack displays the token only once. Copy and store it securely, and rotate it per your organization’s security policy.

​
Connect BrowserStack to Oleria

1

Open the integration

Go to your Oleria workspace, select Integrations, then select the BrowserStack tile.
2

Complete the connection form

Select Continue and fill in the connection form:
3

Save the integration

Select Connect to validate the credentials and save the integration.

​
Verify the integration

Confirm the new instance appears in your Oleria workspace under Connected Integrations with a status of Healthy. Oleria syncs users from BrowserStack on the standard SCIM provisioning schedule once the initial sync completes.
If BrowserStack rotates your bearer token, update the Authentication token in Oleria by editing the integration.

​
Governance actions

Oleria can also invoke lifecycle actions in BrowserStack when the token you provide has write access:
  • Enable or disable a user account
  • Create a new user
Many teams start with a read-only token for visibility, then grant write access once they’re ready to automate remediation in BrowserStack.

​
Contact us

For questions about this integration, contact us at support@oleria.com.