How to configure Access Governance Suite to connect to Microsoft SQL Server using Windows Authentication vs. SQL Auth

  • 7011113
  • 11-Mar-2011
  • 02-Nov-2012


NetIQ Access Governance Suite


How to configure Access Governance Suite to connect to Microsoft SQL Server using Windows Authentication vs. SQL Auth



JTDS Download Location:

JTDS FAQ (Instructions on configuring JTDS jdbc driver):

A. Configure 3rd party application to use JTDS driver with Windows auth.

1) Install 3rd party database browser, such as dbVisualizer.

2) Download latest JTDS driver.

3) Install driver and configure dbVisualizer to utilize said driver.

4) Setup a new connection to your SQL Server database using the JTDS driver. The "Database URL" should look similar to this for proper windows authentication. You may need to change host, port, database name, domain, user and password values per your database environment:


5) Click the "Connect" button. Connection should be successful, assuming proper configuration.

6) Proceed to configure JTDS to work with identityIQ below.

B. Configure identityIQ to use JTDS driver with Windows auth.

Access Governance Suite 5.1p6
SQL Server 2008
Windows 2008 R2 SP1
Tomcat 6.0

1) Shutdown application server.

2) Download latest JTDS driver.

3) Remove existing driver:

4) Attempt to run "iiq console". Should see error about missing driver.

5) Install downloaded JTDS driver into proper location:

6) Modify identityIQ/WEB-INF/classes/ per JTDS FAQ instructions. Here is my example:



7) Attempt to run "iiq console" Should see a similar error:

C:\Sailpoint\identityiq\WEB-INF\bin>iiq console
org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'versionChecker' defined in class path resource [configBeans.xml]: Initialization of bean failed; nested exception is java.lang.RuntimeException: Unable to check Access Governance Suite database version: Invalid object name 'spt_database_version'.

8) Previous error is due to the fact that my "jdoe" login does not own the database or the schema associated with the identityiq database tables. The database was originally created to be owned by a user named "identityiq" with a schema of "identityiq". Your database administrator will need to handle corrections here in the SQL Server database. Once that is done, you should be authenticating via Windows Authentication Mode.

9) After proper database configuration, "iiq console" makes proper connection.

10) Startup application server.

11) Login to identityiq.