-
Bug
-
Resolution: Unresolved
-
Medium
-
None
-
2.0.7, 2.4, 2.8.3, 2.8.4, 2.10.1
-
Crowd with LDAP as backend, LDAP administration by Collax Businness Server
-
23
-
Severity 3 - Minor
-
5
-
When we change in Collax a user to "inactive", this state is not reflected in the crowd database.
The proposed workaround is to remove the user from ldap and re-create the user on crowd. The result is two directories of users in one company. Administration, search, migration will become error-prone and is not acceptable for us. After using crowd with LDAP for about 2 yours, we get to our licence-limit of 100, where the active users are about 70 users.
Steps to reproduce:
- install Crowd
- Create new Directory connecting to OpenLDAP using Connector
- try to disable any user sync from OpenLDAP by unchecking the Active checkbox
Expected Behaviour:
User will be disactivated
Actual Behaviour:
Crowd indicate update is sucessful, but the user remain active
Environment:
Crowd connected to OpenLDAP
Notes
This is not reproducible when Crowd is connecting to Microsoft AD
- causes
-
JRACLOUD-34557 Jira should read from OpenLDAP a flag to make users inactive
- Closed
-
JRASERVER-34557 Jira should read from OpenLDAP a flag to make users inactive
- Gathering Interest
- is related to
-
JRASERVER-65467 Jira should read from FreeIPA a flag to make users inactive
- Closed
-
CWD-2033 "Active" flag for groups does not work / support deactivating groups
- Closed
-
CWD-5533 Support sync for active/inactive status with Novell eDirectory
- Gathering Interest
-
CWD-1740 Support changing active status (activating/deactivating) for users in ApacheDS directories
- Gathering Interest
-
CWD-1930 Add UI to bulk Activate/Deactivate users
- Under Consideration
- relates to
-
CWD-995 Provide Crowd support for Active Directory's "Account Disabled" flag
- Closed
- is cloned by
-
KRAK-4556 Loading...
- links to