What I meant is that it's an app we created in 2014 and didn't touch its code since then. It contains UIWebview etc. where in order to submit a new review will make us change a lot of code. We don't want to touch it, just leave it alive as long as it will take by itself.

Hi, Did you get an answer? I'm trying to do the same.

Have you found a solution to your problem? We also have SSO extension issues.

Yes, but what will happen if the users can't enable their iCloud keychain? We have this issue today where users are already registered on iOS 15 and once they upgraded to iOS 16 they can't use it anymore as their iCloud Keychain is disabled due to enterprise restrictions. We hear more and more complaints from big customers affected by this.

It's a long shot as two years passed, but have you found the answer?

I'm using Implicit and need to return the access token and ID token. On second thought, we are probably doing Device flow (or hybrid) as the authentication is done via a push to the user's mobile device, and we poll for the answer while waiting. We do not use SFSafari or any other in the extension, but regular NSSessions to complete the flow in front of our AS (also certificate-based) so the extension will catch the "authorize", do the token endpoint, etc., and needs to return to Safari with the access token and ID token, but it seems what I try doesn't work. I tried 200 but return to a blank page.

Did you find a solution? Would love to hear about it.

Did you find a solution? I have the same issue

Opened a feedback: FB12334503 with sysdiagnose

I didn't solve it.

I'm getting the same issue. I tried with Admin and Developer permissions. GET works, PATCH doesn't. Status Code: 403 { "errors": [ { "status": "403", "detail": "The API key in use does not allow this request", "code": "FORBIDDEN_ERROR", "id": "<redacted>", "title": "This request is forbidden for security reasons" } ] } Failed to update profile <redacted> Status Code: 403 { "errors" : [ { "id" : "<redacted>", "status" : "403", "code" : "FORBIDDEN_ERROR", "title" : "This request is forbidden for security reasons", "detail" : "The API key in use does not allow this request" } ] }

OK, I found out that a line in my associated domains caused it. Although I had the right line in there, I had another line with a diff domain that didn't match. It didn't accept me having two lines with authsrv and diff domains. Once I removed it everything started working again.

Have you found the solution? Having the same issue.

ok. I just change the config in the user registration method and then rerun again, and due to config changes it will run the device registration again. This is awkward.