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.
OAuth2SchemeBuilder.AuthorizationUrl() incorrectly parses OAuth2 auth url with Azure AD B2C signin policy
See original GitHub issuewhen using Azure AD B2C, the OAuth2 authorization url is something like:
https://login.microsoftonline.com/mytenant.onmicrosoft.com/oauth2/v2.0/authorize?p=b2c_1_mysigninpolicy
note that this authorization url has a query parameter that indicates the B2C policy to use
when using this url with OAuth2SchemeBuilder.AuthorizationUrl() then in Swagger UI the completed authorization url becomes:
https://login.microsoftonline.com/mytenant.onmicrosoft.com/oauth2/v2.0/authorize?p=b2c_1_mysigninpolicy?response_type=token&redirect_uri=....
notice the double appearance of a question mark: apparently the code doesn’t properly parse the provided authorization url, but just blindly appends a new question mark and further querystring parameters
this breaks authentication with a 404 not found
the correct composed url should instead be:
https://login.microsoftonline.com/mytenant.onmicrosoft.com/oauth2/v2.0/authorize?p=b2c_1_mysigninpolicy&response_type=token&redirect_uri=....
Issue Analytics
- State:
- Created 7 years ago
- Comments:6 (1 by maintainers)
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
is there an example for setting up Azure AD B2C with swashbuckle on .NET core?
@markti I just found this article which helped my out.