Summary

After a successful Bamboo upgrade, users get a blank screen or an HTTP redirection loop when trying to log in.

Problem

• The following similar events appear in the atlassian-bamboo.log files


  2016-09-20 08:22:32,990 INFO [http-apr-8085-exec-12] [AccessLogFilter] x.x.x.x GET http://<Bamboo_Server_URL>/userlogin!default.action?os_destination=/start.action 71654kb
  2016-09-20 08:22:42,100 WARN [http-apr-8085-exec-12] [Dispatcher] Could not find action or result: /userlogin!default.action?os_destination=/start.action
  Method default for action userlogin is not allowed! - [unknown location]
  	at com.opensymphony.xwork2.DefaultActionProxy.prepare(DefaultActionProxy.java:200)
  	at org.apache.struts2.factory.StrutsActionProxy.prepare(StrutsActionProxy.java:63)
  	at org.apache.struts2.factory.StrutsActionProxyFactory.createActionProxy(StrutsActionProxyFactory.java:37)
  	at com.opensymphony.xwork2.DefaultActionProxyFactory.createActionProxy(DefaultActionProxyFactory.java:58)

• 404 (Page not found) events may also get logged by Bamboo

  2017-06-13 10:28:03,973 WARN [http-apr-8085-exec-12] [Dispatcher] Could not find action or result: /404.action?os_destination=/start.action
  Method default for action userlogin is not allowed! - [unknown location]
  	at com.opensymphony.xwork2.DefaultActionProxy.prepare(DefaultActionProxy.java:200)
  	at org.apache.struts2.factory.StrutsActionProxy.prepare(StrutsActionProxy.java:63)
  	at org.apache.struts2.factory.StrutsActionProxyFactory.createActionProxy(StrutsActionProxyFactory.java:37)

• An HTTP redirection loop (too many redirections) error may be experienced, or the user may be presented with the same login page even after submitting the authentication form, endelessly.

Diagnosis

Cause 1: seraph-config.xml incompatibilities

• Login or Logout link from Bamboo shows a blank page or 404 is received
• Bamboo was recently upgraded from a version prior to 5.13.0.1
• The seraph-config.xml file was manually overwritten (or restored) with data from an old Bamboo installation, during the upgrade

Cause 2: Incorrect login URL

• seraph-config.xml looks correct
• Login and Logout links from Bamboo
• The logs still report the error

Cause

Cause 1: seraph-config.xml incompatibilities

If there is a change in <bamboo-install>/atlassian-bamboo/WEB-INF/classes/seraph-config.xml attributes, due to this change any customization in this file needs to be merged/migrated to the new file without overwriting the whole file. This problem happens when the seraph-config.xml is overwritten by an older version.

Cause 2: Incorrect login URL

The error occurs when manually visiting the Bamboo user login page. It's likely that a user, or an automated script/service, has a hardcoded link to the incorrect login URL.

Resolution

Cause 1: seraph-config.xml incompatibilities

1. Edit <bamboo-install>/atlassian-bamboo/WEB-INF/classes/seraph-config.xml


2. Modify the <login.url> parameter value based on the Bamboo version you are running:

   Bamboo version	New value
   9.6 and earlier	<param-value>/userlogin!doDefault.action?os_destination=${originalurl}</param-value>
   10.0 and later	<param-value>/userlogin.action?os_destination=${originalurl}</param-value>

3. Restart Bamboo

Cause 2: Incorrect login URL

Please ensure all browser bookmarks or automations are using the correct login action URL based on the Bamboo version you are running: