Blank login screen or HTTP redirection loop after upgrading Bamboo
プラットフォームについて: Server および Data Center のみ。この記事は、Server および Data Center プラットフォームのアトラシアン製品にのみ適用されます。
サーバー*製品のサポートは 2024 年 2 月 15 日に終了しました。サーバー製品を利用している場合は、アトラシアンのサーバー製品のサポート終了のお知らせページにて移行オプションをご確認ください。
*Fisheye および Crucible は除く
要約
After a successful Bamboo upgrade, users get a blank screen or an HTTP redirection loop when trying to log in.
問題
The following similar events appear in the atlassian-bamboo
.logfiles2016-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.
診断
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 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.
ソリューション
Cause 1: seraph-config.xml incompatibilities
<bamboo-install>/atlassian-bamboo/WEB-INF/classes/seraph-config.xmlを編集します。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 以降 <param-value>/userlogin.action?os_destination=${originalurl}</param-value>Restart Bamboo
On future upgrades, best practice is to re-apply any customizations of the seraph-config.xml to the version of the file that comes with the new Bamboo version rather than replacing the entire file with the previous version.
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:
| Bamboo version | URL |
|---|---|
| 9.6 and earlier | $BAMBOO_BASE_URL/userlogin!doDefault.action?auth_fallback |
| 10.0 以降 | $BAMBOO_BASE_URL/userlogin.action?auth_fallback |