[
https://issues.apache.org/jira/browse/JS2-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ate Douma resolved JS2-1068.
----------------------------
Resolution: Fixed
Fix Version/s: 2.2.1
This is not really a bug but the side-effect of some default/example LDAP
configurations provided by Jetspeed.
You should validate and setup the proper configuration used for mapping to
LDAP.
I already removed the uid=foobar example configuration some time ago so I
consider this "issue" fixed.
> LDAP When last user is removed from a role a uniqueMember with uid=foobar is
> left
> ---------------------------------------------------------------------------------
>
> Key: JS2-1068
> URL: https://issues.apache.org/jira/browse/JS2-1068
> Project: Jetspeed 2
> Issue Type: Bug
> Components: LDAP
> Affects Versions: 2.2.0
> Environment: Linux with the Fedora Directory Server
> Reporter: Christopher Marshall
> Priority: Minor
> Fix For: 2.2.1
>
>
> When using the Jetspeed admin interface with Jetspeed configured to use LDAP
> and the last user is disassociated or removed from a role Jetspeed does not
> remove the uniqueMember attribute but instead changes the value to be
> "uid=foobar". This seems like a strange piece of trash to leave around in a
> directory.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
