'Orphaned' personal spaces after the LDAP user has been removed

[Paul Paul]

I have a problem with personal spaces being left in Confluence after a user has been removed from the network. Authentication and users via LDAP. I had assumed that when a user is removed from the LDAP source I would still get to delete the user from Confluence and this would therefore remove the personal space. Recently I am finding that the user no longer exists in Confluence and yet the space is still present - when I am informed they are removed from Active Directory I find there is no user record in Confluence at all. Has anyone else seen this problem?

One oddity I find is that the pages from the Space have already been deleted - would this somehow break the link between space and user if no authored content remained?

[Bruna Griebeler]

If you're having trouble with Orphaned Pages, you can remove them or "give them" to another user (as creator):

Check this KB more more info about it: https://confluence.atlassian.com/display/DOC/Managing+Orphaned+Pages

Cheers!

[Steve Rhodes]

We are 5 years down the line and I have this exact problem in Confluence 5.10. User is gone from LDAP but his personal space is still there. User not in the People Directory anymore, but personal space and all pages still available. The permissions on the space are the default from when the personal space was created.

[JamieA]

This sounds highly related to this jira issue/question: https://answers.atlassian.com/questions/12956/jira-full-ldap-integration-how-do-you-deal-with-retiring-users.

I think Atlassian have somehow missed dealing with this.