Configuring PostgreSQL with DevTest After Install
Article ID: 213609
Updated On:
Products
Issue/Introduction
Currently IAM, Enterprise Dashboard and Registry connect to Derby.
We would like to have assistance configuring all of these components to connect to PostgreSQL.
Environment
All supported DevTest releases.
Cause
N/A
Resolution
NOTE: It is assumed there is a familiarity with PostgreSQL or can confer with a DBA for guidance.
DevTest delivers a PostgreSQL JDBC driver with the product.
For the Enterprise Dashboard (EDB), the driver is delivered in DEVTEST_HOME/lib/dradis/postgresql-42.2.5.jar.
For the Registry, the driver is delivered in DEVTEST_HOME/lib/shared/postgresql-42.2.5.jar.
For Identity Access Manager, this driver is not delivered in any folder under ${IAM_HOME}, so it is suggested to create this folder, ${IAM_HOME}database/drivers, and copy the postgresql-42.2.5.jar file from the EDB to this new folder.
Where $(IAM_HOME) = DEVTEST_HOME/IdentityAccessManager
Bring down all DevTest services.
Configuring PostgreSQL for IdentIty Access Manager (IAM)
1. Edit file ${IAM_HOME}iam.properties.
2. Configure the file using this example (this is a current working example)
iam.db.vendor=postgres
iam.db.url=jdbc:postgresql://[server]:5432/IAM_DB
iam.db.user=postgres
iam.db.password=<password in plain text, once IAM started the password will be stored in VAULT>
iam.db.jdbc.driver.path=${IAM_HOME}/database/drivers/postgresql-driver.jar
where postgresql-driver.jar is the version of the Postgres Driver delivered with Devtest
3. Start the IAM Service.
Configuring PostgreSQL for the Enterprise Dashboard (EDB)
1. Edit file DEVTEST_HOME/dradis.properties.
2. Configure the file using this example (this is a current working example)
## Should we start the internal Derby DB instance in the Enterprise Dashboard?
dradis.db.internal.enabled=false
## ==================================================================================
## PostgreSQL
## ==================================================================================
dradis.db.driverClass=org.postgresql.Driver
dradis.db.url=jdbc:postgresql://[server]:5432/EDB_DB
dradis.db.user=postgres
dradis.db.password=<password in plain text, once the EDB is started the password will be encrypted>
3. Start the Enterprise Dashboard service.
Configuring PostgreSQL for the Registry
1. Edit file DEVTEST_HOME/site.properties.
2. Configure the file using this example (this is a current working example)
## ==================================================================================
## PostgreSQL
## ==================================================================================
lisadb.pool.common.driverClass=org.postgresql.Driver
lisadb.pool.common.url=jdbc:postgresql://[server]:5432/REG_DB
lisadb.pool.common.user=postgres
lisadb.pool.common.password=<password in plain text, once the Registry is started the password will be encrypted>
## ==================================================================================
## Should the internal Derby DB instance in the Registry be started?
## ==================================================================================
lisadb.internal.enabled=false
3. Start the Registry service.
Additional Information
NOTE: When starting IAM, Enterprise Dashboard or Registry, if you get an error similar to this:
"Caused by: org.postgresql.util.PSQLException: FATAL: no pg_hba.conf entry for host "[IP address]", user "postgres", database "REG_DB", SSL off" you are missing some configuration on the PostgreSQL database side.
Please refer to this Knowledge Document: Resolving error: Caused by: org.postgresql.util.PSQLException: FATAL: no pg_hba.conf entry for host "{{IP address}}", user "postgres", database "IAM_X_X_0", SSL off
Feedback
