-
Bug
-
Resolution: Duplicate
-
Low
-
None
-
3.6.1
-
None
-
None
Steps to reproduce:
1. Connect an AD with Stash via JIRA/Crowd and synchronise all the users across JIRA/Crowd and Stash
2. Rename a user in AD and sync across JIRA/Crowd and Stash
3. Upon sync to Stash, Stash creates another user as per screenshot
4. When trying to logging using the updated username, it gets stuck on /j_stash_security_check with an Error 500
2015-06-16 19:19:51,225 DEBUG [http-nio-7990-exec-3] @9D3RJRx1159x1004x0 oeklth 0:0:0:0:0:0:0:1 "POST /mvc/error500 HTTP/1.1" c.a.s.i.s.s.PluginAuthenticationProvider attempting authentication with authenticator com.atlassian.stash.stash-auth-crowd-sso:crowdSsoAuthHandler 2015-06-16 19:19:51,230 DEBUG [http-nio-7990-exec-3] @9D3RJRx1159x1004x0 oeklth 0:0:0:0:0:0:0:1 "POST /mvc/error500 HTTP/1.1" c.a.s.p.a.c.i.CrowdSsoAuthenticationHandler Skipping Crowd SSO as it is not enabled 2015-06-16 19:19:51,230 DEBUG [http-nio-7990-exec-3] @9D3RJRx1159x1004x0 oeklth 0:0:0:0:0:0:0:1 "POST /mvc/error500 HTTP/1.1" c.a.s.i.s.s.PluginAuthenticationProvider attempting authentication with authenticator com.atlassian.stash.stash-authentication:crowdHttpAuthHandler 2015-06-16 19:19:51,230 DEBUG [http-nio-7990-exec-3] @9D3RJRx1159x1004x0 oeklth 0:0:0:0:0:0:0:1 "POST /mvc/error500 HTTP/1.1" c.a.s.i.user.DefaultUserService Authenticating user: _Stash-JIRA-AD_renam
5. In the cwd_user table, it shows the two users which are active
Workaround
Recreate the user directory to "refresh" the cwd_user table
- derived from
-
BSERV-5244 Unique key constraints not working for Embedded Crowd table cwd_user
- Closed