Share all details about your problem, including any error messages you may have received.
Hi all!
Hope you’re having a good start of the year.
I’m facing an issue when trying to connect to an MS SQL data base from IdentityIQ using a Cloud Gateway.
I’m using a service account that was already tested and worked using the Microsoft SQL Server Management tool. I login using Windows Authentication as the authentication option, and I can see all the tables, schemas, etc.
The error happens when I test the connection in the MS SQL connector, giving me a message of wrong credentials or insufficient permissions.
I’m sure that I’m using the correct password (I’ve tried changing it 20 times), so my guess is that somewhere SailPoint is not sending correctly the credentials I’m specifying in the connector configuration.
I’ve already added the app to the Cloud Gateway sync task and run it. There are some JDBC connectors that use the same Cloud Gateway and work perfectly.
I’m adding ;trustServerCertificate=true; at the end of the URL, since this is an option I had to enable in the MSSQL Management tool.
Any idea what could be happening here?
Thanks in advance!
Hi Kumar, thanks for your quick response!
I tried that but got the following error:
[ ConnectionFailedException ] [ Possible suggestions ] Check the configuration details and if there is smooth connectivity with target system. [ Error details ] Error occurred before establishing the connection with Microsoft SQL Server. The TCP/IP connection to the host sqlurl.com, port 1433 has failed. Error: "Connect timed out. Verify the connection properties. Make sure that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port. Make sure that TCP connections to the port are not blocked by a firewall.".
I’ve met with the Database team and they provided these parameters, including the port 8025.
It’s like when SailPoint tries to communicate with the DB through the CG, it uses other credentials.
Hi all,
Worked with the DB team and after tracking the logs, SailPoint was trying to connect using SQL Authentication, and the DB was expecting Windows authentication.
DB team provided a new service account created in the DB that worked.
If someone is having this same issue, please verify what kind of authentication the DB is expecting. If it’s expecting Windows auth, you’d need to work with kerberos.
