Closed janzen01 closed 1 year ago
Thanks for reporting the issue. I will look into it.
The behavior you're observing is actually expected due to the nature of OAuth 2.0's Implicit Grant flow. In the "Implicit" grant flow, the access token is sent as a URL fragment (#access_token=token). According to HTTP specifications, the fragment part of the URL is never sent to the server; it's designed to be processed client-side.
This means that when you authorize using an external browser, the browser itself will not forward this fragment back to the plugin, thus it can't be automatically imported.
There are two ways to work around this:
Thank you for your investigation. I will look into it. :)
Describe the bug I configured OAuth 2 Implicit Grant flow via Microsoft Entra. The Access Token call was successful, and Entra issued an Access Token, but this token was not loaded to the plugin config.
Steps to reproduce
Expected behavior After hitting the button, Call Auth Service and automatically import obtained token to the plugin configuration.
Environment information: