The login failure returned was OUT.
Hi, i want use this plugin to deploy an confluence plugin but i get the following error although bamboo can login in. 18-Sep-2014 12:27:48 Product login failed. The login failure returned was OUT. 18-Sep-2014 12:27:48 Product login failed. The login failure returned was OUT.
Before the login failure messages i get an html output which contains "You are currently logged in as ci.user." So what is wrong?
Any ideas?
Comments (8)
-
-
I'm getting the same error, but only when deploying to an older version of Confluence. So, deployment to Confluence 5.5.3 works. Deployment to Confluence 4.3.7 fails with: simple 06-Oct-2014 13:40:40 Product login failed. The login failure returned was OUT.
When I dump all HTTP traffic, the Incoming Response Debug Log appears to return the Confluence Login page as HTML. I double checked that it wasn't something like a CAPTCHA login issue by logging into (successfully) the Confluence with that account in a separate browser.
I recently updated the continuous deployment plugin to version 3.0.5, and this is the first time I've had an opportunity to use that version against our Confluence 4.3.7.
-
I get the same error, but my scenario i think is different.
My Bamboo Build server is 5.6.2, deploying to Bamboo 5.7 Test Server. The real difference that i think that broke me is that my Bamboo 5.7 Test Server was converted to use Crowd as its user directory, as well as SSO is enabled. I dumpted to HTTP Traffic and noticed the following
SSL Certificate check: enabled 12-Nov-2014 09:44:38 **** Outgoing Request Debug Log (https://build.test.mydomain.com) **** 12-Nov-2014 09:44:38 > POST /userlogin.action HTTP/1.1 12-Nov-2014 09:44:38 > X-Atlassian-Token: no-check 12-Nov-2014 09:44:38 > Content-Length: 42 12-Nov-2014 09:44:38 > Content-Type: application/x-www-form-urlencoded; charset=ISO-8859-1 12-Nov-2014 09:44:38 > Host: build.test.mydomain.com 12-Nov-2014 09:44:38 > Connection: Keep-Alive 12-Nov-2014 09:44:38 > User-Agent: Apache-HttpClient/4.1 (java 1.5) 12-Nov-2014 09:44:38 > 12-Nov-2014 09:44:38 > os_username=MYADMIN&os_password=MYPASS 12-Nov-2014 09:44:38 ************************************ 12-Nov-2014 09:44:39 **** Incoming Response Debug Log **** 12-Nov-2014 09:44:39 < HTTP/1.1 200 OK 12-Nov-2014 09:44:39 < Date: Wed, 12 Nov 2014 15:44:38 GMT 12-Nov-2014 09:44:39 < Set-Cookie: JSESSIONID=D68C271BD401C5BFD503020A18044CE7; Path=/; Secure; HttpOnly 12-Nov-2014 09:44:39 < Set-Cookie: crowd.token_key=""; Domain=.test.mydomain.com; Expires=Thu, 01-Jan-1970 00:00:10 GMT; Path=/; Secure; HttpOnly 12-Nov-2014 09:44:39 < X-Seraph-LoginReason: OUT 12-Nov-2014 09:44:39 < Set-Cookie: crowd.token_key=Sj26MW9iv07JuLrE86yoBA00; Domain=.test.mydomain.com; Path=/; Secure; HttpOnly 12-Nov-2014 09:44:39 < X-Seraph-LoginReason: OK 12-Nov-2014 09:44:39 < Content-Type: text/html;charset=UTF-8 12-Nov-2014 09:44:39 < Content-Language: en-US 12-Nov-2014 09:44:39 < Connection: close 12-Nov-2014 09:44:39 < Transfer-Encoding: chunked
I noticed 2 "X-Seraph-LoginReason" are returned, 1 OUT, 1 OK, as well as 2 crowd.token_key cookies, 1 empty, then 1 populated
I have verified that the credentials do work from a browser
-
-
assigned issue to
-
assigned issue to
-
- changed status to open
I've released a version of the plugin with a change that I think will fix this. I don't have access to a Crowd SSO environment, so I need someone else to test it.
Could someone try installing v3.0.5.1 of the plugin from https://maven.atlassian.com/public/com/atlassian/bamboo/plugins/deploy/continuous-plugin-deployment/3.0.5.1/continuous-plugin-deployment-3.0.5.1.jar and seeing if it resolves the issue? If not, please post any new output from the task with the "dump all traffic" option selected.
-
perfect! works like a charm again!
-
Awesome! I'll merge it in and do a proper release on the Marketplace. Thanks for helping out :)
-
- changed status to resolved
- Log in to comment
Can you reproduce the problem again, but this time select the "Dump all HTTP traffic to build log" option in the task configuration? This will give me more information about the login failure.