There is no claims identity. Please make sure the web application is configured to use Claims Authentication.

[PaulBol]

I followed the instructions step by step. The URL generated by TokenHelper.GetAuthorizationUrl does not lead to a consent page in step 3 but the message.

Sorry, something went wrong

There is no claims identity. Please make sure the web application is configured to use Claims Authentication.

I wish the page would provide an explanation of the error and ideally a solution too.

---

Document Details

⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

• ID: 9be50ae2-2435-480a-0c1e-efca679cd00e
• Version Independent ID: d3c81315-c73e-61c8-2287-dc6e6e5eec5c
• Content: Authorization Code OAuth flow for SharePoint Add-ins
• Content Source: docs/sp-add-ins/authorization-code-oauth-flow-for-sharepoint-add-ins.md
• Product: sharepoint
• GitHub Login: @VesaJuvonen
• Microsoft Alias: vesaj

Thank you for reporting this issue. We will be triaging your incoming issue as soon as possible.

[o-sousa]

This is a problem affecting existing add-ins that were working fine.
It is becoming business critical since users are not able to authorize any connections.

Created a brand new add-in using appregnew.aspx and it gets exactly the same error.

Do you have any update on this?

[PaulBol]

For me the problem does not seem to occur anymore. Several people reported the same problem at https://docs.microsoft.com/en-us/answers/questions/522147/oauthentication-with-office-365-failure-there-is-n.html

[o-sousa]

Yes it is solved on my side too, thank you for letting me know.

[github-actions]

Thank you for taking the time to file an issue. We periodically archive older or inactive issues as part of our issue management process, which automatically closes them once they are archived.

If you’d like to understand more about why and how we handle archived (closed) issues, please see Our approach to closed issues.

We appreciate your contribution and if this is still an active issue with the latest SPFx versions, please do resubmit the details. We needed to perform a cleanup, so that we can start with a clean table with a new process. We apologize for the inconvenience this might cause.