Encrypt Bitbucket configuration properties
In Bitbucket 8.11, we've added a new property
encrypted-property.cipher.classname that replaces the existing
jdbc.password.decrypter.classname property. This new property allows you to encrypt all properties available in the
We will be removing the
jdbc.password.decrypter.classname property in Bitbucket 9.0 and recommend switching to the new property.
To add extra security to your Bitbucket Data Center and Server instance, you can encrypt the configuration properties that are stored in the
bitbucket.properties file. Different encryption methods are available for both basic and advanced users. Additionally, you can create your own encryption mechanism.
The solutions outlined below provide a level of obfuscation for encrypting property values but do not offer complete security. The configuration files will still contain the necessary data to decrypt the values, which means that an attacker with access to these files could potentially decrypt the property values.
These approaches are intended to provide an additional layer of protection against accidental exposure of sensitive data but should not be relied upon as a comprehensive security solution.
This method uses a Base64 cipher, which is simple obfuscation. It is a straightforward solution for users who don’t want to store sensitive passwords in plain-text (for example, database password).
This method allows you to choose an algorithm to encrypt sensitive information. It provides more security as you don't have to store encrypted information anywhere in the configuration file, which makes it difficult for unauthorized parties to find and decrypt it.
AWS Secrets Manager
AWS Secrets Manager は、データベースの認証情報を高レベルで安全に保管するオプションを提供します。このサービスは、ランタイム コールを通じて認証情報を取得し、キーやトークンなどのハードコードされた認証情報を完全に削除します。
If you have special requirements for encryption, you can create your own encryption mechanism based on our examples.