-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
[user rules] Users are loosing their profil on synchronisation after update #15819
Comments
Hi, Are you using the same GLPI version on both servers, or is there a difference in GLPI versions, plugins, ...? |
yes, i added this to "anything else" : both REC and PROD have same system configuration, GLPI version, plugins, rules, LDAP connectors and profiles. The behavior on REC, if i summarize is that the default profile is not applied by my rule or not resolved to create the profil entry in the User. First though is that it looks like the behavior of my new user on production during login : no profil is deduced during sync of login and he is kicked out of GLPI. |
What is the |
Rule 1 : Criteria: Action:
Rule 2 : Criteria: Action:
Ordered like that. Simplest rule added by administrators to identify a specific group on multiple LDAP to assign a profil. After modification : Rule 1 :
Then I rollbacked and explained the change of behavior |
Just tried another simplier rule : With all other rules for users disabled, the new rule is : Criteria :
Action :
My users does not gain any dynamic authorization. Did i miss some other conf somewhere ? i see nothing on entity, Authentication conf or general conf that could impact it. "Test Rule" show a correct result. |
@cedric-anne ok, i've found a difference between REC and PROD : the profile As i'm seeing this, it is not the intended behavior : the default profile should have been applied from my rules and takes precedence unless the "default profile" on rule's action is only in the case of a user with multiple profile and not to be use on profile deduction and setted on user only in this case (which is disturbing). I also tried to define another "default profile" : this is the one assigned to users and authorization if i do not set any "profile" by rule. To summarize, what i understood of the mecanism of assigning an autorization to a user by rules :
If no entity specified by rule or any other configuration -> no autorization automaticaly added. From what i see, 2. is not real and just a confusion from me or a real bug. If not a bug, i have to edit my rules to comply and be less confusing for futur admins |
There has been no activity on this issue for some time and therefore it is considered stale and will be closed automatically in 10 days. If this issue is related to a bug, please try to reproduce on latest release. If the problem persist, feel free to add a comment to revive this issue. You may also consider taking a subscription to get professionnal support or contact GLPI editor team directly. |
Code of Conduct
Is there an existing issue for this?
Version
10.0.9
Bug description
Currently, we have assignment rules for users during LDAP import.
Rule 1 :
if user come from one of our LDAP, we assign
Self Service
for this explanation)Rule 2 (with multiple iteration for different profile but they are the same purpose and same kind of criterias) :
If user contains a specific keyword in '(LDAP) MemberOf', we assign :
Technician
for this explanation)Until now, and this behavior is still the same in production :
memberOf
have the profileSelf Service
for the entity andSelf Service
asdefault profile
Technician
as profile for the entity andTechnician
asdefault profile
I understood it was the correct behavior as the profile would be deduced from default profile and applied in list of profiles automatically.
Now, the issue, on my REC, I had to do some tests for a user that is not allowed to login due to a non-resolution of profile, even if it has one for the entity, during connection (Error message :
You don't have right to connect
).I tried to play with rules and at some point added an action to rule 1 (a thing i've tested some months ago) :
new action : "add profile
Self-Service
".Previously, this kind of action would have the following result :
memberOf
have the profileSelf Service
for the entity andSelf Service
asdefault profile
.Technician
andSelf Service
; default profile isTechnician
Now, I see this :
memberOf
have the profileSelf Service
for the entity andSelf Service
asdefault profile
. --> OKSelf-Service
for the entity andSelf Service
asdefault profile
, no moreTechnician
Profile
--> KOWeider :
I removed the "new" action such as i was in the same state as before and in production but now the result of sync is this one :
memberOf
have noprofile
for any entity and nodefault profile
--> KOTechnician
for the entity andTechnician
asdefault profile
--> OKEdit: precisions and rewording
Relevant log output
Page URL
No response
Steps To reproduce
No response
Your GLPI setup information
Informations sur le système, l'installation et la configuration
Server
GLPI constants
Libraries
LDAP directories
Locales overrides
Anything else?
Both REC and PROD have same system configuration, GLPI version, plugins, rules, LDAP connectors and profiles.
The text was updated successfully, but these errors were encountered: