Can't provision from AAD to 1Password
Since 11:30AM CDT we've been receiving the following error in AAD when trying to provision to 1Password. Sure seems like an issue on your end. Please advise when this will be fixed.
Quarantine details:
While attempting to validate our authorization to access your application, we received this unexpected response: Received response from Web resource. Resource: https://1passwordscim..com/Users?filter=userName+eq+"74c00658-bac4-44b1-96ca-086bf62408d5" Operation: GET Response Status Code: InternalServerError Response Headers: Content-Security-Policy: default-src 'none'; connect-src 'self' https:; script-src 'self'; img-src 'self' data: https://w3.org; style-src 'self'; frame-ancestors 'none'; form-action 'none'; manifest-src 'self' Referrer-Policy: no-referrer Request-Id: chj823f9ipkdc37ofdq0 X-Content-Type-Options: nosniff X-Frame-Options: DENY X-Robots-Tag: none X-Xss-Protection: 1; mode=block Date: Thu, 18 May 2023 19:48:30 GMT Response Content: {"detail":"failed to create session","schemas":["urn:ietf:params:scim:api:messages:2.0:Error"]} Please check the service.
1Password Version: Not Provided
Extension Version: Not Provided
OS Version: Not Provided
Browser:_ Not Provided
Referrer: forum-search:SCIM provisioning quarantine error
Comments
-
We are also getting this, opened support ticket and no response yet.
Were you able to resolve anything?
From what I can tell, it appears to be a certificate issue/bug that is supposed to be resolved in the most recent version of the SCIM Bridge, however I cannot get my Bridge to update.0 -
Hey @skdyer and @jcochran, there were some Let's Encrypt issues that have been resolved in SCIM bridge version 2.8.1. Please update to the latest version, and please let us know if you continue to have issues.
@jcochran, can you share any error messages or specific issues you are having while upgrading the SCIM bridge? What is your deployment method? I can share more specific troubleshooting steps at that point. For example, if you're using Kubernetes, this example might help you.
0 -
yeah sorry, we just needed to regenerate our SCIM bridge token. We are all set.
0 -
Glad to hear it!
0 -
Thanks, we are all set. Support finally got back to me after over a week and we got it resolved. Same as skdyer, needed to regenerate the Token and reconfigure it.
0
