Repository navigation
Noise in Keycloak logs, "missing parameter: response_type" #46460
Replies: 1 comment 2 replies
|
I don't think the errors are noise in this case. From the logs you're showing, it seems like Keycloak has logged an invalid request, since it did not contain a required parameter (the It looks like the messages here are simply generated by user error, since the web UI page clearly states that they should close the tab. Regarding the |
|
I assume that response_type was previously in the authorization session, but this data was deleted after login. The logged-in user's session no longer has this information. This parameter can also be in the URL, but in the URL I have client_data={}. I think the problem is somewhere between checking the cookie/session and the client data from the URL. |
|
I don't think any data is lost, but instead when trying to use the "back" button, the browser is trying to access a previous page using the wrong method. Keycloak likely uses POST requests to send the authorization requests, but when the browser is trying to go back it will use the GET method - the back button acts like a "new" visit to a specific URL but the browser will not reuse the method and specific parameters that were sent with the original request. Since GET expects all parameters in the URL, and POST (usually) sends them in the request body, Keycloak sees the new request as not having any parameters. This behavior is not uncommon, and you may see errors like "this page is expired" when using the back button in certain cases. As mentioned in section 3.1 of OAuth2 (https://datatracker.ietf.org/doc/html/rfc6749#section-3.1), the authorization endpoint must support GET, and POST is optionally supported. Please check the network tab of your browser to see what requests are being sent during the authorization phase and then when clicking on the "back" button; maybe we'll have more to work with. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I would like to raise the topic of error logging, because I have the impression that some error logs are actually "noise".
After the user successfully logs in via Device Authorization Flow, a success screen is displayed.
When the user clicks the "back" button in the browser, an ERROR entry appears in the Keycloak logs.
Logs:
I understand WARN, but I don't know why ERROR in this case.
invalida_requestis not translated btw, maybe a bug.All reactions