1. Atlassian Labs Avatar Atlassian Labs
  2. Atlassian Labs
  3. bamboo-continuous-plugin-deployment
  4. Issues

Deploy JIRA Plugin task fails when WebSudo is not activated

Issue #22 resolved
Michael Tokar created an issue

Output below:

simple  20-Nov-2013 22:20:11    Build Deployment of '6.3.5-rc2' on 'Staging JIRA Servers' started building on agent agent-04-04.buildeng.atlassian.com
simple  20-Nov-2013 22:20:11    Build working directory is /opt/bamboo-agent/xml-data/build-dir/365035521-397443073
simple  20-Nov-2013 22:20:11    Executing build Deployment of '6.3.5-rc2' on 'Staging JIRA Servers'
simple  20-Nov-2013 22:20:11    Starting task 'Make sure the deployment does not run on elastic agents' of type 'com.atlassian.bamboo.plugin.requirementtask:task.requirements'
simple  20-Nov-2013 22:20:11    Finished task 'Make sure the deployment does not run on elastic agents'
simple  20-Nov-2013 22:20:11    Starting task 'Clean working directory task' of type 'com.atlassian.bamboo.plugins.bamboo-artifact-downloader-plugin:cleanWorkingDirectoryTask'
simple  20-Nov-2013 22:20:11    Cleaning working directory '/opt/bamboo-agent/xml-data/build-dir/365035521-397443073'
simple  20-Nov-2013 22:20:11    Finished task 'Clean working directory task'
simple  20-Nov-2013 22:20:11    Starting task 'Download release contents' of type 'com.atlassian.bamboo.plugins.bamboo-artifact-downloader-plugin:artifactdownloadertask'
command 20-Nov-2013 22:20:11    Substituting variable: ${bamboo.gh.version} with 6.3.5-rc2
simple  20-Nov-2013 22:20:11    Preparing to download plan result GH-GHMVN-64 artifact: Shared artifact: [Plugin JAR], pattern: [jira-greenhopper-plugin-6.3.5-rc2.jar] anchored at: [greenhopper/target]
simple  20-Nov-2013 22:20:12    Artifact [Plugin JAR] downloaded successfully in 1s to working directory
simple  20-Nov-2013 22:20:12    Finished task 'Download release contents'
simple  20-Nov-2013 22:20:12    Starting task 'Deploy to QA-EACJ' of type 'com.atlassian.bamboo.plugins.deploy.continuous-plugin-deployment:jiradeploy'
simple  20-Nov-2013 22:20:12    Starting plugin deployment task (v. 2.0.9)
simple  20-Nov-2013 22:20:13    SSL Certificate check: enabled
simple  20-Nov-2013 22:20:15    Product login success!
simple  20-Nov-2013 22:20:15    WebSudo authentication successful!
simple  20-Nov-2013 22:20:16    
simple  20-Nov-2013 22:20:17    Plugin upload succeeded!
simple  20-Nov-2013 22:20:41    Plugin installed successfully
simple  20-Nov-2013 22:20:41    Plugin upload completed successfully. Nice going, mate!
simple  20-Nov-2013 22:20:41    Finished task 'Deploy to QA-EACJ'
simple  20-Nov-2013 22:20:41    Starting task 'Deploy to QA-JAC' of type 'com.atlassian.bamboo.plugins.deploy.continuous-plugin-deployment:jiradeploy'
simple  20-Nov-2013 22:20:41    Starting plugin deployment task (v. 2.0.9)
simple  20-Nov-2013 22:20:41    SSL Certificate check: enabled
simple  20-Nov-2013 22:20:41    **** Outgoing Request Debug Log ****
simple  20-Nov-2013 22:20:41    > POST https://id.stg.iam.atlassian.com/id/rest/login
simple  20-Nov-2013 22:20:41    > Accept: application/json
simple  20-Nov-2013 22:20:41    > 
simple  20-Nov-2013 22:20:41    > {"username":"UUUUU","password":"XXXXX"}
simple  20-Nov-2013 22:20:41    ************************************
simple  20-Nov-2013 22:20:42    **** Incoming Response Debug Log ****
simple  20-Nov-2013 22:20:42    < HTTP/1.1 200 OK
simple  20-Nov-2013 22:20:42    < Server: nginx/1.1.19
simple  20-Nov-2013 22:20:42    < Date: Wed, 20 Nov 2013 22:20:42 GMT
simple  20-Nov-2013 22:20:42    < Content-Type: application/json
simple  20-Nov-2013 22:20:42    < Transfer-Encoding: chunked
simple  20-Nov-2013 22:20:42    < Connection: keep-alive
simple  20-Nov-2013 22:20:42    < P3P: CP="This is not a P3P policy! See http://www.atlassian.com/company/privacy for more info."
simple  20-Nov-2013 22:20:42    < Set-Cookie: __ATL_TOKEN_STG=zW3I80wivcwRbxYm0zVQfQ00; Version=1; Domain=.atlassian.com; Path=/; HttpOnly
simple  20-Nov-2013 22:20:42    < 
simple  20-Nov-2013 22:20:42    < (Non-repeatable response entity cannot be shown.)
simple  20-Nov-2013 22:20:42    *************************************
simple  20-Nov-2013 22:20:42    Login to Atlassian ID was successful.
simple  20-Nov-2013 22:20:42    **** Outgoing Request Debug Log ****
simple  20-Nov-2013 22:20:42    > POST https://jira.stg.internal.atlassian.com/secure/admin/WebSudoAuthenticate.jspa
simple  20-Nov-2013 22:20:42    > Accept: *
simple  20-Nov-2013 22:20:42    > 
simple  20-Nov-2013 22:20:42    > webSudoPassword=XXXXX&authenticate=Confirm
simple  20-Nov-2013 22:20:42    ************************************
simple  20-Nov-2013 22:20:42    **** Incoming Response Debug Log ****
simple  20-Nov-2013 22:20:42    < HTTP/1.1 200 OK
simple  20-Nov-2013 22:20:42    < Server: nginx/1.1.19
simple  20-Nov-2013 22:20:42    < Date: Wed, 20 Nov 2013 22:20:42 GMT
simple  20-Nov-2013 22:20:42    < Content-Type: text/html;charset=UTF-8
simple  20-Nov-2013 22:20:42    < Transfer-Encoding: chunked
simple  20-Nov-2013 22:20:42    < Connection: keep-alive
simple  20-Nov-2013 22:20:42    < X-AREQUESTID: 560x973x1
simple  20-Nov-2013 22:20:42    < Cache-Control: no-cache, no-store, must-revalidate
simple  20-Nov-2013 22:20:42    < Pragma: no-cache
simple  20-Nov-2013 22:20:42    < Expires: Thu, 01 Jan 1970 00:00:00 GMT
simple  20-Nov-2013 22:20:42    < X-ASEN: TestSEN
simple  20-Nov-2013 22:20:42    < X-Seraph-LoginReason: OK
simple  20-Nov-2013 22:20:42    < X-ASESSIONID: h2f401
simple  20-Nov-2013 22:20:42    < X-AUSERNAME: UUUUUUU
simple  20-Nov-2013 22:20:42    < X-Content-Type-Options: nosniff
simple  20-Nov-2013 22:20:42    < X-Robots-Tag: noarchive
simple  20-Nov-2013 22:20:42    < Vary: Accept-Encoding
simple  20-Nov-2013 22:20:42    < Set-Cookie: __atl_path=172.24.36.201.1384986042367828; path=/; expires=Sat, 18-Nov-23 22:20:42 GMT; domain=.atlassian.com
simple  20-Nov-2013 22:20:42    < Set-Cookie: JSESSIONID=E1AB3AF8FE6BBBBC50F686345BD33B1D; Path=/
simple  20-Nov-2013 22:20:42    < Set-Cookie: atlassian.xsrf.token=AKVY-YUFR-9LM7-97AB|c6b8491af4902aaee372503f07e11e0fba34f1bf|lin; Path=/
simple  20-Nov-2013 22:20:42    < 
simple  20-Nov-2013 22:20:42    < (Non-repeatable response entity cannot be shown.)
simple  20-Nov-2013 22:20:42    *************************************
error   20-Nov-2013 22:20:42    WebSudo authentication failed. A required header ('X-Atlassian-WebSudo') was missing from the response.
simple  20-Nov-2013 22:20:42    WebSudo authentication failed. A required header ('X-Atlassian-WebSudo') was missing from the response.
simple  20-Nov-2013 22:20:42    Finished task 'Deploy to QA-JAC'
simple  20-Nov-2013 22:20:42    Finalising the build...
simple  20-Nov-2013 22:20:42    Stopping timer.
simple  20-Nov-2013 22:20:42    Build 365035521-397443073-479461378 completed.
simple  20-Nov-2013 22:20:42    Finished processing deployment result Deployment of '6.3.5-rc2' on 'Staging JIRA Servers'

Comments (3)

  1. Joe Clark

    OK, I finally figured this out. The "required header was missing from the response" error message actually indicates that the websudo authentication failed - the password is incorrect.

    This can happen if you are using Atlassian ID to login, but the system is not yet integrated with Atlassian ID Websudo (still using vanilla JIRA websudo). In this circumstance, the login password (to Atlassian ID) will be different to the websudo password (to JIRA).

    The way Atlassian ID login is implemented means that it intercepts the login request to JIRA, so in JIRA's internal user directory, the password associated with the particular will be probably be different to the password actually stored against that user in Atlassian ID's own data store.

    So when you configure this task, you'll probably need to specify 2 different passwords for the same user (and the configuration UI allows you to do this).

    The long term plan in IT is for all systems that use Atlassian ID to also use Atlassian ID's WebSudo support, and once that change is rolled out this special case will no longer apply.

    I've committed an improvement to the error message that makes it clear that this error means that the password is wrong.

  4. Log in to comment
Assignee
Type
bug
Priority
major
Status
resolved
Votes
0
Watchers
2