Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
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
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
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?