Disabling Integrated Windows Authentication

 

Overview

Predict! Risk Controller supports both Integrated Windows Authentication (IWA) and standard SQL Server authentication.

This article explains how to verify the current authentication method and, if IWA is active, how to disable it and revert to SQL Server credentials.

 

Before You Begin

1. Take a backup of the standalone.xml configuration file before making any edits. 
   • This allows the original configuration to be restored if needed.
2. Stop the Predict! Risk Controller service before making any configuration changes.

 

Check the Current Authentication Method

To confirm whether IWA is currently in use:

1. Locate the standalone.xml file:
   • C:\prc6\WF26\standalone\configuration\standalone.xml
2. Open the file.
3. Locate the <connection-url> element inside <datasources>
4. Check whether integrated Security=true is present.

If integratedSecurity=true is present and Predict! is running correctly, IWA is active. 

 

Disable IWA and Revert to SQL Server Authentication

Step 1 — Stop the Predict! Risk Controller service

1. 1. Open the Windows Services control panel (services.msc)
   2. Locate the Predict! Risk Controller service and stop it.

 

Step 2 — Edit the standalone.xml configuration file

1. 1. Open the following file in a text editor (run as Administrator):
      • C:\prc6\wf26\standalone\configuration\standalone.xml

 

Step 3 — Remove the integratedSecurity parameter from the connection URL

1. 1. Locate the connection-url element within the datasource node.
   2. Remove ;integratedSecurity=true

 

Parameter Details Before:

jdbc:sqlserver://[hostname];DatabaseName=[dbname];integratedSecurity=true

Parameter Details After:

jdbc:sqlserver://[hostname];DatabaseName=[dbname]

 

Step 4 — Add the SQL Server credentials security node

Inside the datasource node, add a <security> block containing the SQL Server username and password.

The datasource node should resemble the following:

<datasource jndi-name="java:/prc4DS" pool-name="prc4DS" enabled="true" use-java-context="true">

  <connection-url>

    jdbc:sqlserver://[hostname];DatabaseName=[dbname]

  </connection-url>

  <driver>MSSqlServer</driver>

  <security>

    <username>[your_sql_username]</username>

    <password>[your_sql_password]</password>

  </security>

</datasource>

 

Step 5 — Revert the service Log On account

1. 1. Open the Windows Services control panel
   2. Right-click the Predict! Risk Controller service and select Properties.
   3. Navigate to the Log On tab and change the Log on as option from This account back to Local System account.
   4. Click Apply.

 

Step 6 — Restart the Predict! Risk Controller service

1. 1. Start the service from the Services control panel.

Predict! will now connect to the database using the SQL Server credentials specified in standalone.xml.

 

Step 7 — Remove the Windows Authentication DLL (optional)

The mssql-jdbc_auth-11.2.1.x64.dll file in the Windows system32 folder is no longer required. Removing it is optional and will not affect application operation.

 

Troubleshooting

Problem	Suggested Resolution
Database connection fails after completing these steps	Verify that the SQL Server account credentials in standalone.xml are correct and that the account has the necessary permissions on the Predict! database. Contact support if the issue persists.
Predict! service fails to start after the change	Confirm the standalone.xml file is valid XML and has not been corrupted during editing. Restore from the backup taken before editing and repeat the steps.
Log On tab still shows a domain account after reverting	Ensure Apply was clicked after selecting Local System account on the Log On tab. Restart the service after applying the change.