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
Former Member
2 years agoerror: failed to create secret secrets "scimsession" already exists
Brand new deployment as of 4/10/23
Deployment instructions do not include what I assume is a method to update the scimsession after regenerating credentials.
After regenerating the credentials ...
Former Member
2 years agoUpdated with response from Support:
On your cluster (this is in Azure btw) do the following. Responses from commands included.
```
kubectl delete secret scimsession
$ secret "scimsession" deleted
```
Then re-create it:
```
kubectl create secret generic scimsession --from-file=scimsession=/home/$USER/scimsession
$ secret/scimsession created
```
After setting your new scimsession secret, you must restart your 1Password SCIM Bridge for the pod to read the scimsession secret. You can do this by using this command:
kubectl scale deploy/op-scim-bridge --replicas=0 && sleep 3 && kubectl scale deploy/op-scim-bridge --replicas=1
$ deployment.apps/op-scim-bridge scaled
$ deployment.apps/op-scim-bridge scaled