You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Join now to unlock these features and more
We have set up JIRA(8.20.12) and BAMBOO ( 8.0 version) integrated and triggering Bamboo build absolutely fine. But intermittently JIRA not triggering BAMBOO build if "BAMBOO" not logged in in Browser.
I mean, we have successfully set up the integration between JIRA and BAMBOO, allowing us to trigger Bamboo builds from JIRA. However, we've noticed an intermittent issue where JIRA fails to trigger a BAMBOO build when the "BAMBOO" user is not logged in on the browser. This results in a user authentication 401 error, even though the user exists and has the necessary permissions.
Error message, we got is: aused by: java.io.IOException: Server returned HTTP response code: 401 for URL) error where user is already exists and has required permissions.
Please team, help on the issue to address more effectively and how to resolve this issue.
Note: We are using JIRA(8.20.12) and BAMBOO ( 8.0 version) of server type instances.
Well 401 error mostly means a problem with authentication/authorization... so I think we should focus on that a little bit.
How did you set up JIRA and Bamboo integration?
Thank you @Mirek for the quick reply.
We are you using Application links created and it is a two way Application link (from Jira to Bamboo and opposite).
This is happening for any job randomly.
Already, enabled "Allow basic authentication on API calls" on JIRA. And we don't use any proxy on the network.
Jira triggering Bamboo build expects "active Bamboo login session" , otherwise it gives above 401 error.
A user authentication 401 error, even though the user exists and has the necessary permissions.
If I login to BAMBOO and then try to trigger, it is working fine. Unable to find the route cause, please help us to fix this issue asap.
I have found that, changing this value in <session-timeout>30</session-timeout> (... atlassian-bamboo\WEB-INF\web.xml) can fix this issue?
and please let me know, how can we set this session timeout value to "never".
I am not completely sure if the problem is related to how long the session is configured...
I think would be good to check the logs (<bamboo-home>/logs/atlassian-bamboo.log and <bamboo-home>/logs/atlassian-bamboo-access.log) for specific clues, temporary switch the user that is triggering that or focus on Application Link configuration for a moment to make sure that everything is correctly set between Jira and Bamboo..
You might start by verifying the Troubleshooting guide https://confluence.atlassian.com/kb/application-links-troubleshooting-guide-718668765.html
Overall there might be many reasons why this is happening.. One of the things is to check HTTPS configuration or even server time on both instances..