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

Link to this comparison view

Both sides previous revision Previous revision
72:ldap_ondemand [2018/07/16 13:53]
bkkr [The ondemandFilter Attribute]
72:ldap_ondemand [2020/01/17 10:36] (current)
evt [The ondemandFilter Attribute]
Line 8: Line 8:
 Example: ''​ondemandFilter=“(sAMAccountName=%,​cn=Users,​dc=methodpark,​dc=com)”''​ 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.