Skip to main content
Bitwarden is a password manager platform for storing and sharing credentials securely. Connect your Bitwarden organization to Oleria to bring user and group access into your identity and access graph, without a dedicated Bitwarden-specific integration.

​
What Oleria discovers

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

​
Prerequisites

  • Admin access in the Bitwarden Admin Console 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 Bitwarden’s own SCIM provisioning documentation.

​
Get your SCIM credentials from Bitwarden

1

Enable SCIM provisioning in the Bitwarden Admin Console

Sign in to the Bitwarden Admin Console as an admin and enable SCIM provisioning in Settings.
2

Copy your SCIM Base URL and Authentication token

Bitwarden 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 Bitwarden organization.
  • Authentication token - the bearer token Bitwarden generates for provisioning.
Bitwarden displays the token only once. Copy and store it securely, and rotate it per your organization’s security policy.

​
Connect Bitwarden to Oleria

1

Open the integration

Go to your Oleria workspace, select Integrations, then select the Bitwarden 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 and groups from Bitwarden on the standard SCIM provisioning schedule once the initial sync completes.
If Bitwarden rotates your bearer token, update the Authentication token in Oleria by editing the integration.

​
Governance actions

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

​
Contact us

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