How to bulk change the password of the Fisheye/Crucible repositories
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. 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.
*Except Fisheye and Crucible
Summary
This page covers the steps required to change a significant amount of repository passwords in your Fisheye/Crucible instance. In particular, it provides a faster alternative to performing the update without changing the passwords one by one through the user interface.
Solution
Stop Fisheye/Crucible.
Locate the
config.xml
file in theFISHEYE_INST
directory.Create a backup copy of the
config.xml
file.Edit
config.xml
and identify the password requiring an update.This file contains the list of the repositories currently configured in the application. The details of each one of them is described by a
repository
tag and its children nodes.The password is stored, in clear text, in the
password
attribute of thepassword-auth
tag. For example:Git repository in the config.xml file
1 2 3 4 5 6
<repository name="Rep1" description="Repository1" store-diff="true" enabled="true"> <git location="https://username@bitbucket.org/repository_path/repository_name.git" renames="none" path=""> <password-auth password="your_password_here"/> </git> ... </repository>
Find and replace the old password with the new password.
Restart Fisheye/Crucible.
Verify that the modified repository/repositories are still
Running
by checking theState
column in theAdministration > Repositories
page.
Was this helpful?