Installation configuration and credentials
Step 4 of the installation sequence. Review the file after extracting the package and before full installation.
Find and protect the configuration
The file is in the extracted package root, beside install_dbaasnow. With this guide's staging directory:
/opt/software/dbaasnow_v3_0_2026/installation_config.yml
Sign in as Linux user dbaasnow:
cd /opt/software/dbaasnow_v3_0_2026
ls -l installation_config.yml
chmod 600 installation_config.yml
vi installation_config.yml
The installer reads this file by default. Preserve its YAML indentation and key names, and restrict access because configured passwords are stored in plain text.
Review the three Repository passwords
The current configuration exposes three Repository password settings. The supplied file contains editable presets; the example below clears them for interactive entry:
broker_installation:
repository_sys_password: ""
repository_pdb_admin_password: ""
repository_dbaasnow_password: ""
| Setting | Purpose |
|---|---|
repository_sys_password |
Repository system-administrator access used during installation |
repository_pdb_admin_password |
Administrator password for the Repository's database container during fresh creation |
repository_dbaasnow_password |
Repository application-account access used by Lifecycle Manager components |
These are Repository installation credentials. Target database credentials and Broker user accounts are configured separately.
The preset values are shared defaults. Replace all three with approved passwords before production use, or clear the values and enter your chosen passwords at the prompts. You can set each password independently; they do not need to match one another.
Choose configured values or interactive prompts
Configured values: replace each preset with the approved password. Keep the file protected with mode 600. The installer validates the values without asking you to enter them again.
Interactive entry: use empty strings ("") as shown in the example above.
For full installation, the installer requests each missing or blank Repository password twice and checks that the entries match. Passwords are not displayed as you type.
| Prompt | Confirmation |
|---|---|
| Repository SYS password | Confirm Repository SYS password |
| Repository DBAASNOW schema password | Confirm Repository DBAASNOW schema password |
| Repository PDB administrator password | Confirm Repository PDB administrator password |
These prompt labels refer to the three Repository roles above. The container-administrator password is requested when Repository installation is selected. A Broker-only installation does not request that password.
The installer also requests the Linux OS password for dbaasnow (sudo) separately. Use the Linux account's credential at that prompt.
Password requirements
All three Repository passwords must:
- Be 8–30 characters long.
- Start with a letter.
- Include uppercase and lowercase letters and at least one number.
- Use only letters, numbers,
_,#and$.
Spaces, @ and quotation marks are not accepted as password characters. The quotation marks around YAML values delimit the string; they are not part of the password.
If validation fails or confirmation entries differ, correct the value and repeat the installation step after reviewing its result. Keep passwords out of command arguments, screenshots and support reports.
If you have an older configuration
Use the current three-field layout above. The older database_admin_password and broker_database_password keys are compatibility aliases for repository_sys_password and repository_dbaasnow_password, respectively.
A current key takes precedence when present, including when its value is blank. A blank current value causes prompting rather than reuse of an older alias. The container-administrator password has its own setting and does not fall back to the system-administrator password.
Customer setup-administrator username, email and password fields are no longer required. Adding older administrator fields does not override the installer's product-managed settings.
Broker console access
The Repository passwords above do not set your Broker console password. Customer access and administration are through the Broker.
For a fresh installation, open the printed console URL and sign in with:
- Username:
admin - Password:
admin
Change this initial password immediately through Setup → User Management. Create named Broker accounts for ongoing operations.
Existing installations and retries
Changing this file and rerunning installation is not a password-rotation procedure for an existing Repository. In particular, completed-Repository reruns do not reset existing container-administrator passwords. Preserve the existing credentials and records, and agree any recovery or password change with DBaasNow.
Using a configuration stored elsewhere
For the standard process, keep the supplied default location. If the installation owner uses a different file, specify it explicitly for full installation:
./install_dbaasnow --config /approved/path/installation_config.yml --components all
Replace the example path with the real protected file. This is an alternative to the standard full-install command.
Completion gate
Confirm that the matching configuration is present and protected, the three password choices are reviewed, and the Linux sudo credential is available. Resolve missing files, invalid passwords, confirmation mismatches or sudo failures before continuing.
Next: Run the four installation commands.