Details
-
Bug
-
Status: Closed
-
Resolution: Fixed
-
6.2.X EE, 7.0.X, 7.1.X, 7.2.X, 7.3.X, Master
-
5
-
3
-
Regression Bug
Description
LPS-36213 prevent any user which is not in "approved" status from being exported to LDAP. This is too broad brush, because it then prevents "deactivated" users from being exported.
This causes unexpected behavior when LDAP export is enabled to use portal to manage a LDAP directory. For example see scenario described in LPS-30516.
Likewise, if both LDAP export & import is enabled, then users that are deactivated on portal will get re-activated upon the next LDAP sync / login. The expectation is for a two way sync between portal & LDAP.
Steps to reproduce:
- Configure LDAP with export enabled. Take care to map the "Status" portal user attribute to an appropriate LDAP attribute. (consider recycling the "roomNumber" from the Person schema maybe)
- Create a new user [email protected]
- Assert that this user now exists in the LDAP directory and has the status of 0 (i.e. "approved")
- Deactivate the user in portal
Expected outcome: The user now has a status of 5 (i.e. "deactivated")
Actual outcome: The user remains untouched in the directory
Attachments
Issue Links
- is caused by
-
LPS-36213 Unapproved accounts are being exported to LDAP
- Closed
- split to
-
LPS-133570 Test coverage for LPS-127989
-
- In Progress
-