Stages Documentation

Differences

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

Link to this comparison view

Next revision		Previous revision
72:ldap_key_attribute [2018/07/16 12:52] – created bkkr72:ldap_key_attribute [2024/02/15 00:00] (current) – external edit 127.0.0.1
Line 7: Line 7:
 Given the example above, the DN for a user entry could be: Given the example above, the DN for a user entry could be:
  
-''<font inherit/Courier New,Courier,monospace;;inherit;;inherit>CN=<userName>,OU=User,DC=pkit,DC=methodpark,DC=de</font>''+''CN=<userName>,OU=User,DC=pkit,DC=methodpark,DC=de''
  
 The value <username> is assumed to be unique in that case. As every user has its own <username> value, it is necessary to set that attribute value for each user respectively before the user can be authenticated. The value <username> is assumed to be unique in that case. As every user has its own <username> value, it is necessary to set that attribute value for each user respectively before the user can be authenticated.
Line 13: Line 13:
 The key attribute is therefore used to specify a Stages user attribute, whose value will be set in an authentication schema to build up the distinguished name of a LDAP user entry. The key attribute is therefore used to specify a Stages user attribute, whose value will be set in an authentication schema to build up the distinguished name of a LDAP user entry.
  
-Possible values for the key attribute are:+//Possible values for the key attribute are://
  
-  * username+   * username
   * fullname   * fullname
   * authenicationUsername   * authenicationUsername
 +
 +**NOTE: **If the key attribute is set to “authenticationUsername“, then the value is used directly to authenticate a user and it is not set in the authentication schema. The login name directly corresponds to the distinguished name of the LDAP entry. The values of these user attributes are stated when a new user gets created in Stages