If you are synchronizing two Jira instances (either Jira Server ↔ Jira Server or Jira Server ↔ Jira Cloud), you might have to adjust your network and firewall configurations. Check that in your Active Directory/Atlassian Crowd configuration, the sync user has the expected credentials.
Jira client login failed password#
Active directory or Atlassian Crowd is set up incorrectlyĪnother possible cause is that in your Active Directory/Atlassian Crowd config, your sync user has a different username and password to what you think. Furthermore make sure the password is set correctly for your sync user in all synchronizations which are using this userįor the sync user, we suggest setting the 'Maximum Authentication Attempts Allowed' setting to 5, to reduce the likelihood of this happening. If the problem reoccurs, login as an administrator and reset the failed login count for the sync user.Log in as your sync user, enter the Captcha, and then log out again.It's possible that the synchronization user cannot log in because a Captcha is required – this is probably because the credentials had been entered wrong before or have changed in the meantime, causing multiple failed logins. Sync user requires two-factor authenticationīackbone is not able to use a synchronization user that requires two-factor authentication to log in.ĭeactivate two-factor authentication for your sync userĬaptcha required for synchronization user If you are syncing a Jira Server with a Jira Cloud instance, generate an API token for the cloud instance's sync user and enter this in the password field rather than the password.The Sync User field contains the sync user's Jira username (for a Jira Server) or the user's email address (for Jira Cloud).
When creating a new sync or updating connection details for an existing one, you get an authentication conflict after entering the base URL and synchronization user credentials:
0 kommentar(er)
