Skip to content
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

Ldap sync deletes permissions and profiles #15102

Closed
2 tasks done
FreeMacs opened this issue Jul 4, 2023 · 9 comments
Closed
2 tasks done

Ldap sync deletes permissions and profiles #15102

FreeMacs opened this issue Jul 4, 2023 · 9 comments
Labels

Comments

@FreeMacs
Copy link

FreeMacs commented Jul 4, 2023

Code of Conduct

  • I agree to follow this project's Code of Conduct

Is there an existing issue for this?

  • I have searched the existing issues

Version

10.0.7

Bug description

We use an Ldap sync cron job that syncs all users once a day. Permissions and profiles are removed and only reassigned when people log in.

We use the following rules to assign identities and profiles to the synchronized users.

RULE OPERATOR = and

Screenshot 2023-07-04 093437

The first four rules are used for the IT department employees, while the last rule is for all other users who should not log in but still need to be present in GLPI for assignments.

The only rule executed during LDAP sync is the last one, which has "no rights". The other rules are applied only when the user logs in, which means that IT department employees have no rights and no assignments until they log in.

The individual rules are executed correctly. However, when I perform a complete test of the rule set, only the last one with "no rights" is executed. What could be the reason for this?

Just to clarify, I want all rules to work directly during LDAP synchronization and not just when users log in. Similar to the "No Rights" rule. Because if the users have no entity and no permissions, they are also not available for selection, for example, for assets or tickets. Even if the group assignment is missing, the users won't receive notifications until they log in again, and that could be too late in many cases.

And I have one more question or problem. When the LDAP sync is performed, all users are logged out. Is there a way to prevent that from happening?

Relevant log output

No response

Page URL

No response

Steps To reproduce

No response

Your GLPI setup information

No response

Anything else?

No response

@trasher
Copy link
Contributor

trasher commented Jul 4, 2023

Please try on latest 10.0/bugfixes nightly build.

@FreeMacs
Copy link
Author

FreeMacs commented Jul 7, 2023

I have updated to the latest version 10.0.8 and I still have the same problems.

I have also found out that all rules with '(LDAP) ...' only work when logging in and not during the sync itself.

image
image

They also don't work when I test the rule set.

Please help!

@cedric-anne
Copy link
Member

Hi,

Rules should act the same whether they are processed during mass sync or during authentication. I do not have time to try reproduce this issue right now, so I cannot confirm the issue.

They also don't work when I test the rule set.

The rule test feature is not working with LDAP criteria. This bug has already been identified in #14059, but I have not been able to fix it yet.

@github-actions
Copy link
Contributor

github-actions bot commented Oct 2, 2023

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.
If it is related to a new feature, please open a topic to discuss with community about this enhancement on suggestion website.

You may also consider taking a subscription to get professionnal support or contact GLPI editor team directly.

@github-actions github-actions bot added the Stale label Oct 2, 2023
@cedric-anne
Copy link
Member

Hi @FreeMacs ,

Could you try with 10.0.10 (many bugs related to LDAP have been solved), and maybe also apply the #15635 patch?

@trasher
Copy link
Contributor

trasher commented Oct 13, 2023

Ne feedback from a while, closing

@trasher trasher closed this as completed Oct 13, 2023
@FreeMacs
Copy link
Author

FreeMacs commented Nov 7, 2023

sorry i only saw this now, this problem still exists as of today

Copy link
Contributor

github-actions bot commented Jan 7, 2024

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.
If it is related to a new feature, please open a topic to discuss with community about this enhancement on suggestion website.

You may also consider taking a subscription to get professionnal support or contact GLPI editor team directly.

@github-actions github-actions bot added the Stale label Jan 7, 2024
@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Jan 17, 2024
@FreeMacs
Copy link
Author

This problem still exists

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants