Deploy 1Password SCIM Bridge on Azure Kubernetes Service

With 1Password Business, you can automate many common administrative tasks using 1Password SCIM bridge. It uses the System for Cross-domain Identity Management (SCIM) protocol to connect 1Password with your existing identity provider, like Azure Active Directory, JumpCloud, Okta, OneLogin, or Rippling.

Step 1: Add provisioning to your 1Password account

Before you can deploy 1Password SCIM bridge, you’ll need to add the provisioning integration and get credentials for it. Click Get Started, sign in to your 1Password account, and follow the onscreen instructions.

Get Started

If you see the details for an existing provisioning integration, you’ll need to deactivate it first. Click More Actions and choose Deactivate Provisioning.

After you complete the setup process, you’ll get a scimsession file and bearer token. Save them both in 1Password and save the scimsession file to your computer. You’ll need these to deploy the SCIM bridge and connect your identity provider.

Step 2: Create and configure the Kubernetes cluster

2.1: Start creating a Kubernetes cluster

The SCIM bridge must be deployed to a cluster. To create a cluster:

1. Sign in to your account on the Microsoft Azure portal.  
2. On the Azure portal menu or from the Home page, select “Create a resource”.
3. Select Containers > Kubernetes Service.

2.2: Configure your cluster

Configure your cluster using the following options. For all other options, you can use the provided defaults or choose your preferred options.

Project details:

• Resource group
  Choose one, or click “Create new” and enter “1Password”.

Cluster details:

• Kubernetes cluster name
  Enter “op-scim”.

Primary node pool:

• Node size
  The SCIM bridge requires at least a “Standard B2s” VM size.
• Scale method
  Choose Autoscale.
• Node count
  The SCIM bridge requires at least 2 nodes.

After you’ve configured your cluster, click “Review + create”. It may take a moment. When you see “Validation passed”, click “Create”.

When you see “Your deployment is complete”, continue to the next step.

Step 3: Set up and deploy 1Password SCIM bridge

3.1: Connect to your Kubernetes cluster

1. Open your cluster on the Microsoft Azure portal.  
2. Click Connect at the top of the page.
3. Click Open Cloud Shell to connect to the cluster.

3.2: Clone the scim-examples repository

All the configuration files you need to deploy the SCIM bridge are available in the scim-examples repository on GitHub.

Switch to the directory where you want to clone the repository, then run the following command:

git clone https://github.com/1Password/scim-examples.git

Switch to the Kubernetes directory in the cloned repository:

cd scim-examples/kubernetes

3.3: Upload your scimsession file

3.4: Create the Kubernetes Secret

To create the Kubernetes Secret, run the following command:

• Bash:

    kubectl create secret generic scimsession --from-file=scimsession=/home/$USER/scimsession
  

• Powershell:

    kubectl create secret generic scimsession --from-file=scimsession=/home/$Env:USER/scimsession
  

3.5: Configure 1Password SCIM bridge

1Password SCIM bridge uses a TLS certificate provided by Let’s Encrypt to secure communication with your identity provider. Edit op-scim-config.yaml to set the domain name for the certificate.

Enter the fully qualified domain name (FQDN) you plan to use for your SCIM bridge (for example: scim.example.com) as the value for OP_LETSENCRYPT_DOMAIN. Save the file.

3.6: Deploy 1Password SCIM bridge

1Password SCIM bridge uses a Redis instance to store and cache your Let’s Encrypt TLS certificate. Deploy the configuration, 1Password SCIM bridge, Redis, and the load balancer using the following command:

kubectl apply -f .

If you use Azure Firewall or are restricting ingress to your SCIM bridge, open port 443 for your Azure Kubernetes cluster. The Let’s Encrypt service uses port 443 to renew the TLS certificate every 60 days. All other SCIM bridge traffic uses port 443.

3.7: Create the DNS record

To get the external IP address of the load balancer:

kubectl get services

If you don’t see the IP address in the External IP column, wait a few minutes and try again.

Add an A record to the DNS entry for your domain that points to the IP address for the load balancer.

Step 4: Test your SCIM bridge

To check that the DNS has propagated and the SCIM bridge is deployed successfully, visit the domain you configured in the previous step in your browser. You’ll see a 1Password SCIM Bridge status page. Enter your OAuth bearer token to verify it’s correct.

Use your bearer token and domain (for example: scim.example.com) to test the connection to 1Password:

curl --header "Authorization: Bearer <bearer_token>" https://<domain>/scim/Users

If you see a list of the users in your 1Password account, your SCIM bridge is deployed correctly.

Step 5: Connect your identity provider to the SCIM bridge

Because 1Password SCIM Bridge provides a SCIM 2.0-compatible web service that accepts OAuth bearer tokens for authorization, you can use it with a variety of identity providers.

Get help

Get help with the SCIM bridge, like if you lose your bearer token or session file.

For more information about the SCIM bridge, contact your 1Password Business representative. To get help and share feedback, join the discussion with the 1Password Support Community.

Learn more

• Update 1Password SCIM Bridge
• Quickstart: Deploy an Azure Kubernetes Service (AKS) cluster using the Azure portal