Personal Space Permissions post LDAP Transition

[Atlassian Admin]

Greetings,

Originally, our Confluence deployment was on a Windows server using Confluence-local users and groups. We later anted up for a larger license and migrated Confluence to a CentOS server with LDAP integration. This migration also featured a series of username changes in LDAP because the names were out of compliance with revised corporate standards.

In its entirety, Confluence seemed to handle this process pretty well with only some minor snags concerning LDAP group permissions. However, we seem to have lost the visibility or use of Personal Spaces. I'm told that prior to the LDAP migration, each user in our enterprise had a Personal Space configured and active. Once the transition occurred, not only did users evidently lose access to their Personal Spaces, it's almost as if they were deleted. I wouldn't have thrashed too much about this except for the fact that we're sampling a CalDAV plugin for Confluence that may rely on Personal Space permissions for private calendars to merge upstream with team calendars.

Being the newest Confluence user, and having come onboard after the LDAP migration, I was able to create a Personal Space and grant it visibility to everyone. However, only one associate can see my space. Furthermore, another user who existed prior to the LDAP change was somehow able to recreate his Personal Space, but even with the page permissions set to enable viewing for all users, only him and myself are able to see his space.

I've had no luck browsing the official documentation, and it's not obvious from within the configuration management console where one goes to begin diagnosing this issue, if it even can be diagnosed from there. Any advice on this matter would be appreciated.