AgileApps default passwords through Software AG Installer
Overview
This feature has been introduced in AgileApps Version 10.15. This feature enables dynamic default password for the administrator users through Software AG installer on Linux or Windows platforms. During the installation you will be asked for the default password for the administrator users.
Impacted Users
Currently, AgileApps and LongJump have 2 users with default passwords:
- LongJump administrator user with the following username - admin@longjump.com.
- AgileApps default tenant administrator user with the username - Administrator.
How to handle default password with automated scripts
For any automated installations using the readScripts, you can make the default password related changes by following the below steps.
The following command line parameters are used to install AgileApps using automated scripts (~readScript).
Default administrator password
The default administrator password is supplied as command line argument while running the installer exe or installer sh.
- As command line argument:
-adminPassword={DEFAULT_PASSWORD}
Note: The argument is prefixed with a minus character for this as a command line argument.
- As parameter in readScript file:
adminPassword={DEFAULT_PASSWORD}
-
Note: Here the argument is not prefixed with the minus character.
Force password change on login flag
This flag can only be configured into the readScript file as parameter.
- As parameter in readScript file:
changeAdminPasswordAtFirstLogin={FLAG_BOOLEAN_VALUE}. - For example:
changeAdminPasswordAtFirstLogin=true
The value of this parameter is either true or false.
Installation and Upgrade
Installation
AgileApps is co-hosted with Integration Server. When AgileApps is selected from the product tree in Software AG installer, Integration Server gets picked-up implicitly. So the same password enforcement is applied for both Integration Server and AgileApps products, and consequently the same default password is applied to both the products.
Minor Upgrade
In a minor version upgrade, AgileApps is shipped with the server side artifacts, database changes as SQL patches, and modified configuration if any. The platform is not required to use the installer tool to install AgileApps. Hence, the default password is not enforced and the platform works with the existing default password for the administrator users.
Major Upgrade
AgileApps needs a parallel installation of the target version to upgrade it to a major version.
During a major upgrade, the AgileApps platform does not expect a default password as the environment already contains it. However, a fresh installation through Software AG installer triggers the default password panel and expects a default password. This default password will be ignored by the AgileApps platform and the already existing password will be used for the administrator users.
-
Note:
- Integration Server is auto selected in the Software AG Installer on selecting AgileApps. Integration Server enforces the default password irrespective of whether it is a fresh installation of AgileApps or an upgrade of the existing environment.
- As the default password is handled separately for Integration Server, the default password provided during the upgrade is applicable for Integration Server only. However, the AgileApps environment ignores this password and uses the existing administrator passwords.
Troubleshooting
Case 1
You get an error logging in to AgileApps with the password you used during installation.
- Check if you are using the same password configured during installation.
- Refer installation level logs
introspectLog.txtin{INSTALL_DIR}/install/logs. - Refer application level logs
relationals.login{INSTALL_DIR}/profiles/IS_default/logs.
Case 2
You have encountered invalid credentials error. For example, Invalid username, password or platform account.
- Check for AgileApps installed version in database in the below table:
Table Setting NETWORK_GLOBAL_PROPERTIES version
- The version ensures the database has been installed fresh as a part of AgileApps installation.
Case 3
There are multiple layers involved in AgileApps installation, and a fault could be triggered by system failures or connection issues. In such cases:
- Contact the AgileApps R&D team for a temporary password solution.
- A hashed temporary password is shared with you with a force-change-password-on-first-login flag enabled. You will need to apply this into your database server and restart the server.