Summary

When a user logs in via a delegated directory, Confluence creates a USERINFO record in the content table, and submits that for re-indexing. This allows the newly logged in user to be mentioned, and visible in the people directory.

If the USERINFO record exists (because a connector type directory was used previously), then the record will not be submitted for reindexing.

Scenario1 : Confluence - LDAP

Steps to reproduce

1. Setup Confluence with a Connector to an LDAP directory, and sync it.
2. Remove the LDAP directory, shut down Confluence and delete the index folder
3. Start Confluence, and rebuild the index
4. Verify you can mention a user on a page, but when you attempt to save the page, Confluence reports A link in the editor with the alias '<user name>' could not be found. The resource may no longer exist.
5. Subsequent attempts to mention that user produce no results
6. Create a delegated LDAP directory with the same settings
7. Log in as the same user you attempted to mention in Step 4
8. Attempt to mention this user, or search for the user in the people directory

Expected Results

The user should be mentionable, and visible in the people directory

Actual Results

The user can't be found or mentioned until a reindex is performed.

Scenario2 : Confluence - Crowd

Steps to reproduce

1. Setup Confluence and Crowd that contains a user that does not belong to any groups, and sync it
2. In Crowd, go to Application setting, add "confluence-users" into the Automatically assigned to list
3. In Confluence User Directory settings, make sure that the "Update group memberships when logging in" has been set to "Every time the user logs in"
4. In Confluence, attempt to mention the user

Expected Results

The user should be mentionable, and visible in the people directory

Actual Results

The user can't be found or mentioned, not visible in the people directory until a reindex is performed.

Investigation Notes

We discovered through debug logging that although the user logs in, no submission is made to the journal.
By right, as the user's group membership of this user will be updated on login, Confluence should've add an entry to the journalentry table for this user detail's changes to be reindexed.
There's also a cache or something of usernames, as the user is visible in the mention list (after the connector is removed) but as soon as we attempted to mention that user the entry was removed and subsequent mentions failed.

Confluence should submit the USERINFO record regardless of if it was created or if it existed.