Travis Cornwell commented on Oct 10, 2011

Re: Cleanup of deleted user Artefacts from WebSphere Portal and reestablish Unique ID binding on LDAP change

The CleanUpUsers procedure cleans up entries in the Release database, namely the USER_DESC table. The most common symptom for "when" to run CleanUpUsers is when assigning permissions, you see blank lines in the Resource Permissions portlet. This is often the sign two entries for the same user existing in the Release database. One of the entries is outdated and needs to cleaned up, the other is valid / still in use.

Most common reasons to run CleanUpUsers

1) You use common name (cn) as your primary Portal attribute. Somebody gets married. Their LDAP information changes from "John Doe" to "John Smith" ... you would need to cleanup the old "John Doe" entries. The "John Smith" entries would already be active / in use.

2) An entry is deleted in recreated in the same LDAP server. The external identifier of the LDAP will have changed in that case, and will cause a duplicate entry in the Portal database as a result.

3) An LDAP server migration, moving from one LDAP to a different one and data is not replicated between the LDAPs. Although the distinguished names of the users may remain the same, the external identifiers will be different, causing duplicate entries.

MemberFixer and User Transformation Tool (UTT) clean the JCR database, but not the Release database. CleanUpUsers cleans the Release database. CleanUpUsers should be run prior to run MemberFixer and/or the User Transformation Tool.

Melissa Howarth commented on Sep 23, 2009

More explanation

Could you please add a bit more explanation/introduction to this article about when and why you would use it. Thanks

Joe Breal commented on Sep 10, 2009

Replacement for MemberFixer?

Just curious if this process is meant to replace MemberFixer.

Also, what versions does this work with?

Thanks

Joel B Allen commented on Sep 10, 2009

Users in the DB

Note that users that aren't in the databases but are in the LDAP will not show up for clean up by this task. Only users which are in the database that need to be cleaned up will be present.

This may help some who expect a user to get cleaned up if that user has been removed from the LDAP but does not show up in the clean up user task. It's likely that the user was never created in the database because that user never authenticated to Portal, causing a database entry to be created.