You can deploy 1Password SCIM Bridge on any supported infrastructure that allows ingress by your identity provider and egress to 1Password servers. Here you'll find configuration files and best practices to help with your deployment.
Tip
Before you deploy your SCIM bridge, learn more about automating provisioning in 1Password using SCIM.
For an automated deployment of 1Password SCIM Bridge where some settings are pre-configured for you, use a marketplace app from Google Cloud Platform or DigitalOcean:
To customize your deployment, you can use containers as a service or create your own advanced deployment with the examples below as your base.
Before you begin deploying 1Password SCIM Bridge, review the Preparation Guide. The guide will help you plan for some of the technical components of the deployment and consider some issues you may encounter along the way.
Containers as a service (CaaS) can simplify your deployment by using the built-in tools of the CaaS for DNS and certificate management. This gives you an easy, low-cost SCIM bridge with minimal infrastructure management requirements.
- Azure Container Apps
- DigitalOcean App Platform
If you have particular requirements for your environment, we recommend an advanced deployment. These example configurations will give you a base to create the deployment from, as well as explain what 1Password SCIM Bridge needs to function and how to maintain your bridge once you've deployed it.
These are beta versions of 1Password SCIM Bridge deployment examples. These deployments should work, but aren't guaranteed and will change in the future. See the README for more information about the "beta" designation.
- ✨ NEW AWS with CloudFormation
- ✨ NEW Docker
A list of recently-deprecated deployments can be found in /deprecated. At the time of deprecation, these deployments were fully functional, but will soon become unsupported.
When a deployment method is deprecated, we will simultaneously append a deprecation notice to the deployment name listed in this README and move all files associated with the deployment method to /deprecated.
Deprecated deployments will remain in /deprecated for approximately three months, after which time they will be deleted. The deletion date of deprecated deployments will be posted in /deprecated/README.md.
Where possible, we will provide suggested alternatives in /deprecated/README.md.
If you encounter issues with your SCIM bridge deployment or have general questions about automated provisioning, contact 1Password Support. If you need additional deployment examples or some information in these guides needs improvement, file an issue or open a pull request in this repo to let us know.