The 'Last Authenticated' status for a user is displayed as 'Unknown' in the Bitbucket Server
Platform notice: Server and Data Center only. This article only applies to Atlassian products on the Server and Data Center platforms.
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Summary
When reviewing the user, the Bitbucket Server shows the status of the user's most recent authentication as 'Unknown'.
Environment
Tested on Bitbucket Server 7.21.7
It applies to most of the Bitbucket Server versions.
Cause
This is as per the behaviour of the product. The users who are shown as Unknown have either never logged into Bitbucket or are not licensed, any user who has logged into Bitbucket or has cloned via HTTPS or SSH will have the Last Authenticated field updated.
Solution
This behaviour generally occurs when users are configured through LDAP Active Directory Synchronization with Bitbucket and users who are not required in Bitbucket are visible but will never log in to Bitbucket. In such a condition, filter condition to fetch users needs to be improved in a way that users will not occur to Bitbucket through synchronization.
Note: In Bitbucket, the Last authenticated time is updated every time a user is authenticated by the Bitbucket and the value is updated on the cwd_user_attribute table. The user who is shown with the Last authenticated time as Unknown will not have an entry on the cwd_user_attribute table.