Contents Now Platform Administration Previous Topic Next Topic Create a data source for LDAP Subscribe Log in to subscribe to topics and get notified when content changes. ... SAVE AS PDF Selected Topic Topic & Subtopics All Topics in Contents Share Create a data source for LDAP Each LDAP organizational unit (OU) definition has its own related list of data sources. Before you beginRole required: admin About this task Note: Both the LDAP Server and LDAP OU Definition must be active for the test load action to function properly. When the test load is activated for the first time, the system samples up to 20 records to determine the length of the import set fields. If the sampled records do not contain values for the User ID field, the system sets the field length for all subsequent imports to the default length of 40. The import truncates any imported data that exceeds the import set table field length. Additionally, the User ID field is truncated to a maximum of 40 characters. Be aware that the 20 loaded records cannot be transformed and are for testing purposes only. If the test records contain values for the User ID field, the field length is set based on the field length of the longest user ID in the test records. To create a new data source: Procedure Navigate to System LDAP > LDAP Servers. Select the LDAP server to configure. In the LDAP OU Definitions related list, select an item, such as Groups or Users. In the Data Sources related list, click New. Complete the Data Source form (see table). Click Submit. Under Related Links, click Test Load 20 Records to test whether the data source can bring LDAP data into the import table. Table 1. Data Sources form Field Description Name Specify the name the integration uses when referencing this data source. Import set table name Enter the name of the staging table where the system temporarily places the imported LDAP records and attributes. Review this table to view imported LDAP records. You can use the same import set table name for all LDAP data sources. Type Select LDAP to indicate the imported data is LDAP data. After you select the type LDAP, the form displays the LDAP target field. LDAP target Select the LDAP OU definition associated with this data source. Related TasksUpload the LDAP X.509 SSL certificateDefine an LDAP serverProvide LDAP server login credentialsSet LDAP connection propertiesTest an LDAP connection manuallyDefine LDAP organizational unitsAuto provision LDAP usersConfigure an LDAP serverSet up communication between LDAP and MID serversImport binary data through a MID ServerRelated ConceptsLDAP connection timeoutAutomatic LDAP operational status updateLDAP transform mapsLDAP data transformationonStart and onAfter LDAP scriptsScheduled data imports for LDAPScheduled data imports for LDAPTroubleshooting LDAP integration via MID ServerRelated ReferenceLDAP communication channels On this page Send Feedback Previous Topic Next Topic
Create a data source for LDAP Each LDAP organizational unit (OU) definition has its own related list of data sources. Before you beginRole required: admin About this task Note: Both the LDAP Server and LDAP OU Definition must be active for the test load action to function properly. When the test load is activated for the first time, the system samples up to 20 records to determine the length of the import set fields. If the sampled records do not contain values for the User ID field, the system sets the field length for all subsequent imports to the default length of 40. The import truncates any imported data that exceeds the import set table field length. Additionally, the User ID field is truncated to a maximum of 40 characters. Be aware that the 20 loaded records cannot be transformed and are for testing purposes only. If the test records contain values for the User ID field, the field length is set based on the field length of the longest user ID in the test records. To create a new data source: Procedure Navigate to System LDAP > LDAP Servers. Select the LDAP server to configure. In the LDAP OU Definitions related list, select an item, such as Groups or Users. In the Data Sources related list, click New. Complete the Data Source form (see table). Click Submit. Under Related Links, click Test Load 20 Records to test whether the data source can bring LDAP data into the import table. Table 1. Data Sources form Field Description Name Specify the name the integration uses when referencing this data source. Import set table name Enter the name of the staging table where the system temporarily places the imported LDAP records and attributes. Review this table to view imported LDAP records. You can use the same import set table name for all LDAP data sources. Type Select LDAP to indicate the imported data is LDAP data. After you select the type LDAP, the form displays the LDAP target field. LDAP target Select the LDAP OU definition associated with this data source. Related TasksUpload the LDAP X.509 SSL certificateDefine an LDAP serverProvide LDAP server login credentialsSet LDAP connection propertiesTest an LDAP connection manuallyDefine LDAP organizational unitsAuto provision LDAP usersConfigure an LDAP serverSet up communication between LDAP and MID serversImport binary data through a MID ServerRelated ConceptsLDAP connection timeoutAutomatic LDAP operational status updateLDAP transform mapsLDAP data transformationonStart and onAfter LDAP scriptsScheduled data imports for LDAPScheduled data imports for LDAPTroubleshooting LDAP integration via MID ServerRelated ReferenceLDAP communication channels
Create a data source for LDAP Each LDAP organizational unit (OU) definition has its own related list of data sources. Before you beginRole required: admin About this task Note: Both the LDAP Server and LDAP OU Definition must be active for the test load action to function properly. When the test load is activated for the first time, the system samples up to 20 records to determine the length of the import set fields. If the sampled records do not contain values for the User ID field, the system sets the field length for all subsequent imports to the default length of 40. The import truncates any imported data that exceeds the import set table field length. Additionally, the User ID field is truncated to a maximum of 40 characters. Be aware that the 20 loaded records cannot be transformed and are for testing purposes only. If the test records contain values for the User ID field, the field length is set based on the field length of the longest user ID in the test records. To create a new data source: Procedure Navigate to System LDAP > LDAP Servers. Select the LDAP server to configure. In the LDAP OU Definitions related list, select an item, such as Groups or Users. In the Data Sources related list, click New. Complete the Data Source form (see table). Click Submit. Under Related Links, click Test Load 20 Records to test whether the data source can bring LDAP data into the import table. Table 1. Data Sources form Field Description Name Specify the name the integration uses when referencing this data source. Import set table name Enter the name of the staging table where the system temporarily places the imported LDAP records and attributes. Review this table to view imported LDAP records. You can use the same import set table name for all LDAP data sources. Type Select LDAP to indicate the imported data is LDAP data. After you select the type LDAP, the form displays the LDAP target field. LDAP target Select the LDAP OU definition associated with this data source. Related TasksUpload the LDAP X.509 SSL certificateDefine an LDAP serverProvide LDAP server login credentialsSet LDAP connection propertiesTest an LDAP connection manuallyDefine LDAP organizational unitsAuto provision LDAP usersConfigure an LDAP serverSet up communication between LDAP and MID serversImport binary data through a MID ServerRelated ConceptsLDAP connection timeoutAutomatic LDAP operational status updateLDAP transform mapsLDAP data transformationonStart and onAfter LDAP scriptsScheduled data imports for LDAPScheduled data imports for LDAPTroubleshooting LDAP integration via MID ServerRelated ReferenceLDAP communication channels