We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
There is no error handling for the PKCE token request, and the request that is attempted is also not shown in the UI.
The PKCE token request can fail, for example, if there is no CORS-setting on the server for oauthdebugger.com.
The request should be shown, and the errors should be caught and displayed.
Nevertheless, very useful tool. A little bit surprised it requires a server component, though.
The text was updated successfully, but these errors were encountered:
There is no error handling for the PKCE token request, and the request that is attempted is also not shown in the UI. The PKCE token request can fail, for example, if there is no CORS-setting on the server for oauthdebugger.com. The request should be shown, and the errors should be caught and displayed.
This is a good suggestion, thanks!
A little bit surprised it requires a server component, though.
I tried to eliminate this, but a server is required for handling POST-based redirect flows.
Sorry, something went wrong.
No branches or pull requests
There is no error handling for the PKCE token request, and the request that is attempted is also not shown in the UI.
The PKCE token request can fail, for example, if there is no CORS-setting on the server for oauthdebugger.com.
The request should be shown, and the errors should be caught and displayed.
Nevertheless, very useful tool. A little bit surprised it requires a server component, though.
The text was updated successfully, but these errors were encountered: