Submit a ticketCall us

Don’t fall victim to a ransomware attack
Backups are helpful, but sometimes that’s not enough to protect your business against ransomware. At our live webcast we will discuss how to protect against ransomware attacks with SolarWinds® Patch Manager and how to leverage log data to detect ransomware. Register now for our live webcast.

Home > Success Center > Database Performance Analyzer (DPA) > Enable Windows Authentication using NTLMv2 in Ignite PI

Enable Windows Authentication using NTLMv2 in Ignite PI

Table of contents
Created by Interspire Import, last modified by MindTouch on Jun 23, 2016

Views: 73 Votes: 0 Revisions: 14

Overview

Certain Microsoft domain configurations require authentication with the domain controller to use NTLMv2. By default, Ignite PI authenticates with the Domain Controller using NTLM when using Windows authentication.   

 

If your Domain Controller requires NTLMv2 you may receive the following error when attempting to connect to a SQL Server instance using Windows authentication:
Login failed for user ''.  The user is not associated with a trusted SQL Server connection.

 

You may also see this error if the user credentials are incorrect, so you should first verify if the user name and password are correct before attempting the following solution.

Environment

  • All DPA versions
  • Ignite 4.3 and later

Steps

  1. Add the following property to <ignite_install_directory>/iwc/tomcat/ignite_config/idc/system.properties
     

    com.confio.idc.wizard.showAdditionalConnectionProperties=true

     

  2. Enter useNTLMv2=true in the JDBC URL Properties field on the Repository Connection Information screen.

    enterrepositoryconnectioninfo.gif

Last modified
19:14, 22 Jun 2016

Tags

Classifications

Public