The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
You can configure directory integration through service profiles using Cisco Unified Communications Manager release 9 or later or with the configuration file. Use this section to learn how to configure the client for directory integration.
When both a service profile and a configuration file are present, the following table describes which parameter value takes precedence.
Service Profile |
Configuration File |
Which Parameter Value Takes Precedence? |
---|---|---|
Parameter value is set |
Parameter value is set |
Service profile |
Parameter value is set |
Parameter value is blank |
Service profile |
Parameter value is blank |
Parameter value is set |
Configuration file |
Parameter value is blank |
Parameter value is blank |
Service profile blank (default) value |
Note | Cisco Unified Presence, Release 8.x profiles cannot be used for directory integration. |
Note | Install Cisco Jabber for Windows on a workstation that is registered to an Active Directory domain. In this environment, you do not need to configure Cisco Jabber for Windows to connect to the directory. The client automatically discovers the directory and connects to a Global Catalog server in that domain. |
With Cisco Unified Communications Manager version 9 and higher, you can provision users with service profiles and deploy the _cisco-uds SRV record on your internal domain name server.
The client can then automatically discover Cisco Unified Communications Manager and retrieve the service profile to get directory integration configuration.
Deploy the _cisco-uds SRV record on your internal domain name server.
Ensure that the client can resolve the domain name server address.
Ensure that the client can resolve the hostname of Cisco Unified Communications Manager.
Ensure that the client can resolve the fully qualified domain name (FQDN) for the Cisco Unified Communications Manager.
Cisco Jabber now supports Cisco Unified Communications Manager User Data Service (UDS). In addition to being able to deploy Cisco Jabber using LDAP to connect to Active Directory, Jabber can now alternatively be deployed with Cisco Unified Communications Manager User Data Services contact lookup service. Server scaling must be considered when using the UDS server. A Cisco Unified Communication node can support UDS contact service connections for 50% of the maximum device registrations supported by the server.
To configure directory integration in a service profile, do the following:
The following table lists the configuration parameters you need to set in the directory profile:
It is not possible to change the default attribute mappings in a service profile. If you plan to change any default attribute mappings, you must define the required mappings in a client configuration file.
The following tables are a summary of all directory integration parameters.
These parameters are used for attribute mapping with LDAP directory servers.
BDI Parameters |
EDI Parameters |
---|---|
|
These parameters are used for connecting to LDAP directory servers.
BDI Parameters |
EDI Parameters |
---|---|
These parameters are used for contact resolution and directory queries with LDAP directory servers.
BDI Parameters |
EDI Parameters |
---|---|
|
These parameters are used for interacting with UDS as a contact source.
Parameter |
Value |
Description |
---|---|---|
DirectoryServerType |
BDI EDI UDS |
|
The following sections lists details about the parameters you can configure for LDAP-based directory integration.
BDI Parameter |
EDI Parameter |
Directory Attribute |
Exists in Global Catalog by Default |
Is Indexed by Default |
Set for Ambiguous Name Resolution (ANR) by Default |
||||
---|---|---|---|---|---|---|---|---|---|
BDICommonName |
CommonName |
cn |
Yes |
Yes |
No |
||||
BDIDisplayName |
DisplayName |
displayName |
Yes |
Yes |
Yes |
||||
BDIFirstname |
Firstname |
givenName |
Yes |
Yes |
Yes |
||||
BDILastname |
Lastname |
sn |
Yes |
Yes |
Yes |
||||
BDIEmailAddress |
EmailAddress |
Yes |
Yes |
Yes |
|||||
|
|
msRTCSIP-PrimaryUserAddress |
Yes |
Yes |
Yes |
||||
BDIPhotoSource |
PhotoSource |
thumbnailPhoto |
No |
No |
No |
||||
BDIBusinessPhone |
BusinessPhone |
telephoneNumber |
Yes |
No |
No |
||||
BDIMobilePhone |
MobilePhone |
mobile |
Yes |
No |
No |
||||
BDIHomePhone |
HomePhone |
homePhone |
Yes |
No |
No |
||||
BDIOtherPhone |
OtherPhone |
otherTelephone |
Yes |
No |
No |
||||
|
|
Yes |
No |
No |
|||||
BDITitle |
Title |
title |
Yes |
No |
No |
||||
BDICompanyName |
CompanyName |
company |
Yes |
Yes |
No |
||||
BDIUserAccountName |
UserAccountName |
sAMAccountName |
Yes |
Yes |
Yes |
||||
BDIDomainName |
DomainName |
EDI - userPrincipalName BDI - dn |
Yes |
Yes |
No |
||||
BDICountry |
co |
Yes |
No |
No |
|||||
BDILocation |
Location |
EDI - co BDI - location |
Yes |
No |
No |
||||
BDINickname |
Nickname |
displayName |
Yes |
Yes |
Yes |
||||
BDIPostalCode |
PostalCode |
postalCode |
Yes |
No |
No |
||||
BDICity |
City |
l |
Yes |
Yes |
No |
||||
BDIState |
State |
st |
Yes |
Yes |
No |
||||
BDIStreetAddress |
StreetAddress |
streetAddress |
Yes |
No |
No |
You must index attributes on your LDAP directory server so that the client can resolve contacts.
sAMAccountName
displayName
sn
name
proxyAddresses
department
givenName
telephoneNumber
Note | By default secondary number queries are enabled in Cisco Jabber for Windows. You can disable secondary number queries with the DisableSecondaryNumberLookups parameter. |
msRTCSIP-PrimaryUserAddress
Index msRTCSIP-PrimaryUserAddress for intradomain federation only.
Replicating attributes to your Global Catalog server generates traffic between Active Directory servers in the domain. For this reason, replicate attributes to your Global Catalog server at a time when network traffic can handle extra load.
If you do not want to replicate attributes to a Global Catalog server, configure Cisco Jabber to connect to a Domain Controller. However, the client queries single domains only when it connects to a Domain Controller.
BDI Parameter |
EDI Parameter |
Value |
Description |
||
---|---|---|---|---|---|
ConnectionType |
|
||||
BDILDAPServerType |
AD OpenLDAP |
|
|||
BDIPresenceDomain |
Domain of the presence node. |
Required parameter. Specifies the domain of the presence node. The client appends this domain to the user ID to create an IM address. For example, a user named Adam McKenzie has the user ID amckenzie. You specify example.com as the presence node domain. When the user logs in, the client constructs the IM address amckenzie@example.com for Adam McKenzie. |
|||
BDIPrimaryServerName |
PrimaryServerName |
Required parameter. Specifies the address of the primary directory server. This parameter is required for manual connections where the client cannot automatically discover the directory server.
|
|||
SecondaryServerName |
IP address FQDN |
Specifies the address of the backup directory server. This parameter is required for manual connections where the client cannot automatically discover the directory server. |
|||
BDIServerPort1 |
ServerPort1 |
||||
ServerPort2 |
ServerPort2 |
Port number |
|||
UseWindowsCredentials |
0 1 |
|
|||
BDIUseJabberCredentials |
true false |
|
|||
BDIConnectionUsername |
ConnectionUsername |
Lets you manually specify a shared username that the client can use to authenticate with the directory server. The client transmits and stores this username as plain text. By default, Cisco Jabber for Windows uses Integrated Windows Authentication when connecting to the directory server. This parameter lets you manually specify a username in scenarios where it is not possible to authenticate with the directory server with the user's Microsoft Windows credentials. Use only a well-known or public set of credentials for an account with read-only permissions to the directory. |
|||
BDIConnectionPassword |
ConnectionPassword |
Lets you manually specify a shared password that the client can use to authenticate with the directory server. The client transmits and stores this password as plain text. By default, Cisco Jabber for Windows uses Integrated Windows Authentication when connecting to the directory server. This parameter lets you manually specify a password in scenarios where it is not possible to authenticate with the directory server with the user's Microsoft Windows credentials. Use a well-known or public set of credentials for an account with read-only permissions to the directory. |
|||
BDIEnableTLS |
true false |
|
|||
UseSSL |
0 1 |
|
|||
UseSecureConnection |
0 1 |
|
BDI Parameter |
EDI Parameter |
Value |
Description |
||
---|---|---|---|---|---|
BDIBaseFilter |
BaseFilter |
Specifies a base filter for Active Directory queries. Specify a directory subkey name only to retrieve objects other than user objects when you query the directory. The default value for all clients is (&(objectCategory=person)( objectClass=user). Configuration files can contain only valid XML character entity references. Use & instead of & if you specify a custom base filter. |
|||
BDIUseANR |
true false |
Configure your directory server to set attributes for ANR if you want the client to search for those attributes. |
|||
BDIPredictiveSearchFilter |
PredictiveSearchFilter |
Defines filters to apply to predictive search queries. You can define multiple, comma-separated values to filter search queries.
Configure your directory server to set attributes for ANR if you want the client to search for those attributes. |
|||
DisableSecondaryNumberLookups |
0 1 |
|
|||
SearchTimeout |
|||||
UseWildcards |
0 1 |
|
|||
MinimumCharacterQuery |
Sets the minimum number of characters in a contact name to query the directory. For example, if you set 2 as the value of this parameter, the client searches the directory when users enter at least two characters in the search field. |
||||
BDISearchBase1 |
SearchBase1 SearchBase2 SearchBase3 SearchBase4 SearchBase5 |
Specifies a location in the directory server from which searches begin. In other words, a search base is the root from which the client executes a search. By default, the client searches from the root of the directory tree. You can specify the value of up to five search bases in your OU to override the default behavior. Active Directory does not typically require a search base. Specify search bases for Active Directory only for specific performance requirements. Specify a search base for directory servers other than Active Directory to create bindings to specific locations in the directory.
|
The following are example base filters you can use to look up specific locations or objects.
Find only specific groups:
(&(objectClass=user)(memberOf=cn=group-name,ou=Groups,dc=example,dc=com))
Find a nested group within a group:
(&(objectClass=user)(memberOf:search-oid:=cn=group-name,ou=Groups,dc=example,dc=com))
Find only enabled accounts and non-administrator accounts:
(&(objectCategory=person)(objectClass=user)(!(userAccountControl:search-oid:=2)) (!(sAMAccountName=*_dbo))(!(sAMAccountName=*-admin)))
Parameter |
Value |
Description |
---|---|---|
PhoneNumberMasks |
Specifies masks to use when users search for phone numbers. For example, a user receives a call from +14085550100. In the directory, this number is +(1) 408 555 0100. The following mask resolves the number: +1408|+(#) ### ### #### The length of mask strings cannot exceed the size restriction for registry subkey names. |
Phone masks apply to phone numbers before the client searches your directory. If you configure phone masks correctly, directory searches succeed as exact query matches and prevent any impact to performance of your directory server.
Element |
Description |
---|---|
Phone number pattern |
Provides a number pattern to retrieve phone numbers from your directory. To add a phone mask, you specify a number pattern that applies to the mask. For example, to specify a mask for searches that begin with +1408, you can use the following mask: +1408|+(#) ### ### #### To enable a mask to process phone numbers that have the same number of digits, but different patterns, use multiple masks with the same number of digits.
|
Pipe symbol (|) |
Separates number patterns and masks. For example, +1408|+(#) ### ### ####|+34|+(##) ### ####. |
Wildcard character |
Substitutes one or more characters for a subset of possible matching characters. Any wildcard character can exist in a phone mask.
|
Reverse mask |
Applies a number pattern from right to left. For example, a mask of +3498|R+34 (98) 559 #### applied to +34985590199 results in +34 (98) 559 0199. You can use both forward and reverse masks. |
BDI Parameter |
EDI Parameter |
Value |
Description |
---|---|---|---|
BDIPhotoUriSubstitutionEnabled |
PhotoUriSubstitutionEnabled |
|
|
BDIPhotoUriSubstitutionToken |
PhotoUriSubstitutionToken |
Specifies a directory attribute to insert in the photo URI; for example, sAMAccountName. |
|
BDIPhotoUriWithToken |
PhotoUriWithToken |
Specifies a photo URI with a directory attribute as a variable value. For example: http://staffphoto.example.com/sAMAccountName.jpg The parameter applies to LDAP directory integrations. To configure photo URI substitution, you set the directory attribute as the value of BDIPhotoUriSubstitutionToken. The client must be able to retrieve the photos from the web server without credentials. |
|
BDIPhotoSource |
PhotoSource |
Directory attribute |
The name of a directory attribute that stores a contact photo as a binary object or a URI to a contact photo. |
Cisco Jabber retrieves and displays contact photos with the following methods.
Note | When you change a photo in the Active Directory, the photo can take up to 24 hours to refresh in Cisco Jabber. |
Cisco Jabber dynamically builds a URL to contact photos with a directory attribute and a URL template.
<BDIPhotoUriSubstitutionToken>sAMAccountName</BDIPhotoUriSubstitutionToken>
<PhotoUriSubstitutionToken>sAMAccountName</PhotoUriSubstitutionToken>
<BDIPhotoUriWithToken>http://staffphoto.example.com/sAMAccountName.jpg</BDIPhotoUriWithToken>
<PhotoUriWithToken>http://staffphoto.example.com/sAMAccountName.jpg</PhotoUriWithToken>
With the example values in the preceding steps, the sAMAccountName attribute might resolve to msmith in your directory. Cisco Jabber then takes this value and replaces the token to build the following URL: http://staffphoto.example.com/msmith.jpg.
Cisco Jabber retrieves the binary data for the photo from your database.
If you are using binary objects from Active Directory do not set BDIPhotoUriWithToken or PhotoUriWithToken.
<BDIPhotoSource>jpegPhoto</BDIPhotoSource>
<PhotoSource>thumbnailPhoto</PhotoSource>
Cisco Jabber retrieves a URL from a directory attribute.
<BDIPhotoSource>photoUri</BDIPhotoSource>
<PhotoSource>photoUri</PhotoSource>
Parameter | Value | Description |
---|---|---|
PresenceDomain |
Domain of the presence node. |
Required parameter. Specifies the domain of the presence server. The client appends this domain to the user ID to create an IM address. For example, a user named Adam McKenzie has the following user ID: amckenzie. You specify example.com as the presence server domain. When the user logs in, the client constructs the following IM address for Adam McKenzie: amckenzie@example.com. |
UdsServer |
IP address FQDN |
Specifies the address of the Cisco Unified Communications Manager User Data Service (UDS) server. This parameter is required for manual connections where the client cannot automatically discover the UDS server. |
UdsPhotoUriWithToken |
URI |
Specifies a photo URI with a directory attribute as a variable value; for example, http://www.photo/url/path/%%uid%%.jpg.
The client must be able to retrieve the photos from the web server without credentials. |
Cisco Unified Communications Manager User Data Service (UDS) dynamically builds a URL for contact photos with a directory attribute and a URL template.
<UdsPhotoUriWithToken>http://server_name/%%uid%%.jpg</UdsPhotoUriWithToken>
UDS substitutes the %%uid%% token with the value of the userName attribute in UDS. For example, a user named Mary Smith exists in your directory. The value of the userName attribute for Mary Smith is msmith. To resolve the contact photo for Mary Smith, Cisco Jabber takes the value of the userName attribute and replaces the %%uid%% token to build the following URL: http://staffphoto.example.com/msmith.jpg
Note | When you change a photo in the Active Directory, the photo can take up to 24 hours to refresh in Cisco Jabber. |
If you deploy Expressway for Mobile and Remote Access, the client automatically uses UDS for contact resolution when users connect to services from outside the corporate network. When you set up UDS contact resolution for Expressway for Mobile and Remote Access, you must add the web server on which you host the contact photos to the HTTP server allow list in your Cisco Expressway-C server configuration. The HTTP server allow list enables the client to access web services inside the corporate network.
All contact photos must follow the format of the URL you specify as the value of UdsPhotoUriWithToken.
To achieve the best result with Cisco Jabber, your contact photos should have specific formats and dimensions. Review supported formats and optimal dimensions. Learn about adjustments the client makes to contact photos.
Cisco Jabber does not apply any modifications to enhance rendering for contact photos in GIF format. As a result, contact photos in GIF format might render incorrectly or with less than optimal quality. To obtain the best quality, use PNG format for your contact photos.
Tip | The optimum dimensions for contact photos are 128 pixels by 128 pixels with an aspect ratio of 1:1. 128 pixels by 128 pixels are the maximum dimensions for local contact photos in Microsoft Outlook. |
Location |
Dimensions |
---|---|
Audio call window |
128 pixels by 128 pixels |
|
64 pixels by 64 pixels |
|
32 pixels by 32 pixels |
Tip | Resizing contact photos can result in less than optimal resolution. For this reason, use contact photos that are 128 pixels by 128 pixels so that the client does not automatically resize them. |
Cropping—Cisco Jabber automatically crops nonsquare contact photos to a square aspect ratio, or an aspect ratio of 1:1 where the width is the same as the height.
Portrait orientation—If contact photos in your directory have portrait orientation, the client crops 30 percent from the top and 70 percent from the bottom.
For example, if contact photos in your directory have a width of 100 pixels and a height of 200 pixels, Cisco Jabber needs to crop 100 pixels from the height to achieve an aspect ratio of 1:1. In this case, the client crops 30 pixels from the top of the photos and 70 pixels from the bottom of the photos.
Landscape orientation—If contact photos in your directory have landscape orientation, the client crops 50 percent from each side.
For example, if contact photos in your directory have a width of 200 pixels and a height of 100 pixels, Cisco Jabber needs to crop 100 pixels from the width to achieve an aspect ratio of 1:1. In this case, the client crops 50 pixels from the right side of the photos and 50 pixels from the left side of the photos.
This section describes supported integration scenarios and provides example configurations.
Parameter |
Value |
---|---|
DirectoryServerType |
EDI |
ConnectionType |
1 |
<Directory><DirectoryServerType>EDI</DirectoryServerType> <ConnectionType>1</ConnectionType></Directory>
Parameter |
Value |
---|---|
DirectoryServerType |
EDI |
PrimaryServerName |
FQDN IP address |
ServerPort1 |
Port number |
SecondaryServerName |
FQDN IP address |
ServerPort2 |
Port number |
<Directory>
<DirectoryServerType>EDI</DirectoryServerType>
<PrimaryServerName>primary-server-name.domain.com</PrimaryServerName> <ServerPort1>1234</ServerPort1> <SecondaryServerName>secondary-server-name.domain.com</SecondaryServerName> <ServerPort2>5678</ServerPort2> </Directory>
Parameter |
Value |
||
---|---|---|---|
DirectoryServerType |
UDS |
||
UdsServer |
IP address of the UDS server |
||
UdsPhotoUriWithToken |
Contact photo URL |
||
PresenceDomain
|
Server address of your presence domain |
Note | Configure the DirectoryServerType parameter to UDS only if you want to use UDS for all contact resolution (that is, from inside and outside the corporate firewall). |
<Directory> <DirectoryServerType>UDS</DirectoryServerType> <UdsServer>11.22.33.444</UdsServer> <UdsPhotoUriWithToken>http://server-name/%%uid%%.jpg</UdsPhotoUriWithToken> </Directory>
Note | LDAP is the default configuration, so it is not necessary to include the DirectoryServerType parameter in your client configuration file. |
Parameter |
Value |
---|---|
BDIPhotoUriWithToken | Contact photo URL when inside the corporate firewall |
UdsPhotoUriWithToken | Contact photo URL when outside the corporate firewall |
<Directory> <BDIPhotoUriWithToken>http://photo.example.com/sAMAccountName.jpg</BDIPhotoUriWithToken> <UdsPhotoUriWithToken>http://server-name/%%uid%%.jpg</UdsPhotoUriWithToken> </Directory>
<UseWindowsCredentials>0</UseWindowsCredentials> <UseSSL>0</UseSSL> <UseSecureConnection>0</UseSecureConnection> <ConnectionUsername>username</ConnectionUsername> <ConnectionPassword>password</ConnectionPassword>
Simple authentication lets you connect to a directory server using simple binds, as in the following example configuration:
<BDIEnableTLS>False</BDIEnableTLS> <BDIConnectionUsername>username</BDIConnectionUsername> <BDIConnectionPassword>password</BDIConnectionPassword> <BDIServerPort1>389/3268</BDIServerPort1>
<UseWindowsCredentials>0</UseWindowsCredentials> <UseSSL>1</UseSSL> <UseSecureConnection>0</UseSecureConnection> <ConnectionUsername>username</ConnectionUsername> <ConnectionPassword>password</ConnectionPassword>
<BDIEnableTLS>True</BDIEnableTLS> <BDIConnectionUsername>username</BDIConnectionUsername> <BDIConnectionPassword>password</BDIConnectionPassword> <BDIServerPort1>636/3269</BDIServerPort1>
You can integrate with OpenLDAP using anonymous binds or authenticated binds.
Parameter |
Value |
---|---|
DirectoryServerType |
EDI |
ConnectionType |
1 |
PrimaryServerName |
IP address Hostname |
UseWindowsCredentials |
0 |
UseSecureConnection |
1 |
SearchBase1 |
Root of the directory service or the organizational unit (OU) |
UserAccountName |
Unique identifier such as UID or CN |
BaseFilter |
Object class that your directory service uses; for example, inetOrgPerson. |
PredictiveSearchFilter |
UID or other search filter |
<Directory> <DirectoryServerType>EDI</DirectoryServerType> <ConnectionType>1</ConnectionType> <PrimaryServerName>11.22.33.456</PrimaryServerName> <UseWindowsCredentials>0</UseWindowsCredentials> <UseSecureConnection>1</UseSecureConnection> <SearchBase1>ou=people,dc=cisco,dc=com</SearchBase1> <UserAccountName>uid</UserAccountName> <BaseFilter>(&(objectClass=inetOrgPerson)</BaseFilter> <PredictiveSearchFilter>uid</PredictiveSearchFilter> </Directory>
Parameter |
Value |
---|---|
DirectoryServerType |
BDI |
BDILDAPServerType |
OpenLDAP |
BDIPrimaryServerName |
IP address Hostname |
BDIEnableTLS |
True |
BDISearchBase1 |
Root of the directory service or the organizational unit (OU) |
BDIServerPort1 |
The port for the primary directory server |
BDIUserAccountName |
Unique identifier such as uid or cn |
BDIBaseFilter |
Object class that your directory service uses; for example, inetOrgPerson. |
(Optional) BDIPredictiveSearchFilter |
uid or other search filter |
<Directory> <DirectoryServerType>BDI</DirectoryServerType> <BDILDAPServerType>OpenLDAP</BDILDAPServerType> <BDIPrimaryServerName>11.22.33.456</BDIPrimaryServerName> <BDIEnableTLS>True</BDIEnableTLS> <BDISearchBase1>ou=people,dc=cisco,dc=com</BDISearchBase1> <BDIServerPort1>636/3269</BDIServerPort1> <BDIUserAccountName>uid</BDIUserAccountName> <BDIBaseFilter>(&(objectClass=inetOrgPerson)</BDIBaseFilter> <BDIPredictiveSearchFilter>uid</BDIPredictiveSearchFilter> </Directory>
Parameter |
Value |
---|---|
DirectoryServerType |
EDI |
ConnectionType |
1 |
PrimaryServerName |
IP address Hostname |
UserWindowsCredentials |
0 |
UseSecureConnection |
0 |
SearchBase1 |
Root of the directory service or the organizational unit (OU) |
UserAccountName |
Unique identifier such as UID or CN |
BaseFilter |
Object class that your directory service uses; for example, inetOrgPerson. |
PredictiveSearchFilter |
UID or other search filter |
ConnectionUsername |
Username |
ConnectionPassword |
Password |
<Directory> <DirectoryServerType>EDI</DirectoryServerType> <ConnectionType>1</ConnectionType> <PrimaryServerName>11.22.33.456</PrimaryServerName> <UserWindowsCredentials>0</UserWindowsCredentials> <UseSecureConnection>0</UseSecureConnection> <SearchBase1>ou=people,dc=cisco,dc=com</SearchBase1> <UserAccountName>uid</UserAccountName> <BaseFilter>(&(objectClass=inetOrgPerson)</BaseFilter> <PredictiveSearchFilter>uid</PredictiveSearchFilter> <ConnectionUsername>cn=lds-read-only-user,dc=cisco,dc=com</ConnectionUsername> <ConnectionPassword>password</ConnectionPassword> </Directory>
Parameter |
Value |
---|---|
DirectoryServerType | BDI |
BDILDAPServerType | OpenLDAP |
BDIPrimaryServerName |
IP address Hostname |
BDIEnableTLS | False |
BDISearchBase1 |
Root of the directory service or the organizational unit (OU) |
BDIServerPort1 |
The port for the primary directory server |
BDIUserAccountName | Unique identifier such as UID or CN |
BDIBaseFilter |
Object class that your directory service uses; for example, inetOrgPerson. |
BDIPredictiveSearchFilter | (Optional) UID or other search filter |
BDIConnectionUsername | Username |
BDIConnectionPassword | Password |
<Directory> <DirectoryServerType>BDI</DirectoryServerType> <BDILDAPServerType>OpenLDAP</BDILDAPServerType> <BDIPrimaryServerName>11.22.33.456</BDIPrimaryServerName> <BDIEnableTLS>False</BDIEnableTLS> <BDISearchBase1>ou=people,dc=cisco,dc=com</BDISearchBase1> <BDIServerPort1>389/3268</BDIServerPort1> <BDIUserAccountName>uid</BDIUserAccountName> <BDIBaseFilter>(&(objectClass=inetOrgPerson)</BDIBaseFilter> <BDIPredictiveSearchFilter>uid</BDIPredictiveSearchFilter> <BDIConnectionUsername>cn=administrator,dc=cisco,dc=com</BDIConnectionUsername> <BDIConnectionPassword>password</BDIConnectionPassword> </Directory>
You can integrate with AD LDS or ADAM using specific configurations.
Parameter |
Value |
---|---|
DirectoryServerType |
EDI |
PrimaryServerName |
IP address Hostname |
ServerPort1 |
Port number |
UseWindowsCredentials |
0 |
UseSecureConnection |
1 |
SearchBase1 |
Root of the directory service or the organizational unit (OU) |
<Directory>
<DirectoryServerType>EDI</DirectoryServerType>
<PrimaryServerName>11.22.33.456</PrimaryServerName> <ServerPort1>50000</ServerPort1>
<UseWindowsCredentials>0</UseWindowsCredentials> <UseSecureConnection>1</UseSecureConnection>
<SearchBase1>dc=adam,dc=test</SearchBase1> </Directory>
Parameter |
Value |
---|---|
BDIPrimaryServerName |
IP address Hostname |
BDIServerPort1 |
Port number |
BDISearchBase1 |
Root of the directory service or the organizational unit (OU) |
<Directory> <BDIPrimaryServerName>11.22.33.456</BDIPrimaryServerName> <BDIServerPort1>50000</BDIServerPort1> <BDISearchBase1>dc=adam,dc=test</BDISearchBase1> </Directory>
Parameter |
Value |
---|---|
DirectoryServerType |
EDI |
PrimaryServerName |
IP address Hostname |
ServerPort1 |
Port number |
UseWindowsCredentials |
0 |
UseSecureConnection |
1 |
ConnectionUsername |
Username |
ConnectionPassword |
Password |
UserAccountName |
Unique identifier such as UID or CN |
SearchBase1 |
Root of the directory service or the organizational unit (OU) |
<Directory> <DirectoryServerType>EDI</DirectoryServerType> <PrimaryServerName>11.22.33.456</PrimaryServerName> <ServerPort1>50000</ServerPort1> <UseWindowsCredentials>0</UseWindowsCredentials> <UseSecureConnection>1</UseSecureConnection> <ConnectionUsername>cn=administrator,dc=cisco,dc=com</ConnectionUsername> <ConnectionPassword>password</ConnectionPassword> <UserAccountName>cn</UserAccountName> <SearchBase1>ou=people,dc=cisco,dc=com</SearchBase1> </Directory>
Parameter |
Value |
---|---|
DirectoryServerType |
EDI |
PrimaryServer |
IP address Hostname |
ServerPort1 |
Port number |
UseWindowsCredentials |
0 |
UseSecureConnection |
0 |
ConnectionUsername |
Username |
ConnectionPassword |
Password |
UserAccountName |
Unique identifier such as UID or CN |
SearchBase1 |
Root of the directory service or the organizational unit (OU) |
<Directory>
<DirectoryServerType>EDI</DirectoryServerType>
<PrimaryServerName>11.22.33.456</PrimaryServerName> <ServerPort1>50000</ServerPort1> <UseWindowsCredentials>0</UseWindowsCredentials> <UseSecureConnection>0</UseSecureConnection> <ConnectionUsername>cn=administrator,dc=cisco,dc=com</ConnectionUsername> <ConnectionPassword>password</ConnectionPassword> <UserAccountName>cn</UserAccountName> <SearchBase1>ou=people,dc=cisco,dc=com</SearchBase1> </Directory>
Parameter |
Value |
---|---|
BDIPrimaryServerName |
IP address Hostname |
BDIServerPort1 |
Port number |
BDIConnectionUsername |
Username |
BDIConnectionPassword |
Password |
BDIUserAccountName |
Unique identifier such as uid or cn |
BDISearchBase1 |
Root of the directory service or the organizational unit (OU) |
<Directory>> <BDIPrimaryServerName>11.22.33.456</BDIPrimaryServerName> <BDIServerPort1>50000</BDIServerPort1> <BDIConnectionUsername>cn=administrator,dc=cisco,dc=com</BDIConnectionUsername> <BDIConnectionPassword>password</BDIConnectionPassword> <BDIUserAccountName>cn</BDIUserAccountName> <BDISearchBase1>ou=people,dc=cisco,dc=com</BDISearchBase1> </Directory>