While either developing or just trying to use an application that authenticates against Azure AD, you might get an error message that contains error code “AADSTS70005“. This means that you’re trying to use implicit authentication flow, but it isn’t allowed for your app. If you have access to the Azure AD you’re authentication against, it’s easy to fix! See more below…
You might get an error, somewhat like this:
AADSTS70005: response_type 'token' is not supported for the application Trace ID: <Guid_1> Correlation ID: <Guid_2> Timestamp...
This is returned by your Azure AD instance, as it doesn’t allow the use of implicit OAuth2 authentication flow for the application id you’re using.
Solution: Enable the Implicit Authentication Flow
Okay, luckily the fix is going to be easy. You can resolve the issue by enabling the implicit authentication flow for OAuth2. There’s actually no switch in GUI for this – you’ll have to edit the manifest of your registered Azure AD application yourself. Follow these steps:
- First, browse to your registered app in your Azure AD instance. If you’re working with SharePoint Online (like I was), see this article on how to find the correct instance: How to use the Azure AD associated with your SharePoint Online! 🙂
- Then open the Manifest editor from the “ribbon”, see below for an example:
- Following that, you’ll need to edit the manifest to allow for implicit oauth2 authentication. See the highlighted row below:
Then just hit “Save”, and try again! It should work now 🙂
Latest posts by Antti K. Koskela (see all)
- Thanks for coming to my session at SPS New England 10/20 ! - October 20, 2018
- Speaking at SPS New England on 10/20! - October 17, 2018
- Ignite 2018 recap: What’s new for Azure Functions? - October 16, 2018
- Problematic behavior of web.AddSupportedUILanguage(int lcid) in SharePoint 2013 and 2016 - October 10, 2018