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
Missing setup streams and user dashboards after entering through the active directory #2516
Comments
@angelsedoy Are you completely sure that the user names are identical? Keep in mind that user names in Graylog are case-sensitive, so "user1" is not identical to "User1". |
I think that I have checked everything. Accounts only AD. Members include, but are taken to a page "No streams configured.". |
Could you please provide a dump of your user collection in mongodb after you logged in with a user? |
first login
Add stream and dashboard
again log in
|
Hello!
|
Ah I see. This happened during a bugfix in 2.0.0 beta.3 apparently 9b746fa We should merge the permission list, rather than overwriting them with the empty list. Thanks for the input! |
@angelsedoy the workaround should be to create a role for this user and then assigning it. |
@kroepke , I think it does not work
It would be useful to keep this possibility, I understand that it is necessary to set right through Active Directory, but in some cases it is convenient to carry out authorization through Active Directory and give rights to GL |
I'm having a similar issue RE: this but I"m not sure if its a bug or a potential feature in the future. I have a LDAP + group mapping setup on GL 2.1.2 for our users. A typical flow would be:
My only workaround this is to disable group mapping totally and manually add permissions for them. |
@davidchua please update to the latest release and check if the problem still present. Additional please do not highjack old closed issues. If the problem is present in the latest release please open a new issue with a reference to this. |
In #2529, while fixing #2516, persisting all permissions of roles assigned to a user was reintroduced (fixed in 35c9325 before). This happened due to the introduction of a temporary variable that was not used effctively. After this change, LDAP permissions are not modified blindly but the permission set of a user still stays denormalized when modified and saved.
In #2529, while fixing #2516, persisting all permissions of roles assigned to a user was reintroduced (fixed in 35c9325 before). This happened due to the introduction of a temporary variable that was not used effctively. After this change, LDAP permissions are not modified blindly but the permission set of a user still stays denormalized when modified and saved. (cherry picked from commit 1f2aeb5)
In #2529, while fixing #2516, persisting all permissions of roles assigned to a user was reintroduced (fixed in 35c9325 before). This happened due to the introduction of a temporary variable that was not used effctively. After this change, LDAP permissions are not modified blindly but the permission set of a user still stays denormalized when modified and saved. (cherry picked from commit 1f2aeb5)
In #2529, while fixing #2516, persisting all permissions of roles assigned to a user was reintroduced (fixed in 35c9325 before). This happened due to the introduction of a temporary variable that was not used effctively. After this change, LDAP permissions are not modified blindly but the permission set of a user still stays denormalized when modified and saved.
Problem description
After obnovlenyai from 1.7 to 2.0 version, settings are lost after entering through Active Directory. So it should be, or am I doing something wrong? Previously, it was possible to adjust the stream and dashboards for each individual.
Steps to reproduce the problem
Environment
The text was updated successfully, but these errors were encountered: