Connecting Stash to JIRA for User Management Fails
After testing the connectivity between Stash and JIRA User Management, the connection fails in the UI and the following appears in the
2014-01-23 13:16:51,800 ERROR [http-bio-7990-exec-1] build 796x7756x0 15rk9g2 192.168.2.135,127.0.0.1 "POST /plugins/servlet/embedded-crowd/configure/jira/ HTTP/1.1" c.a.c.e.a.ConfigurationController Configuration test failed for user directory: [ ACM Corporation JIRA], type: [ CROWD ] com.atlassian.crowd.exception.runtime.OperationFailedException: com.atlassian.crowd.exception.InvalidAuthenticationException: Application failed to authenticate ... Caused by: com.atlassian.crowd.exception.InvalidAuthenticationException: Application failed to authenticate ...
2014-05-07 10:06:57,751 ERROR [scheduler_Worker-7] c.a.c.d.DbCachingDirectoryPoller Error occurred while refreshing the cache for directory [ 2097154 ]. com.atlassian.crowd.exception.OperationFailedException: com.atlassian.crowd.exception.InvalidAuthenticationException: Application failed to authenticate ... ...
In order to be able to connect Stash to JIRA User Management, you need to prepare JIRA and configure a specific user/password pair on it so that Stash can get connected for User Management purposes. In this case, the password being sent on the connection request from Stash to JIRA does not match what JIRA is expecting which causes the exception above to be thrown in Stash logs.
Please refer to it in order to reproduce this use case.
- Please review the step "1. Set up JIRA to allow connections from Stash" described in the Connecting Stash to JIRA for user management document. Check that the username and password pair you created for Stash is correct.
Making sure you remove/re-add JIRA as User management to your Stash instance will help you troubleshoot if the user/password is incorrect wither in JIRA or Stash.