Communities
A collaborative platform to connect and grow with like-minded Informaticans across the globe
Product Communities
Connect and collaborate with Informatica experts and champions
Discussions
Have a question? Start a Discussion and get immediate answers you are looking for
User Groups
Customer-organized groups that meet online and in-person. Join today to network, share ideas, and get tips on how to get the most out of Informatica
Get Started
Community Guidelines
Knowledge Center
Troubleshooting documents, product guides, how to videos, best practices, and more
Knowledge Base
One-stop self-service portal for solutions, FAQs, Whitepapers, How Tos, Videos, and more
Support TV
Video channel for step-by-step instructions to use our products, best practices, troubleshooting tips, and much more
Documentation
Information library of the latest product documents
Velocity (Best Practices)
Best practices and use cases from the Implementation team
Learn
Rich resources to help you leverage full capabilities of our products
Trainings
Role-based training programs for the best ROI
Certifications
Get certified on Informatica products. Free, Foundation, or Professional
Product Learning Paths
Free and unlimited modules based on your expertise level and journey
Resources
Library of content to help you leverage the best of Informatica products
Tech Tuesdays Webinars
Most popular webinars on product architecture, best practices, and more
Product Availability Matrix
Product Availability Matrix statements of Informatica products
SupportFlash
Monthly support newsletter
Support Documents
Informatica Support Guide and Statements, Quick Start Guides, and Cloud Product Description Schedule
Product Lifecycle
End of Life statements of Informatica products
Ideas
Events
Change Request Tracking
Marketplace
English
  • INFACore
  • All Products

Table of Contents

Search

  1. Preface
  2. Connections to source and target endpoints

Connections for INFACore

Connections for INFACore

Back Next

LDAP

LDAP

Create an LDAP connection to read from or write to LDAP.

Feature snapshot

Operation
Support
Read
Yes
Write
Yes

Connection properties

The following table describes the LDAP connection properties:
Property
Description
Connection Name
Name of the connection.
Each connection name must be unique within the organization. Connection names can contain alphanumeric characters, spaces, and the following special characters: _ . + -,
Maximum length is 255 characters.
Host Name
Required. LDAP directory server host name.
You can use the LDAP or LDAPS protocol to connect to LDAP Server.
  • To use the LDAP protocol, use one of the following formats:
    • ldap://<hostname>
    • <hostname>
  • To use the LDAPS protocol, use the
    ldaps://<hostname>
     format.
If you use SSL, use the host name that you specify in the SSL certificate.
Port
Required. LDAP directory server port number. Default is 389.
Anonymous Connection
Establishes an anonymous connection with the LDAP directory server. Select anonymous connection to access a directory server as an anonymous user without authentication.
You cannot establish an anonymous connection with Active Directory.
User Name
The LDAP user name to connect to the LDAP directory server.
Required if you want to connect to Active Directory.
Password
The password to connect to the LDAP directory server. If you do not enter the password, the Client establishes an anonymous connection.
Required if you want to connect to Active Directory.
Secure Connection
Establishes a secure connection with the LDAP directory server through the TLS protocol.
TrustStore File Name
The file name of the truststore that contains the TLS certificate to establish a one-way secure connection with the LDAP directory server.
Contact the LDAP Administrator for the truststore file name and password.
TrustStore Password
The password for the truststore file that contains the SSL certificate.
KeyStore File Name
The file name of the keystore that contains the keys and certificates required to establish a two-way secure communication with the LDAP directory server.
Contact the LDAP Administrator for the keystore file name and password.
KeyStore Password
The password for the keystore file required for secure communication.
Base DN
Required. The distinguished name (DN) of the root directory in the LDAP directory server.
For example, use the following base DN to connect to the Informatica domain:
dc=informatica-connector,dc=com
If you do not specify the base DN, the Secure Agent fails to fetch the metadata.
0 COMMENTS
We’d like to hear from you!