-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Token endpoint response error in the authorization code flow. #120
New issue
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
Labels
status: invalid
An issue that we don't feel is valid
Comments
Please see #102 (comment) . He said invalid issue. |
@lizhongyue248 Thank you. Seems to be a duplicate issue, I will look at your issue later. |
@vincent-hsin It's not clear to me the issue you are having. Please provide more details if you want me to look into this issue. Detailed steps to reproduce or ideally a minimal sample. |
vincent-hsin
added a commit
to vincent-hsin/spring-authorization-server
that referenced
this issue
Sep 25, 2020
Closing as per comment |
vincent-hsin
added a commit
to vincent-hsin/spring-authorization-server
that referenced
this issue
Oct 12, 2020
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
It response error when I request token endpoint with code and client_id parameters in the authorization code flow. But it reponse the expected result without client_id parameters.
To Reproduce
{
"error": "invalid_client"
}
Expected behavior
{
"access_token": "eyJraWQiOiIzYjEzOTg3Yi05Mjk3LTRkOWQtOTdkOC02MWVlY2ZjMmFlZTQiLCJ0eXAiOiJKV1QiLCJhbGciOiJSUzI1NiJ9.eyJzdWIiOiJ1c2VyMSIsImF1ZCI6Im1lc3NhZ2luZy1jbGllbnQiLCJuYmYiOjE2MDA5NDA2MjIsInNjb3BlIjpbIm1lc3NhZ2UucmVhZCIsIm1lc3NhZ2Uud3JpdGUiXSwiaXNzIjoiaHR0cHM6XC9cL29hdXRoMi5wcm92aWRlci5jb20iLCJleHAiOjE2MDA5NDQyMjIsImlhdCI6MTYwMDk0MDYyMiwianRpIjoiYTg3ZWYwNTMtNjE0NC00NmI2LWI3M2YtZjJiMDA3NzYxNWE1In0.UsyIWPgODPIo-Ol5RmVt3tLUovBaFgJcKS4P2HJ7Cz6usNUG9UJUt_gATHAZ6CzDeFPTPw9zXwhRUGzCJChLfWSw-u6khvV91QwaB1sLzIsVEHR4tWNJULMsaaJLZtZz4BdP-_GHUFnxazxnPdpGqng035RbOoe7l8F0Ie9ObHIc2-H2MCaCIxbFbH7zpxsY2yStzUE0VILJnb8hi7kV8p3F7LsBrCM8f1SvwJR60VFoSIZhL7aaQVd9rfGpLNVgONadCEvFjHarN03JUcRUQG2YdDkDoul6MZtipnB8Cra1h9VFX7jn4vN7VPlel9HmFKLfeIVqNB2VBx7-EYEXwg",
"scope": "message.read message.write",
"token_type": "Bearer",
"expires_in": "3600"
}
The text was updated successfully, but these errors were encountered: