LDAP synced user showing "User does not exist" with question mark by the user avatar
プラットフォームについて: Server および Data Center のみ。この記事は、Server および Data Center プラットフォームのアトラシアン製品にのみ適用されます。
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.
*Fisheye および Crucible は除く
要約
Individual users from LDAP are showing "User does not exist" on the user profile even though the user exists in Jira and username and email are populating correctly.
診断
- The user is unable to login to the Jira environment, even after performing a full sync.
- The user avatar shows a question mark and by hovering over the message "User does not exist" is displayed.
- Submitting a request on behalf of or adding as a request participant prompts an error to select a valid user.
- There is a deleted entry in the LDAP server for this user – the user was deleted and recreated on the LDAP server.
Verify the ObjectGUID being stored for the user in the Jira database is NOT the same as the LDAP server:
select EXTERNAL_ID from cwd_user where user_name = '<user>';
原因
LDAP syncronization is incorrectly mapping to the old external ID for the archived user record.
ソリューション
Fully remove the inactive user record with the queries in Delete user from database in Jira server and perform a full sync.
データベースの変更を行う前に必ずデータをバックアップしてください。可能であれば、まずステージング サーバーで、すべての変更、挿入、更新、または削除の SQL コマンドをテストしてください。
関連記事
- User does not exist error when trying to use, edit or delete an user
- "User Does not Exist" JQL Exception even when Providing Valid Users
- Jira throws error user exists but has no unique key mapping on login