AdminUI won't bind to AD for Administrative Authentication.

book

Article ID: 211488

calendar_today

Updated On:

Products

SITEMINDER CA Single Sign On Agents (SiteMinder) CA Single Sign On Federation (SiteMinder)

Issue/Introduction

AdminUI won't bind to AD for Administrative Authentication. 

When going through external admin store configuration wizard, admin enters external user directory connection information, ends up getting an error in admin ui:

Error: A connection to the LDAP directory 'ad.demo.com:389' could not be established for user 'ad_service_account', please check the connection details and try again.

Cause

Customer has verified that the AD service account and password are correct.

Environment

Windows 2012

policy server: 12.8sp2

Resolution

If AD is listening on default port 389, you may remove the port number to move forward within wizard.

If AD is listening on non default port, then you must provide the specific port.

Attachments