-
Bug
-
Resolution: Not a bug
-
Low
-
None
-
5.9.10
-
1
-
Summary
Users sync between Jira and Confluence is not successful after changing username on Jira side
Environment
- Confluence 5.9.10
- Jira 7.x
Steps to Reproduce
- Set a Jira instance with Internal Directory, create a user with username: 'BOSMADA'
- Set confluence and delegate authentication to jira and sync users
- Set and AD in Jira, crate a user with username: 'bosmada'
- Deactivate 'BOSMADA' from the Jira internal directory and change the user name to 'BOSMADA_internal'
- Sync Jira with AD, the new user is there and able to login
- Sync confluence with Jira
Expected Results
The new user bosmada from the JIRA AD should be in confluence and should be able to login
Actual Results
The new user bosmada from the JIRA AD is not synced and can't login
Workaround
flushing the cache and synchronizing again brings the new user to confluence, he is able to login.
[CONFSERVER-43177] Failed sync of user from Jira to confluence after changing the user name
dave.bosman2033919398 I am quite confusing now with the steps to reproduce
4. Deactivate 'BOSMADA' from the Jira internal directory and change the user name to 'BOSMADA_internal'
5. Sync Jira with AD, the new user is there and able to login
Could you confirm the steps to reproduce in the description correct?
Dave Bosman
added a comment - But it is the internal user that has been deactivated. NOT the AD user.
Without changing anything in JIRA it works again after the flushing of the cache in Confluence.
You might not find this a BUG but it is one, as seen that the software does not recognize the second (and active) user at that point.
Dave Bosman
added a comment - But it is the internal user that has been deactivated. NOT the AD user.
Without changing anything in JIRA it works again after the flushing of the cache in Confluence.
You might not find this a BUG but it is one, as seen that the software does not recognize the second (and active) user at that point. dave.bosman2033919398 From the description, the step 4 mentioned that we deactivated the user and rename the username
That is the reason why that username could not log in after the sync
Dave Bosman
added a comment - How do you come to the conclusion this is not a bug?
I would like to point out that the user that is imported from AD has the correct groups and is active when the problem occurs.
Also the problem solves when you flush the Cache in Confluence so to me it seems the problem is not at the JIRA side but at the Confluence side.
Best Regards,
Dave
Dave Bosman
added a comment - How do you come to the conclusion this is not a bug?
I would like to point out that the user that is imported from AD has the correct groups and is active when the problem occurs.
Also the problem solves when you flush the Cache in Confluence so to me it seems the problem is not at the JIRA side but at the Confluence side.
Best Regards,
Dave Dear All,
I believe this is not a bug. You should activate the account in JIRA that you want to log in with from Confluence
I am going to close this issue with "Not a bug" resolution. Please feel free to let me know if you have any kind of concern
Best regards,
Minh Tran
Confluence BugMaster
Atlassian
The steps mentioned are correct.
The Account you deactivate in step 4 is the internal account. At that point you are unable to see the AD user!
In step 5 you sync JIRA again with the AD server (or wait until he does it himself) and then the AD user shows up in the list.