Protect what matters – even after you're gone. Make a plan for your digital legacy today.
Forum Discussion
Former Member
4 years agoEncountered an error when testing the SCIM bridge for our Azure Kubernetes
I am setting up the SCIM bridge for our tenant using Azure Kubernetes. I followed the instructions from this guide: https://support.1password.com/scim-deploy-azure/#step-4-test-the-scim-bridge and go...
Former Member
4 years agoThis issue is now resolved after we do the following:
* clear the redis cache
* restarted the SCIM bridge
Thanks to @DeVille_1P for providing support and the detailed instructions below.
The steps to clear the redis cache and restart the SCIM bridge are as follows:
1. Open a terminal where you have access to the Kubernetes command line interface (kubectl), and make sure you are connected to the cluster running your SCIM bridge
2. Scale down the SCIM bridge instance in your cluster: kubectl scale --replicas=0 deployment/
3. Scale down the redis instance in your cluster: kubectl scale --replicas=0 deployment/
4. Wait a few seconds for the Kubernetes scheduler to remove the running redis and SCIM bridge instance
5. Scale up the redis instance in your cluster: kubectl scale --replicas=1 deployment/
6. Scale up the SCIM bridge instance in your cluster: kubectl scale --replicas=1 deployment/
You may need to specify the namespace for your SCIM bridge and redis deployment. You can get the namespace for these by issuing the kubectl get deployment --all-namespaces command. You can then include the namespace in the above commands by adding the --namespace=