Submit a ticketCall us

WebinarUpcoming Webinar: Know What’s Changed – with NEW Server Configuration Monitor

Change management in IT is critical. But, even with a good change management process, changes are too often not correctly tracked, if at all. The configuration of your servers and applications is a key factor in their performance, availability, and security. Many incidents can be tracked back to an authorized (and sometimes unauthorized) configuration change, whether to a system file, configuration file, or Windows® Registry entry. Join SolarWinds VP of product management Brandon Shopp to discover how the new SolarWinds® Server Configuration Monitor is designed to help you.

Register now.

Home > Success Center > Database Performance Analyzer (DPA) > DPA - Knowledgebase Articles > Cannot authenticate to remote DPA instances from a Central DPA using AD/LDAP

Cannot authenticate to remote DPA instances from a Central DPA using AD/LDAP

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

Views: 910 Votes: 0 Revisions: 11

Overview

You cannot authenticate to a remote DPA instance from the DPA Central Server. This can happen in the following cases:

  • The DPA Central Server cannot connect to your AD/LDAP domain server.
  • The credentials supplied are invalid.
 

This is a side effect of one of our anti-lockout features for AD/LDAP. Many AD/LDAP servers are configured to lock out user accounts for failed passwords. To avoid locking accounts, we don't try to log on to any remote instances using AD/LDAP if you don't log on to the Central DPA with a valid AD/LDAP credential first.

Resolution

  • Log on to the Central DPA using valid AD/LDAP credentials.
    -or- 
  • Log on to each remote DPA instance separately without using the Central DPA.
    -or- 
  • If your AD/LDAP server does not lock out user accounts for failed password failures, you can configure your Central DPA instance to always attempt authentication with remote DPA servers:
    1. Edit the file <dpa>\iwc\tomcat\ignite_config\idc\system.properties
    2. Add the following line:
      com.confio.iwc.client.factory.ldap.login.on.fail=true
    3. Save the file and then restart the Central DPA. 

 

Last modified

Tags

Classifications

Public