"Location Attribute Sync Issue in LDAP Configuration"

[CLcdiazp]

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

GLPI 10.0.15

Bug description

In the LDAP server configuration for users, the default settings include the following AD attributes:"
Surname: sn
Email: mail
Given Name: givenname
Title: title
The root rule is:

Global Criterion - LDAP Server is Server Name
Actions: Action Entity assign Entity > Subentity
This ensures that when the LDAP is synchronized, the username, Surname, Email, and Title are synchronized in the subentity, and this process works correctly.

However, when adding a location attribute configuration:

Surname: sn
Email: mail
Given Name: givenname
Title: title
Location: l
Upon synchronization, the location is loaded into the root of the entity rather than the subentity.

When checking the root rule, I noticed that the location criterion is missing from its criteria.

LDAP Criteria:

(AD) User ID
(LDAP) MemberOf
(LDAP) Title
(LDAP) Common Name
(LDAP) Department Number
(LDAP) DistinguishedName
(LDAP) Email
(LDAP) Employee Number
(LDAP) Manager
(LDAP) Organization
(LDAP) Telephone Number
(LDAP) User ID
Object Class
Therefore, if I add the parameter l in the LDAP server's location, it will load it into the root entity, which has caused a problem for me.

I'm not sure if this is a bug.

Let me know if you need any further assistance!

Relevant log output

No response

Page URL

No response

Steps To reproduce

No response

Your GLPI setup information

No response

Anything else?

No response

[github-actions]

This issue has been closed as we only track bugs here.

You can get community support on forums or you can consider taking a subscription to get professional support.
You can also contact GLPI editor team directly.