ldap.conf

A list of properties that are passed on to LDAP.

The listed attributes for the  java.naming.ldap.attributes.binary  key are read as binary values.

If there is more than one attribute, they must be separated by spaces, e.g.:

<map>

  <entry key="java.naming.ldap.attributes.binary" value="objectGUID"/>

</map>

In the case of the environment variable, only a String must be assigned, e.g. 'objectGUID'

S 39.5.34

A hardcoded filter to narrow down the search area

These are the recommended PLANTA groups to assign users to roles from the DirectoryService. Each of these groups references a role in PLANTA project:
- PLANTAProject_Administrator
- PLANTAProject_Employee
- PLANTAProject_ProjectManager
- PLANTAProject_MultiProjectManager
- PLANTAProject_DepartmentManager
- PLANTAProject_PortfolioManager
- PLANTAProject_PMAdministrator

A list of all LDAP attributes that are written into the DB when a user logs in or by a query_user_data.

They are listed as key - value pairs.

The key that is flagged with login is used to authenticate the user.

The key that is flagged with uuid is converted into an UUID String and serves to log the user in.

At the moment, only text attributes are allowed, except for the objectGUID which is converted into a UUID String.

For example:

<map>

  <entry key="userPrincipalName" value="login"/>

  <entry key="mail" value=""/>

  <entry key="sAMAccountName" value=""/>

  <entry key="sn" value=""/>

  <entry key="objectGUID" value="uuid"/>

</map>

In the case of the environment variable a Array of Strings has to be assigned, e.g. {'userPrincipalName=login','mail=','sAMAccountName=','distinguishedName=','objectGUID=uuid'}

S 39.5.34

Attribute name that contains the distinguished name

Up to S 39.5.31

Attribute name to add to the ldapUserFilter to search the user

Up to S 39.5.31

Attribute name which contains the user name that is forwarded to the login method

Up to S 39.5.31

The search scope for searches

Up to S 39.5.31