JDBC Connector Test Connection Error

Identity Security Cloud (ISC) ISC Discussion and Questions
1

Hi All,

For one of our JDBC connector we are facing attached below while performing test connection. Can someone please help on how to troubleshoot this.

**Error message displayed on UI**
[ ConnectorException ] [ Error details ] The server encountered an unexpected error while contacting target system. Please check the logs. test configuration

**Error message gathered via ccg.logs**

Caused by: sailpoint.connector.ConnectorException: The password property exceeds the maximum number of 128 characters.
	at sailpoint.connector.JDBCConnector.getConnection(JDBCConnector.java:2473)
	at sailpoint.connector.JDBCConnector.testConfiguration(JDBCConnector.java:345)
	... 11 more
Caused by: sailpoint.tools.GeneralException: The password property exceeds the maximum number of 128 characters.
	at sailpoint.connector.util.JDBCUtil.getConnection(JDBCUtil.java:295)
	at sailpoint.connector.JDBCConnector.getConnection(JDBCConnector.java:2469)
	... 12 more
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: The password property exceeds the maximum number of 128 characters```
2

Hi @maheshtare

Based on the error message the issue here is that the password being provided for the database connection is too long, exceeding the allowed limit of 128 characters.

3

Hi @rajeshs,

But we are able to connect to the Database using SQL Server Management Studio using same password.

4

Hi @maheshtare are you still having an issue to date? thanks

5

Hi @princess,

Yes we are still struggling with the same issue.

6

Do other of your JDBC sources have similar settings, including the pw count?
Going to recommend comparing one jdbc source working successfully that shares the same setup as this one. What did our support team say too? Always great to get their thoughts and have them look at it.

7

Hey Mahesh, were you able to solve this issue? From what i checked online it seems that the password which is being taken during the connection is the encrypted one (hence its crossing the 128 character length) which is causing this exception. That’s super strange, if true.

Do let us know if you have resolved the issue and if you were able to find out the root cause.

Thanks
Aishwarya

8

Hi Folks,

We are able to resolve the issue and reason we could identify is the special character in the password. Our Password had “£” symbol in it, once we changed the password without “£” it worked perfectly fine.

Strange but this is what we observed.

1 Like
9

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.