Differences

This shows you the differences between two versions of the page.

--- 72:ldap_optional_attributes [2018/07/16 13:54] – [Optional Attributes] bkkr
+++ 72:ldap_optional_attributes [2020/01/17 10:34] – [Optional Attributes] evt
@@ Line 47: / Line 47: @@
 |(&(objectClass=user)(!age<18)<font inherit/Arial,Helvetica,sans-serif;;inherit;;inherit>(</font>|(sn=smith)(sn=wright)))|All entries that are users having surname set to "smith" or "wright" and are older than 18| |
-**NOTE**: In the <font inherit/Courier New,Courier,monospace;;inherit;;inherit>PKitConfig.xml</font> file the character “&“ has to be escaped via “&“. Otherwise errors parsing the configuration file could occur.
+**NOTE**: In the <font inherit/Courier New,Courier,monospace;;inherit;;inherit>Config.xml</font> file the character “&“ has to be escaped via “&“. Otherwise errors parsing the configuration file could occur.
 There is a special memberOf keyword available on many LDAP directory servers. In the case of Microsoft Active Directory, groups are represented via entries of object class “group“ by default. The distinguished names of the group members are set in the member attributes of the group entry. On the other hand, the distinguished name of every group a user is part of is automatically set in a <font inherit/Courier New,Courier,monospace;;inherit;;inherit>memberOf</font>attribute of the user entry.
@@ Line 68: / Line 68: @@
 groupMemberAttribute="member“</font>''
-===   ===
+=== The ondemandFilter Attribute ===
+This attribute is required for user auto-creation and/or on-demand synchronization mode. It allows the Stages system to query the LDAP server for specific users by their Stages login name. The attribute value a query filter like the searchFilter attribute, except that it is meant for unique queries.
+The ondemandFilter must contain the placeholder character “%” that will be replaced by the username when queries on the LDAP repository are made.
+Example: ''ondemandFilter=“(sAMAccountName=%,cn=Users,dc=methodpark,dc=com)”''
+=== The matchUsersMode Attribute ===
+The matchUserMode attribute specifies how LDAP user entries are matched to Stages users when no mapping can be performed using the special _KEY attribute.
+Possible values for the matchUserMode attribute are:
+  *
+username
+  *
+fullname
+  *
+email
+If no explicit value is set for that attribute then the username will be used for that purpose.
+=== The adoptUsers attribute ===
+Stages distinguishes between local user accounts and LDAP user accounts in its user database. The adoptUsers attribute can be used to convert a local user account to an LDAP account if the user can be identified via the matchUserMode attribute. To enable the user account conversion the adoptUser attribute has to be set to “true“. The conversion is disabled by default.
+=== The generateDN attribute ===
+If the directory server does not provide a distinguished name attribute for its entries, the generateDn attribute can be set to “true“ to calculate the distinguished name automatically.
+=== The defaultLicenseType attribute ===
+The defaultLicenseType attribute specifies which license type shall be granted to a newly created LDAP user. Possible values for that attribute are:
+  *
+QM
+  *
+PM
+  *
+Dev
+  *
+none
+The specified license type is only assigned if the corresponding license limit for that type is not reached. If the defaultLicenseType attribute is not specified then the value of the configuration property license.types.initialType is used for that purpose.
 \\