This seems like it should be straight forward.
I've set up JIRA with an apache front end, so my <context path="JRA" ...=""/> in JIRA. It's accessible both at http://myserver.tld:8080/JRA and http://myvhost.tld/JRA. When setting up confluence, I want to use JIRA as my user repository (JIRA is using delegated LDAP w/internal directory).
I've tried all variations of JIRA URL's (virtual host, actual host, tomcat port, apache port ...) and I get the same error:
connection test failed: Response from Server:
com.atlassian.crowd.exception.InvalidAuthenticationException: Application failed to authenticate
I'm using the default admin credentials I set up when setting up JIRA for Application Name and Application Password, but no joy.
Sorry to hear you experiencing such issue on your instance. Judging from the provided information, it seems that the credential used by Confluence in order to access JIRA user management framework is incorrect.
As mentioned on this documentation, may I know if you have done the following steps
Go to your JIRA administration screen and define the Confluence application to JIRA:
6. Save the new application.
Could you please let us know if you have used the application named and password configure on step number three on Confluence side?
Again as mentioned earlier,
connection test failed: Response from Server: com.atlassian.crowd.exception.InvalidAuthenticationException: Application failed to authenticate
The above error message means Confluence was able to access or ping JIRA server using the configured URL, however the application name and credential by the configured directory is not the same as the one configured on step 3 above.
Please ensure that the JIRA directory configured on Confluence side use the correct application name and credential to access JIRA user management framework.
Hope it helps.
2 years on, and it helped me! Thanks.
On a side note: I found an issue with the my servers hosts file resolving the FQDN to localhost/127.0.0.1 which created all sorts of app-linking problems for me (don't know where to put this for others). I was behind a reverse proxy, so needed the IP address of the proxy for the linking to work (host/nslookup tool worked to diagnose this for me).
I have a similar issue, now the only thing is, the documentation is no longer up-to-date for JIRA v 6.2 and Confluence 5.5. I cannot seem to find the "Add Application" link with the new User Management screen.
Can anyone from Atlassian answer this? Where can I add Confluence as an application in JIRA so that it can be used for user management? I have Application Links working and I am still getting the same error.
I posted a question here as well: https://confluence.atlassian.com/display/DOC/Connecting+to+Crowd+or+JIRA+for+User+Management#ConnectingtoCrowdorJIRAforUserManagement-ConnectingConfluencetoJIRAforUserManagement- and so far the documentation has not been updated.
Hi John, Thank you, this is really helpful info.
I have added the necessary group memberships in JIRA, but still no success.
Meanwhile I also figured out that the application name and password entry form may cause the issue as it can only be saved after a test cycle, however when the form reloads it changes the set password ...
I just looked up the entries in the DB (found it stored plain text ...), and updated manually here:
cwd_directory_attribute table, where attribute_name is application.password.
And finally it is working! Thanks again!
The version of Chrome I am using is doing the same thing - it switched the password field back to another value after every successful test, and it took me well over an _hour_ to figure this out. I had torn everything apart trying to figure out why it passed when I would click Test, but outside the settings box synchronizations would fail every time. Sigh. -Kelly G. Schoenhofen
My issue was my browser kept automatically putting wrong values in the Username & Password fields after every page refresh (such as after a successful test). Assuming that is your issue; set everything correctly, click Test, and if it worked, _set them again_ and click Save without testing, again. My browser kept screwing up the settings _after_ a successful test, and I wasn't noticing. (especially the password part - ****** looks the same as ******. Crazy, but true!)
I have a very similar issue with setting up both Stash and Confluence to use JIRA as the user database. I am running all services on different ports (under different Java VMs), and all are behind an apache reverse proxy forcing https with a valid certificate.
I have added the certificates to the JRE keystores.
I was able to set up the application links both in JIRA and in Stash and Confluence, tested the links from Stash and Confluence, both were working. So I changed the order of auth services in Confluence, logged out and tried log back in, but now I'm closed out.
With Stash I also cannot authenticate through the JIRA user base, I've got the following error: com.atlassian.crowd.exception.InvalidAuthenticationException: Application failed to authenticate
So now I'm stuck, and even cannot log in to Confluence.
Any help is really appreciated!
This community is celebrating its one-year anniversary and Atlassian co-founder Mike Cannon-Brookes has all the feels.Read more
Hi Community! Kesha (kay-sha) from the Confluence marketing team here! Can you share stories with us on how your non-technical (think Marketing, Sales, HR, legal, etc.) teams are using Confluen...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs