Directory

• Code (field COD)

This code identifies the current record in a unique way.

• Description (field INTIT)

Enter the description of the relevant record.

This long description is used as a title in screens and reports.

• Active (field ENAFLG)

Select this check box to activate the current record.

Disabled records keep their content and setup but cannot be used by recalling their code:

• On other records such as documents and settings
• On mass processes

The authorizations for a given function can prohibit the creation of an active record. In this case, the check box is disabled by default. It can only be modified by an authorized user or through a signature workflow.

• Domain (field DOMAIN)

The domain name is used to find the directory code that will be used to log in the user connected.

If the domain name is empty, the active directory code with empty domain will be used.

If the domain name is not empty, the active directory code with domain -of the connected user- will be used.

In both cases, if an active record is not found, the connection will be denied.

• Main server (field SERV1)

Is used to define the server name on which the LDAP directory is to be opened.
The second server is used upon connection error on the first server.

• Secondary server (field SERV2)

Is used to define the second server name on which the LDAP directory is to be opened if the first one has errors.

• Port number (field PORT)

This is the directory query port. By default this number is set to 389.

• Search identifier (field CONNEC)

This identifier is used for the search in the LDAP.

• Password (field PASSE)

• field MODPAS

This is the password of the identifier used for the search in the LDAP.

• Parameter 1 (field PARAM1)

When searching a user in the LDAP directory, the properties associated with a node in a hierarchical tree. This setup is used to defined where the hierarchy must start the search when the user wants to find information linked to the user. Moreover, this search will be carried out by setting a condition based on the value of the field Identifier 1 or Identifier 2 given in the setup table.

• Parameter 2 (field PARAM2)

the execution engine of the SAFE X3 platform uses 3 search instructions in the directory. This setup is used to define the search instruction that will be launched by the engine when checking the existence of a user in the LDAP database. It can take the following values:

• LEVEL results in the use of the Srldaplv instruction, which causes a one level search (search under the level corresponding to the specified node).
• BASE corresponds to the Srldapbsinstruction, which causes a base search (direct search in the specified node).
• SUBTREE (or any other value) corresponds to the Srldaptrinstruction, which results in a sub-tree search (search in the whole sub-tree corresponding to the given root).

An example of menu is given in the introduction of the technical appendix of the LDAP setup; in this example, 3 frameworks define these 3 levels of search.

• Field type (field TYPFLD)

This type of setup is used to manage the fields of the LDAP directory.
- Identifier: this is the unique identifier which makes it possible to link to the X3 table key.
- Identifier2: this is the identifier used if the first one was not successful.
- Record: is used to enter the field of the X3 user table (AUTILIS table).
- Setup: is used to enter the values of the general setups (ADOVAL table).

• X3 field (field CODFLD)

Is used to enter a field in the AUTILIS table if the field type is "Identifier/Identifier2/Record" or a general setup code if the field type is "Setup"

• Description (field NAMFLD)

• Directory field (field ADDFLD)

Is used to enter the attribute name in the LDAP directory.

• Formula (field FORFOR)

This formula is used to enter the search criteria in the LDAP in order to update the users.
The %% is used to highlight a formula which is valuated generating the criterion.
The $$ is used to indicate the user field number which will be used as a value of this criteria.
If the user field is in alphanumerical mode and if it is used in a formula, remember to add inverted commas, if necessary.

For instance, let us consider the formula (&(objectclass=user)(sAMAccountName=%%toupper("$$4$$")%%))
The $$4$$ represents the field [F:AUS]LOGIN.
Upon login of a user, this field is replaced by the user login and then evaluated (uppercase) and the search criteria in the LDAP becomes for this user:
(&(objectclass=user)(sAMAccountName=LOGIN))

It is also possible to enter (&(objectclass=user)(sAMAccountName=$$4$$))

• Domain (field DOMAIN)

• Criteria (field FILTRE)

LDAP query complying with the standardized syntax of the directory.

• Directory field (field ADDFLD)

Field of the directory which has been set up.

• Order (field SELECT)