{"id":4979,"date":"2024-01-05T11:20:29","date_gmt":"2024-01-05T19:20:29","guid":{"rendered":"https:\/\/SUMMALAI.COM\/?p=4979"},"modified":"2024-01-05T11:20:30","modified_gmt":"2024-01-05T19:20:30","slug":"how-to-troubleshoot-1password-azure-scim-bridge","status":"publish","type":"post","link":"https:\/\/SUMMALAI.COM\/?p=4979","title":{"rendered":"How to Troubleshoot 1Password Azure SCIM Bridge"},"content":{"rendered":"\n

All Kubernetes commands are run from the Azure Cloud Shell.
\u00a0
First, Let’s check if your pod was running:<\/u><\/strong><\/p>\n\n\n\n

kubectl get pods<\/code><\/pre>\n\n\n\n
\u00a0
Next, check your SCIM bridge logs to see if there is any errors:<\/u><\/strong><\/p>\n\n\n\n
kubectl logs deploy\/op-scim-bridge -f<\/code><\/pre>\n\n\n\n
\u00a0
Semms Let’s Encrypt rate-limited the server from obtaining a new TLS certificate; therefore, you will need to update your DNS record to bypass this.
\u00a0
for example, update the URL from\u00a0scim.example.org<\/em>\u00a0to\u00a0scim1pass.example.org<\/em>
\u00a0
Update the OP_TLS_DOMAIN with the new DNS record:<\/u><\/strong>
\u00a0<\/p>\n\n\n\n
kubectl set env deploy\/op-scim-bridge OP_TLS_DOMAIN=scim1pass.calgaryunitedway.org<\/code><\/pre>\n\n\n\n
\u00a0
After this, Regenerate Credentials once more to have a fresh set.
\u00a0
Delete the old scimsession<\/em> secret and put in the new one:<\/u><\/strong>
\u00a0<\/p>\n\n\n\n
kubectl delete secret scimsession<\/code><\/pre>\n\n\n\n
kubectl create secret generic scimsession --from-file=scimsession=\/home\/$USER\/scimsession<\/code><\/pre>\n\n\n\n
\u00a0
Next, Let’s loaded the new SCIM bridge URL and entered the new\u00a0bearer token<\/em>\u00a0to confirm everything was up and running! And it was!
\u00a0
Finally, we had to update the Entra ID 1Password Enterprise app to have the new SCIM bridge URL and new\u00a0bearer token:<\/em><\/u><\/strong>
\u00a0<\/p>\n\n\n\n
  1. Navigate to the 1Password Business Enterprise app.<\/li>
  2. Click Provisioning<\/strong>.<\/li>
  3. Click Provisioning<\/strong> again.<\/li>
  4. Expand Admin Credentials<\/strong>.<\/li>
  5. Update the URL<\/em> and API token<\/em>.<\/li>
  6. Click Test Connection.<\/strong><\/li>
  7. Click Save<\/strong>.<\/li>
  8. Click Overview<\/strong>.<\/li>
  9. Click Restart Provisioning.<\/strong><\/li><\/ol>\n\n\n\n
    \u00a0
    We now have the SCIM bridge back in working order!

    <\/p>\n","protected":false},"excerpt":{"rendered":"
    All Kubernetes commands are run from the Azure Cloud Shell.\u00a0First, Let’s check if your pod was running: \u00a0Next, check your SCIM bridge logs to see if there is any errors: \u00a0Semms Let’s Encrypt rate-limited the server from obtaining a new TLS certificate; therefore, you will need to update your DNS record to bypass this.\u00a0for example, Read More<\/a><\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_bbp_topic_count":0,"_bbp_reply_count":0,"_bbp_total_topic_count":0,"_bbp_total_reply_count":0,"_bbp_voice_count":0,"_bbp_anonymous_reply_count":0,"_bbp_topic_count_hidden":0,"_bbp_reply_count_hidden":0,"_bbp_forum_subforum_count":0,"om_disable_all_campaigns":false,"_monsterinsights_skip_tracking":false,"footnotes":""},"categories":[1734,1249,10],"tags":[],"class_list":["post-4979","post","type-post","status-publish","format-standard","hentry","category-1password","category-azure-microsoft","category-microsoft"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\n\t\t