-
Bug
-
Resolution: Fixed
-
Medium
-
2.7, 2.7.2
-
None
-
Standalone Application
Apache Tomcat/7.0.40
Ubuntu Server 12.04 LTS
Java: 1.7.0_45
First of all: We have installed the version 2.7.0. I can't find this one in your "Affects Version" list.
Most of the description you can find here in this answer: https://answers.atlassian.com/questions/296167/crowd-removing-group-from-user-with-in-username-results-in-error?page=1
We are using Crowd for custom applications. Underlying directory is Open-LDAP running on the same server as the crowd installation.
My last post in the answer identifies the main problem:
I tested with activated caching function for LDAP-Directory for a user with already existing group.
1. Removed Group from user
2. Error occurred but group was removed in the crowd web console
3. Looked direcly into LDAP. Group was still attached to the user!
4. Clicked on synchronisation
5. On crowd web console: Group was readded to user by synchronisation
So the problem seems to be with the LDAP connector.
It is customer requirement for this username format and very important that crowd supports this. Our customer bought the biggest license and wants to migrate from another system to crowd.
With this bug we have a showstopper!
![[Extranet] Page](/images/icons/generic_link_16.png "[Extranet] Page"){kind=icon}
[CWD-3923] Removing group from user account with '#' in username results in error
| Workflow | Original: Simplified Crowd Development Workflow v2 - restricted [ 1510936 ] | New: JAC Bug Workflow v3 [ 3365628 ] |
| Status | Original: Resolved [ 5 ] | New: Closed [ 6 ] |
| Workflow | Original: Simplified Crowd Development Workflow v2 [ 1392429 ] | New: Simplified Crowd Development Workflow v2 - restricted [ 1510936 ] |
| Workflow | Original: Crowd Development Workflow v2 [ 687866 ] | New: Simplified Crowd Development Workflow v2 [ 1392429 ] |
Avi Knoll (Inactive)
made changes -
| Remote Link | Original: This issue links to "Page (Extranet)" [ 66421 ] | New: This issue links to "Page (Extranet)" [ 66421 ] |
Avi Knoll (Inactive)
made changes -
| Remote Link | Original: This issue links to "Page (Extranet)" [ 66421 ] | New: This issue links to "Page (Extranet)" [ 66421 ] |
| Fix Version/s | New: 2.8 [ 36896 ] |
Lutz Galich
added a comment - We tried to fix this by changing the spring-LDAP-jar directly in the WEB-INF/lib from version 1.3.1 to 1.3.2. After that we restarted the crowd-server.
Result: The bug is NOT fixed.
We know that this is not the common way to do this, but we need a hot fix for this bug!
Lutz Galich
added a comment - We tried to fix this by changing the spring-LDAP-jar directly in the WEB-INF/lib from version 1.3.1 to 1.3.2. After that we restarted the crowd-server.
Result: The bug is NOT fixed.
We know that this is not the common way to do this, but we need a hot fix for this bug! Lutz Galich
added a comment - Could you estimate the date of next Crowd release? This fix will be present in the next release of Crowd. With naive matching disabled, the only change is to upgrade Spring LDAP from 1.3.1 to 1.3.2.
> We know that this is not the common way to do this, but we need a hot fix for this bug!
Can you follow up with Support, please? They'll be better placed to take a look at your specific case.