LDAP Integration pointed to an Active Directory Global Catalog Server

book

Article ID: 37725

calendar_today

Updated On:

Products

SUPPORT AUTOMATION- SERVER CA Service Desk Manager - Unified Self Service KNOWLEDGE TOOLS CA Service Management - Asset Portfolio Management CA Service Management - Service Desk Manager

Issue/Introduction

Problem:

When integrating CA SDM with an Active Directory Global Catalog Server  (via port 3268), not all LDAP fields may be available for syncing contact data in Service Desk.  However, if using port 389, it works.

Resolution:

The port 3268 is used for queries intended for the Global Catalog.

LDAP requests sent to port 3268 will search entire forest.

Only the attributes "marked for replication" to the Global Catalog will be returned.

For example: an LDAP query sent to port 3268 may not return the "department" attribute as it is not replicated to the global catalog. 

The port 389 is used for querying ldap data from the local domain.

LDAP requests sent to port 389 are used to only search for objects in the Global Catalog's home domain.

An LDAP query sent to port 389 will return the contact's "department" attribute.

Environment

Release:
Component: USRD