You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
You can authenticate without redirect_uri param on the authentication page. In this case, authentication is possible on the server side only by not including the redirect_uri. I think this is a bit misleading as the documentation doesn't specify that this redirect_uri param is optional.
My proposal is If that param doesn't exist, sending a error or edit the documentation.
Create a oauth client that has callback uri
Go code authorization page without redirect_uri param
Do authorize
Goes to callback uri
From server side, sending POST /token (with request_uri params) throws invalid redirect_uri
redirect_uri is optional because the Client credential oauth flow doesn't require it.
For client_credentials it is, but for grant authorize_code I think it's different: if you look at the picture above, you can see that redirect_uri is not provided to get a token. Even though the authorization page actually redirected them to that redirect_uri.
Although I think I'd rather have the documentation only listing the endpoints for oauth2 and link to external oauth2 documentation (something like this maybe) for people who want to implement their own client instead of using existing libraries.
You can authenticate without
redirect_uri
param on the authentication page. In this case, authentication is possible on the server side only by not including theredirect_uri
. I think this is a bit misleading as the documentation doesn't specify that thisredirect_uri
param is optional.My proposal is If that param doesn't exist, sending a error or edit the documentation.
redirect_uri
paramThis is happened from my side:
redirect_uri
, Gets ErrorAfter removing
redirect_uri
param from reqClient:
The text was updated successfully, but these errors were encountered: