Issue Summary

When the same username for a user is created by two external user directories(Crowd, LDAP), Confluence updates the last login dates for both of them each time, this behavior causes mismatched information between Crowd and Confluence DBs.
This is reproducible on Data Center: yes

Steps to Reproduce

1. Configure one Crowd user directory,
2. Configure one LDAP user directory,
3. Sync both of them, then login with a common user
4. Execute the below SQL query on Crowd DB:

   SELECT cwd_user.*,
          cwd_directory.id, 
          cwd_directory.directory_name, 
          cwd_user_attribute.attribute_value 
   FROM   cwd_user 
          join cwd_directory 
            ON cwd_user.directory_id = cwd_directory.id 
          join cwd_user_attribute 
            ON cwd_user.id = cwd_user_attribute.user_id 
   WHERE  cwd_user_attribute.attribute_name = 'lastAuthenticated' 
          AND cwd_user.user_name='username'
   

1. Execute the below  SQL query on Confluence DB:

   SELECT cu.*,
          cd.directory_name,
          li.successdate
   FROM logininfo li
   JOIN user_mapping um ON um.user_key = li.username
   JOIN cwd_user cu ON um.username = cu.user_name
   JOIN cwd_directory cd ON cu.directory_id = cd.id
   where cu.user_name='username'
   ORDER BY successdate;
   

Expected Results

The results should match on both Confluence and Crowd SQL queries.

Actual Results

Confluence SQL query shows both LDAP and Crowd user logged in at the same time. However, the Crowd SQL query shows a different date.

Workaround

Currently, there is no known workaround for this behavior. A workaround will be added here when available