Self-hosting SCIM
note
The steps described in this article are for Docker standard deployments, in Helm deployments you will instead need to set scim: true
in the values.yaml
file to enable SCIM.
In order to use SCIM to automatically provision and de-provision members and groups in your self-hosted Bitwarden organization, you will need to enable a flag in your config.yml
file. To enable SCIM for your Bitwarden server:
Save a backup of, at a minimum,
.bwdata/mssql
. Once SCIM is in use, it's recommended that you have access to a backup image in case of an issue.note
If you are using an external MSSQL database, take a backup of your database in whatever way fits your implementation.
Update your self-hosted Bitwarden installation in order to retrieve the latest changes:
Bash./bitwarden.sh update
Edit the
.bwdata/config.yml
file and enable SCIM by togglingenable_scim
totrue
.Bashnano bwdata/config.yml
Rebuild your self-hosted Bitwarden installation:
Bash./bitwarden.sh rebuild
Update your self-hosted Bitwarden installation again in order to apply the changes:
Bash./bitwarden.sh update
Now that your server has SCIM enabled, use one of our SCIM integration guides to integrate your Bitwarden organization with:
Suggest changes to this page
How can we improve this page for you?
For technical, billing, and product questions, please contact support