DEV Community

Michael
Michael

Posted on • Originally published at gbase8.cn

How to Update GDOM Database Credentials: Changing Users, Passwords, and IPs

#gbase #database #数据库 #security

GDOM (GBase Database Operation Manager) connects to three databases: a resource database, an analysis database (gdom_real), and a history database (gdom_history). When the IP, user, or password of any of these databases changes, the GDOM configuration must be updated accordingly, or the system will fail to start or operate correctly. This guide covers the standard procedure: stopping GDOM, generating an encrypted password, modifying the configuration, and restarting.

Locating the Configuration File

All database connection settings are stored in the application.properties file under the GDOM installation directory:

<install_dir>/install/gdom-service/config/application.properties

The file contains three groups of connection parameters:

  • Resource database (gdom): prefixed with gdom.datasource.druid.master.*
  • Analysis database (gdom_real): prefixed with gdom.datasource.druid.analysis.*
  • History database (gdom_history): prefixed with gdom.datasource.druid.analysis-history.*

Relevant configuration snippet:

gdom.datasource.druid.master.url=jdbc:postgresql://10.0.2.151:5432/gdom?useUnicode=true&characterEncoding=utf8
gdom.datasource.druid.master.username=gdom
gdom.datasource.druid.master.password=dVFIIHIxM5KGmDHjW4VKgQ==
gdom.datasource.druid.analysis.url=jdbc:gbase://10.0.2.151:5268/gdom_real?...
gdom.datasource.druid.analysis.username=gbase
gdom.datasource.druid.analysis.password=CRMSD4emUVT5HCD5H8Eotg==
gdom.datasource.druid.analysis-history.url=jdbc:gbase://10.0.2.151:5268/gdom_history?...
gdom.datasource.druid.analysis-history.username=gbase
gdom.datasource.druid.analysis-history.password=CRMSD4emUVT5HCD5H8Eotg==
Enter fullscreen mode Exit fullscreen mode

Step‑by‑Step Procedure

1. Stop GDOM

From the GDOM extraction directory, run the stop script:

./gdomStop.sh -s
Enter fullscreen mode Exit fullscreen mode

2. Generate an Encrypted Password

Navigate to the GDOM installation directory and execute the gdom-encrypt.sh tool, passing the new password as an argument. The script outputs a Base64‑encoded ciphertext.

./install/gdom-service/bin/gdom-encrypt.sh NEWPASSWORD
Enter fullscreen mode Exit fullscreen mode

Example output:

BCzwBU0W10jD74i9IGH/qA==
Enter fullscreen mode Exit fullscreen mode

Security note: The output is a Base64 string that decodes to an unreadable binary blob; it does not reveal the original plaintext password.

3. Update the Configuration File

Edit application.properties and replace the username and password values for the affected database(s). For instance, changing the resource database password:

# Old value
gdom.datasource.druid.master.password=dVFIIHIxM5KGmDHjW4VKgQ==
# New ciphertext
gdom.datasource.druid.master.password=BCzwBU0W10jD74i9IGH/qA==
Enter fullscreen mode Exit fullscreen mode

If the IP or database name also changed, update the url property accordingly.

4. Start GDOM

Return to the GDOM extraction directory and run the start script:

./gdomStart.sh -s
Enter fullscreen mode Exit fullscreen mode

After the service starts, log in to the GDOM web console to verify that the database connections are working properly.

Summary

Always synchronize database password changes with GDOM configuration updates. Use the built‑in encryption tool to generate ciphertext, update the properties file, and restart the service. This keeps your gbase database management tool running without interruption, even when backend credentials change.

Top comments (0)