Signing back into the Community for the first time? You'll need to reset your password to access your account. Find out more.
Forum Discussion
Redeploy SCIM bridge
Hi,
We deactivated provisioning in 1Password in order to enable health monitor, but unable to set it up again by navigating to the same domain URL. SCIM bridge was set up in GCP via marketplace. A...
Hi @yma,
Graham here, jumping in for DV.
Indeed when you deactivate the integration, it removes the service account associated with the scimsession and bearer token deployed on your bridge. Therefore the bridge will no longer be able to authenticate with our servers. In order to get back up and running, you will need to redeploy the bridge.
You mentioned you deployed the bridge on GCP. What you need to do is almost the same as the redeploy option documented in updating the bridge, with one exception: as you deleted the integration, you will need to remove the old and now invalid scimsession file from the disk on the Kubernetes cluster. To do that, go to Kubernetes Engine --> Storage, find the Persistent Volume Claim (pvc) associated with your cluster, and delete it. Then you should then be good to redeploy. The persistent volume claim will get automatically re-created during the re-installation.
In the future, to enable Health Monitoring after deployment, you can go into the integration and under Health Monitoring, click Manage, toggle on Health Monitoring, enter your SCIM bridge address, and then press Save.
Integrations Page, select Manage in the top right
Toggle Health Monitoring On
Enter your bridge address, and press save.
Let me know what further questions you have!
Graham
