OAuth SignUp 403 response (when using Identity Experience Framework)
See original GitHub issueBug description
I’ve followed the steps to integrate B2C Signin / Signup with the new portal. https://docs.microsoft.com/en-us/azure/api-management/api-management-howto-aad-b2c
Sign in works fine, but on the complete sign up page I see the error message Server error. Unable to send request. Please try again later.
caused by a HTTP 403 response to https://my-api-name.management.azure-api.net/subscriptions/xxx/resourceGroups/xxx/providers/Microsoft.ApiManagement/service/xxx/users?api-version=2018-06-01-preview
(note the xxx are in the call made, see screenshot).
Is there some additional setup with products or subscriptions I’m missing?
Reproduction steps
- As above
Expected behavior
OAuth Sign up to complete.
Is your portal managed or self-hosted?
Managed
Release tag or commit SHA (if using self-hosted version)
N/A
API Management service name
Prefer not to say.
Environment
- Operating system: Windows
- Browser: Google Chrome
Additional context
Issue Analytics
- State:
- Created 4 years ago
- Comments:6
Top Results From Across the Web
"403: Forbidden" returned by /oauth/token - Auth0 Community
Generally, the 403 Forbidden error happens when the authorization code passed in the request is invalid, revoked, or expired. This is detailed ...
Read more >Microsoft EWS throws "403 Forbidden" in modern oAuth ...
This means that, while you may have a valid authentication token, that token does not grant you access to the specific resource you're...
Read more >403 Forbidden - HTTP - MDN Web Docs - Mozilla
The HTTP 403 Forbidden response status code indicates that the server understands the request but refuses to authorize it.
Read more >Resolve Microsoft Graph authorization errors
Authorization errors can occur as a result of several different issues, most of which generate a 403 error (with a few exceptions).
Read more >403 Forbidden Error: What It Is and How to Fix It - Airbrake Blog
If the application you're using has some form of user authentication, the last client-side step to try is to log out and then...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Hi @simonness, thank you for confirming this. You’re right, we added a work item to update documentation, thanks!
@azaslonov I’ve updated the policy to also include:
<OutputClaim ClaimTypeReferenceId="objectId" PartnerClaimType="oid"/>
and it did the trick. Thanks very much for the push in the right direction!
I couldn’t spot anything in the documentation covering this, might be worth updating?