Open mat-patrickschmelter opened 9 months ago
Hi @mat-patrickschmelter did you find this solution? @tchiotludo can you help?
The problem still exists
Can you check this and see if updating the Keycloak configuration solves the issue ?
I don't know what could cause the issue on the AKHQ side as it seems to be deeply linked to the auth flow between micronaut and keycloak.
If it doesn't work, can you increase the logs to TRACE ? We will have more information about this auth flow
I have same isssue
Hello @AlexisSouquiere Patrick is not in at the moment, but we will check for the logs and reach out to you again
Same issue
Can you check this and see if updating the Keycloak configuration solves the issue ?
I don't know what could cause the issue on the AKHQ side as it seems to be deeply linked to the auth flow between micronaut and keycloak.
If it doesn't work, can you increase the logs to TRACE ? We will have more information about this auth flow
@qkhuyit, @marcosschroh please check my message above, try the possible fix from the Keycloak config and give more logs if it doesn't work
We still encounter the same issue after applying the changes you suggested to our keycloak. I will attach two log exports with trace logging enabled.
In the first case, the user sees an error message in the browser with the stacktrace including errorcode "invalid_grant". A workaround is to refresh the browser window - inclucing cache, and the user will be logged in https://pastebin.com/D0dgJEPK
The second case redirects the user to the /login/failed url, which leads to an endless loop if the user clicks "Login" again. Refreshing the page does not solve the problem. After some time the error disappears and the user is able to log in normally https://pastebin.com/nhgk58aZ
hi @AlexisSouquiere, the problem is still occurring. is there anything new here yet? many thanks in advance
@MaybeIknow is part of our team.
Any news on this Issue yet? We experience this problem since the beginning of the year and our users are slowly getting kind of nervous :)
We moved to a different project, I really recommend http://ui.docs.kafbat.io/
@mat-patrickschmelter, @MaybeIknow did you had a look to this ? It seems that people already had this kind of issue and had to force https scheme in the callback uri
I'm also trying to reproduce it on my side. It should fix the http instead of https issue but I don't know if it will fix the invalid_grant issue
We have implemented the suggested changes and will monitor the behavior for a few days
@AlexisSouquiere unfortunately, the issue still exists
Do you still have the two issues ? I mean the callback uri call with http and the invalid_grant issue ? Or did the config update fix the first one ?
Yes we still have both issues
I recommend use Kafbat https://github.com/kafbat/kafka-ui It is normally integrated with Keycloak
When trying to log in using a keycloak oidc provider, the first login succeeds. After waiting a few hours, the session gets invalid but cannot be closed correctly as it seems (by the way, even pressing logout will not end the session - thats another bug which cloud be related?). After pressing login again, the callback uri will be opened using http instead of https. After accepting the warning message in the browser, I get redirected to the https endpoint, reulting in the following error message:
AKHQ Config:
Trace Logs: https://pastebin.com/9q8wgDCX