Details
-
Bug
-
Resolution: Timed out
-
Medium
-
None
-
1.4.4
-
4
-
Severity 1 - Critical
-
1
-
Description
Hello everyone,
We have recently reviewed this issue and the overall interest in the problem. As the issue hasn't collect votes, watchers, comments, or support cases from many customers during its lifetime, it's very low on our priority list, and will not be fixed in the foreseeable future. That's why we've decided to resolve it as Timed Out.
Although we're aware the issue is still important to those of you who were involved in the conversations around it, we want to be clear in managing your expectations. The Crowd team is focusing on issues that have broad impact and high value, reflected by the number of comments, votes, support cases, and customers interested. Please consult the Atlassian Bugfix Policy for more details.
We understand how disappointing this decision may be, but we hope you'll appreciate our transparent approach and communication.
Atlassian will continue to watch this issue for further updates, so please feel free to share your thoughts in the comments.
Thank you,
Crowd Team
Using our internal OpenLDAP 2.3.35 server I have been able to replicate this issue. Once the OpenLDAP user is removed via Crowd, the user is NOT removed from group memberships. This causes the following exception when attempting to browse the group:
2008-07-30 12:13:48,429 http-8095-4 ERROR [console.action.group.ViewGroup] [LDAP: error code 32 - No Such Object]; nested exception is javax.naming.NameNotFoundException: [LDAP: error code 32 - No Such Object]; remaining name 'cn=groupuser,o=sgi,c=us' org.springframework.ldap.NameNotFoundException: [LDAP: error code 32 - No Such Object]; nested exception is javax.naming.NameNotFoundException: [LDAP: error code 32 - No Such Object]; remaining name 'cn=groupuser,o=sgi,c=us' at org.springframework.ldap.support.LdapUtils.convertLdapException(LdapUtils.java:155)
