Personal Space Disappears after Removing User from LDAP

Still need help?

The Atlassian Community is here for you.

Ask the community

Symptoms

After a user is removed from LDAP, that user's personal space in Confluence is no longer accessible

Cause

Unlike global spaces, Confluence associates a personal space with an existing username. If the user does not exist within Confluence, the personal space will become inaccessible.

Workaround

You can create a local user with the same username as the LDAP user:

  1. Log in as a local Confluence administrator (an account that is not from LDAP).
  2. Go to Confluence Admin > User Directories
  3. In order to add a local user, the Confluence Internal Directory is at the top position. Promote the directory to the top if it's not already.
  4. Go to Confluence Admin > Manage Users, and add a local user as desired. Be sure the username matches exactly with what the user was using before from LDAP.
  5. You can swap the directory order back to how it was after adding this user.

The missing personal space should once again become accessible since the username exists. Optionally, you can move the content into a global space so that it can be accessed even if the user is removed from Confluence.

 

Last modified on May 4, 2016

Was this helpful?

Yes
No
Provide feedback about this article
Powered by Confluence and Scroll Viewport.