AE fails to connect to PostgreSQL DB.

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

When attempting to connect to a new database on postgres, the connection failed with the following error-

v12.3

20220420/104458.203 - U00003545 UCUDB: Opening database ...
20220420/104458.203 - U00029112 UCUDB - Length of the DB-History area: 100
20220420/104458.953 - U00003590 UCUDB - DB error: 'FATAL:  LDAP authentication failed for user "aeuser"
', '', '', ''
20220420/104458.953 - U00000001 NO DATA (end of file, invalid key, no message...)
20220420/104458.953 - U00000001 NO DATA (end of file, invalid key, no message...)
Application return code = 1

v24.x

20250626/202518.988 - U00003545 UCUDB: Opening database ...
20250626/202518.988 - U00029112 UCUDB - Length of the DB-History area: 100
20250626/202519.066 - U00003590 UCUDB - DB error: 'connection to server at "databaseserver", port 5432 failed: FATAL:  LDAP authentication failed for user "aeuser"
connection to server at "databaseserver", port 5432 failed: FATAL:  no pg_hba.conf entry for host "databaseserver", user "aeuser", database "db", no encryption
', '', '', ''

Environment

Automic Automation

Resolution

The password for the database user contained a special character that the driver drops when passing the password to PostgreSQL DB.

Please change the password and excluded some special characters such as | @ and /. You can always try to remove all special characters from your password to test it if you are unsure what special characters are not being translated by the postgres driver.

Additional Information

There are known issues about special characters.

https://www.postgresql.org/message-id/trinity-6901c03f-0697-4493-bd86-779816915279-1368712107174%403capp-gmx-bs58