- Sponsor
-
Notifications
You must be signed in to change notification settings - Fork 694
Login not authorized when a user belong to two groups #524
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
Comments
Can you share the configuration files please to have a direct reproduction please ? |
Here is my config :
|
Please format or join as file please |
it's now formatted |
Very strange, without changing nothing sometimes I succeed to connect ! And after disconnecting it doesn't work again |
Can you try with last |
Yes I can, but I think I have to change the format of my yml file no ? |
Yes, the same than before a map of groups instead of list of groups, like at the application example there is admin group for example |
I test the dev version after adapting the config file but the behavior is the same. |
I have a clue, maybe the length of the field topics-filter-regexp. What is the limit for this field ? |
no limits as I know 🤔 |
It seems yes, I made several test and with 2636 characters it's ok, after not |
is there a possibility to define a list of regex instead of a long unique one ? |
Strange behaviour here ! |
If I put : topics-filter-regexp: >- Only the TOPIC1 is available |
don't use enter, just trying with | because I think there is no limit on size |
like that ? topics-filter-regexp: "TOPIC1|TOPIC2" |
like that : topics-filter-regexp: >-
TOPIC1|TOPIC2 |
OK, so it's working with 2 topics but when I put the problematic line I obtain the same error |
I don't have this problem in 0.12.0 |
What is the exact error ? |
When I'm on login page and click on "Login", I got "Wrong Username or Password", but it's the good one. It occurs only when the topics-filter-regexp of my ldap family have a value longer than 2636. |
I have made some try to reproduce your issue and I'm not able. |
Hi, I finally install the last version of akhq (0.17.0) to do more testing and I still have the same issue.
With this configuration, if I try to connect with "admin1" it works fine. For information, admin1 and admin2 users have the same password. I hope with all these information you will find the problem. Thanks |
Hi, Finally I now use the right jar file :) And with this previous config file I got the same error when I try to connect.
With 66 it's ok ! |
Please give me a docker compose file to reproduce the issue, I never have the issue on my side |
I'm sorry, I don't know how to make a docker compose file, but I reproduce the same behaviour on a docker instance by running this command : docker run -d -p 8080:8080 -v /tmp/kafkahq.yml:/app/application.yml tchiotludo/akhq:dev with following /tmp/kafkahq.yml :
With admin1 login with old fashion topics-filter-regexp it works because I'm under the length limit (if I add some topics it failed). Normally you should have the same behaviour with the same docker file and same config yml file, no ? |
Hi,
I have the ldap authentification configured and I have an issue since I update from 0.12.0 to 0.16.0
My user belong to two groups defined into the yml and the connection issue is related to that.
If I remove one of the groups than I can connect, otherwise I have an error "Wrong Username or Password!"
If I rollback to 0.12.0 I don't have this issue.
Regards
Alain
The text was updated successfully, but these errors were encountered: