How to disable the SSO authentication in Bamboo from the backend database
プラットフォームについて: Server および Data Center のみ。この記事は、Server および Data Center プラットフォームのアトラシアン製品にのみ適用されます。
Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Fisheye および Crucible は除く
要約
If SSO is the primary authentication method and for some reason, it fails or want to bypass/disable it from backend, please follow the below instructions mentioned in the solution.
環境
Bamboo 8.1+ versions with SSO support and miniorange SAML SSO setup used for this case.
ソリューション
Solution 1:
SSO authentication can be bypassed by enabling the username/password authentication with a REST call. Please follow the steps mentioned in this document Lockout recovery process under section Fallback authentication in Bamboo for the same.
Solution 2:
データベースの変更を行う前に必ずデータをバックアップしてください。可能であれば、まずステージング サーバーで、すべての変更、挿入、更新、または削除の SQL コマンドをテストしてください。
If the above solution didn't work for your Bamboo instance and still authentication points to SSO, please follow the below steps:
Run the below SQL query on the Bamboo database:
SELECT * FROM BANDANA WHERE BANDANA_KEY like '%ENABLE_SAML_SSO%';If the above query provide you results like below for example, then continue to the next steps:
98926605 | 0 | miniorange.saml.ENABLE_SAML_SSO | <string>true</string>- Stop Bamboo
- Take a backup of the Bamboo database.
Run the below update SQL query:
UPDATE BANDANA set serialized_data='<string>false</string>' where BANDANA_ID=<id from the query in step 2>;Once the above update runs successfully, verify the same if updated correctly by running the below query, it should as '<string>false</string>' under the serialized_data column:
SELECT * from BANDANA where BANDANA_ID=<id from the query in step 2>;- Start Bamboo.