LDAP Server

The Lightweight Directory Access Protocol (LDAP) is an open industry standard that has evolved to meet these needs. LDAP defines a standard method for accessing and updating information in a directory.

A directory is a listing of information about objects arranged in some order that gives details about each object. Common examples are a city telephone directory and a library card catalog. For a telephone directory, the objects listed are people; the names are arranged alphabetically, and the details given about each person are address and telephone number. Books in a library card catalog are ordered by author or by title, and information such as the ISBN number of the book and other publication information are given. Directories allow users or applications to find resources that have the characteristics needed for a particular task. For example, a directory of users can be used to look up a person's e-mail address or fax number. A directory could be searched to find a nearby PostScript color printer. Or a directory of application servers could be searched to find a server that can access customer billing information.

The Ud interface is between the Front-Ends (FEs) and the User Data Repository (UDR) in the User Data Convergence (UDC architecture). The User Data Convergence Stage 2 description (architecture and information flows) is specified in 3GPP TS 23.335.

Parameters:

Authentication Simple Authentication Method Name Password	Database Max Entries Root Entry RDN Second Level Entry RDN Third Level Entries CSV Test Data File
Uniform Delayed Response Enable Delayed Search Response Delay Interval (Search Requests) Delay Time (s) Max Number of Delayed Responses

LDAP Parameter Reference:

LDAP Limitation NOTEs:

Since the LDAP server cannot support the items listed below, the LDAP client must follow these limitations to ensure the LDAP query will be successful.

Landslide LDAPV3 APP currently only supports filter choice Filter_equalityMatch(3), other filter choices (0~2, 4~9) are not supported (Filter_and(0), Filter_or(1), Filter_not(2), Filter_equalityMatch(3),
Filter_substrings(4), Filter_greaterOrEqual(5), Filter_lessOrEqual(6), Filter_present(7), Filter_approxMatch(8)
Filter_extensibleMatch(9)).
In Filter_equalityMatch, the filter attributeDesc must be the first column in DIT Database definition.
Other columns in DIT database definition as filter search attribute conditions are not supported.
The RDN levels are counted by comma’,’ numbers in LDAP search request baseObject.
For LDAP Filter_equalityMatch BaseObject search, the Search BaseObject can support at most 3 RDN levels (Root RDN, Second Root RDN, Third Level RDN).
For LDAP Filter_equalityMatch SingleLevel search, the Search BaseObject must greater than 1 RDN level, should be 2 Root RND levels.
For LDAP Filter_equalityMatch WholeSubtree search, the Search BaseObject can support 0 (empty), 1 or 2 levels Root Entry RDN.
All test cases require that the client be stopped first to ensure no traffic is sent to the server, then the server should be stopped. If this sequence is not followed, the Abort button can be used to stop the test case.

Simple Authentication Method

LDAP server uses the selected authentication to validate each LDAP session.

There are three choices - Anonymous, Unauthenticated, and Name + Password.

If Anonymous Authentication is selected - Name and Password are Disabled.

If Unauthenticated Authentication is selected - Name is enabled and Password are Disabled.

If Name/Password Authentication is selected - Name and Password are both enabled.

Default: Anonymous (Tcl value = 0)

Unauthenticated Authentication (Tcl value = 1)

Name/Password Authentication (Tcl value = 2)

LdapSrvUdAuthMethod

Name

Name - USER ID of the LDAP Manager that has administrative access rights to the LDAP Directory.

Range: Up to 128 Characters.

Default: NONE

LdapSrvMgrDn

Password

Password for USER ID of the LDAP Manager that has administrative access rights to the LDAP Directory.

Range: Up to 128 Characters.

Default: NONE

LdapSrvMgrPassword

Max Entries

The Max number of entries that the LDAP server database can store.

Range: 1 to 50,000,000 (The actual size depends on the memory size of the Landslide test module)

Default: 100

LdapSrvDbMaxEntries

Root Entry RDN

RDN of first level root entry in DIT database

Range: Up to 128 Characters

Default: None

LdapSrvDitRootRdn

Second Level Entry RDN

RDN of second level root entry in DIT database.

Range: Up to 128 Characters.

Default: NONE

LdapSrvDitSecondRdn

Third Level Entries CSV Test Data File

This Test Data File (TDF) should contain a list of LDAP Third-level entries, where the first column defines and contains the unique identifier keys for the entries.

The first column supports defining a range of keys using the – character, e.g. 123450000-123459999. When using the range, each row would then represent multiple entries based on the range. The TDF should contain as many entries as needed to match the Database Max Entries parameter value, and any extra entries will just be ignored. Up to 128 columns are supported to represent the LDAP Attributes. The column names must use standard ASCII characters.

This TDF does not support the Auto-Incremented Groups feature, the first column range format provides a similar function.

Example of LDAP Third Level Entry file.

Learn more about Test Data Files.

Select/Create a new TDF-CSV

Allows you to create a new TDF by entering a file name that doesn’t already exist or select an existing file by entering a file name that already exists.

Click to open the Select Existing or Create window.

Navigate to the relevant library/folder,
Enter the name of the file:
If the file name already exists, the file is selected and applied in the test case.
If the file name does not exist, a message displays that says you are creating a new TDF and the embedded TDF-CSV will be launched.
- Click Yes to launch the TDF-CSV Editor and create/save the new TDF-CSV.
- Click No to select a different file

NOTE: If you do not have permission to save in the selected library, an error displays when you try to create a new file.

TIP: You may also navigate to the relevant library/folder and select file, and click OK.

Upload a New TDF to TAS

Click to import a new TDF file from your local folder and select in the test Case (instead of having to go to TDF Admin).

Navigate to the file on your local folder and select.
Then navigate to the location (library) where you want to save it on the TAS. You may rename the file, if required.

View Edit Selected TDF in TDF-CSV Editor

Available only when you have selected a TDF on TAS. Click to open the selected file in TDF-CSV Editor (in place, that is, within the Test Case).

Edit the file and save. You may also click Save As to save the edited TDF-CSV to a different library and also rename the file, if required.

NOTE: You may also select a TDF from a library to which you do not have write permissions, edit the file as required, and save (Save As) only to a different library with the same file name or a different name.

The only options available are Save As and Cancel.

Open Selected TDF in Standalone TDF-CSV Editor

Available only when you have selected a TDF on TAS. Select to retrieve the CSV file and open it in the stand alone TDF-CSV Editor.

Generate Stub TDF-CSV

TIP: Available only when a CSV specification has been defined for in the Test Case for the TDF widget ( View TDF Actions/Options Menu)

Opens an example context specific test data parametersexample context specific test data parameters, which you may save as a .CSV file or open in the TDF-CSV Editor.

Launch Standalone TDF-CSV Editor

Click to open a blank TDF-CSV Editor.

The Launch Standalone TDF-CSV editor options handles very large TDFs that may use too much Client memory if opened within the Test Case/in the embedded editor. You may set the standalone TDF-CSV Editor memory high to edit large TDFs.

Enable Delayed Search Response

Select to Enable Delay Interval, Delay Time and Max Number of Delayed Responses.

True/False

Default: False

LdapSrvDelayedRespEn

Delay Interval (Search Requests)

1 out of every X (entered value) responses to the LDAP Server Node will be delayed.

Range: 1 to 100000

Default: 100

LdapSrvDelayedRespInterval

Delay Time (s)

Every Delayed Response will be delayed by this number of Seconds.

Range: 1 to 1000

Default: 10

LdapSrvDelayedRespTime

Max Number of Delayed Responses

Enter the Maximum total number of delayed responses.

Range: 1 to 100000

Default: 100000

LdapSrvMaxDelayedResp