Test Console > OAuth 2.0 Authorization Code Authorization > "Unable to authenticate due to internal error." about api-management-developer-portal

[phsmith]

I got the same behavior even though the access_token was generated successfully and the requests work fine, but the alert keeps showing in a loop.

I have tested with the latest versions of Chrome and Firefox.

Edit: I disabled the React Developer Tools extension and the alert goes away.

[sthirthala]

Please log managed portal issues to Azure support team using Support + Help link in Azure portal and select Problem Type = Developer portal.

[gs11]

I can confirm that disabling React Developer Tools in Firefox resolves the issue for me as well.

[JakubHolovsky]

I am having the same issue on Edge however I don't have react tools installed. These are the only extensions enabled in my browser:

[KrisFrost]

Update: This does not look to be a Developer portal issue but rather injected extension code triggering an event listener created for the scenario of Authorization such as with Try It.

The developer portal code for the authentication registers an event listener receiveMessage.

return new Promise(((resolve,reject)=>{ try { window.open(oauthClient.code.getUri(), "_blank", "width=400,height=500"); const receiveMessage = event=>__awaiter(this, void 0, void 0, (function*() { if (!event.data.accessToken) return void alert("Unable to authenticate due to internal error."); const accessToken = event.data.accessToken , accessTokenType = event.data.accessTokenType; resolve(${utils_1.Utils.toTitleCase(accessTokenType)} ${accessToken}) } )); window.addEventListener("message", receiveMessage, !1) } catch (error) { reject(error) } }

Setting a break point here, and then stepping through, the code triggering these event is coming from content.js from editor extension in this case. Other extensions can be debugged the same way.

For the editor extension, what appears to be doing is a grammar check on the drop-down box for either the Authorization flow dropdown or the Subscription key drop down or all of them.

It's triggering the dev portals receiveMessage eventlistener. I did find I could go into the settings and changed "This can read and change site data" to When you click the extension. This prevents the issue as well.

Additionally, you could try experiment with turning off grammar or also exclude the developer portal domain from being used by the extension which is probably the best option and still have the extension available.