Resetting Admin Password

If you forgot the password of your admin user and cannot log in to ADx or Conversion, follow the procedure below to reset the password. Note that you cannot simply edit the installation file and reinstall when the password is already persisted in the database.

Resetting from configuration.json (no reinstallation required)

If you don't want to reinstall ADx, follow the procedure below to reset admin password. You will need access to the installation directory.

Encrypt your new password. You can use the encrypt.sh script provided in your package for that purpose. Copy the encrypted password to clipboard.
Shut down the ADx or Conversion instance where you forgot the password.
Open your installation directory (folder where ADx/Conversion is installed).
Open the conf folder.
Open the configuration.json file in a text editor.

Set the new encrypted password in json code. You can identify the relevant part by bind-id set to tribefire-admin-user.

 {"_type": "com.braintribe.cartridge.common.processing.configuration.url.model.RegistryEntry", "_id": "0",
    "bindId": "tribefire-admin-user",
    "denotation": {"_type": "com.braintribe.model.user.User", "_id": "1",
        "name": "admin",
        "password": "${decrypt('FWnpV1EI0oMcpeMYCaHoFhBRUYBghnXSrw/hH43dkmSLSJI9qT2V/vXym1b/8zIYvalWVw==')}"
}

Change password value to your encrypted password. Save and close the file.
Open the tribefire.properties file.
Set TRIBEFIRE_AUTH_ADMIN_ENFORCEPASSWORD=true. This will enforce the newly set password to be used.
Start the node again. You should now be able to log in with the new password.

Note that you cannot use TRIBEFIRE_AUTH_ADMIN_USERNAME and TRIBEFIRE_AUTH_ADMIN_PASSWORD properties in this case, because they are overriden by settings in the configuration.json file.

Resetting from Installation File (reinstallation required)

You can edit admin user credentials inside the .yaml setting file used for installation, provided you add the TRIBEFIRE_AUTH_ADMIN_ENFORCEPASSWORD: "true" property to the file. You need to re-install ADx for your changes to take effect.

Encrypt your new password. You can use the encrypt.sh script provided in your package for that purpose. Copy the encrypted password to clipboard.
Shut down the ADx or Conversion instance where you forgot the password.
Open your deployment package directory.

Open the installation yaml file. Paste your encrypted password into the ADMIN_USER section:

# ** Admin User **
# Configures the credentials for the default admin user.
# If the user doesn't exist yet, it will be created and the password will be set as specified here.
# If the user already exists, nothing will be done, i.e. its password will NOT be changed!
predefinedComponents:
    ADMIN_USER: !com.braintribe.model.user.User
        # Admin user name
        name: "admin"
        # Admin user password. Replace "[ENCRYPTED_PASSWORD]" with the encrypted password, e.g. "${decrypt('HMuN/VXo5+L0vVQzuJe7bAOiBmeKzWluP+POb7zjkcLCnzgawUfWmZAIu9eIOfVAzEQn6Q==')}".
        password: "${decrypt('7tykS+5v1dHkYfW+tAZHSxr/8VZiAh21dJMGyC4LIbbU8Ru5mv/8ugDCwVOj4wyti0roYg==')}"

Add the TRIBEFIRE_AUTH_ADMIN_ENFORCEPASSWORD: "true" property to the file.

    # ** Runtime Properties **
    # Runtime properties are used to configure application specific settings. Which properties are available/required depends on the application.
    # For the complete list of supported runtime properties refer to the documentation. However, all important/mandatory properties are listed below.
    runtimeProperties:
        ##############################################################################
        # Platform settings
        ##############################################################################

        TRIBEFIRE_AUTH_ADMIN_ENFORCEPASSWORD: "true"


        # This enables support for encrypted passwords in this configuration file (don't change!)
        TRIBEFIRE_SECURED_ENVIRONMENT: "true"

Reinstall ADx. You should now be able to log in with the new password.