search cancel

Incorrect password for MSSQL after PAM SC 14.1 installation

book

Article ID: 190025

calendar_today

Updated On:

Products

CA Privileged Access Manager - Server Control (PAMSC)

Issue/Introduction

CA PAM SC 14.1 has been installed in Windows. MSSQL 2012 has been configured as its Relational Database (RDBMS) with mixed authentication.
Installation has passed all the checks: the MSSQL user specified to connect can successfully log in into the database from outside PAM SC and it meets the necessary complexity requirements
However, when starting jboss, there are some errors in the logs...

2020-05-04 11:02:53,972 INFO  [org.hibernate.connection.DatasourceConnectionProvider] (default-threads - 5) Using datasource: java:/jdbc/reportsnapshot
2020-05-04 11:02:54,347 WARN  [org.jboss.jca.core.connectionmanager.pool.strategy.PoolBySubject] (default-threads - 5) IJ000604: Throwable while attempting to get a new connection: null: javax.resource.ResourceException: Could not create connection
 at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.createLocalManagedConnection(LocalManagedConnectionFactory.java:347)
 at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.getLocalManagedConnection(LocalManagedConnectionFactory.java:354)
 at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory.access$200(LocalManagedConnectionFactory.java:63)
 at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory$1.run(LocalManagedConnectionFactory.java:263)
 at org.jboss.jca.adapters.jdbc.local.LocalManagedConnectionFactory$1.run(LocalManagedConnectionFactory.java:254)
...

...so that wildfly is not able to connect to the database and therefore the initialization of the product fails

Environment

CA PAM SERVER CONTROL 14.X

Cause

This issue occurs because of the difference in length of the password accepted by MSSQL and the one accepted by jboss/PIM. MSSQL will allow a long password (e.g. 18 characters including special characters) whereas wildfly is expecting a password of at most 11 characters. Hence, authentication fails

Resolution

Make sure the password specified for the RDBMS user used to connect to MSSQL does not exceed 11 characters