Which case user_key in table app_user has value as ID?

[Tran Tuan Duong]

I queried data in app_user table and found that almost cases user_key = lower_user_name.

However some cases user_key field value is ID##### (##### is value of ID field).

Example:

• ID = 12345
• user_key = ID12345
• lower_user_name = duongtt

Let's try:

SELECT * FROM `app_user` u WHERE u.`user_key` LIKE '%ID%'; 

I ensure that all users logged in with their username.

Which case user_key in table app_user has value as ID?

[naveen_nayak]

This may be due to GDPR changes in JiraServer 8.2 

https://confluence.atlassian.com/jiracore/gdpr-changes-in-jira-975041009.html

[Payne]

user_key holds the original value of lower_user_name. If the username ever changes, that will be reflected in lower_user_name, but user_key will always hold the original value.

As to why it is sometimes ID#####, I would that has something to do with anonymous access at some point?

[Tran Tuan Duong]

Thank for your answer. My system is configured to avoid anonymous access.

And in my point of view, with anonymous access, how the system know to update low_user_name :)