Differences

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

Link to this comparison view

Last revisionBoth sides next revision
72:ldap_mapping [2018/07/16 14:05] – created bkkr72:ldap_mapping [2019/07/22 08:31] – [Mapping LDAP Attributes to Stages] eazn
Line 38: Line 38:
       * The user attribute “_KEY“ should contain a unique key for every user entry in Stages. If no mapping is specified for that user attribute then the user attribute “username“ is assumed to be unique for every user entry.       * The user attribute “_KEY“ should contain a unique key for every user entry in Stages. If no mapping is specified for that user attribute then the user attribute “username“ is assumed to be unique for every user entry.
   * authenticationUsername   * authenticationUsername
-      * ​​​​​​​The user attribute “authenticationUsername“ should contain the LDAP distinguished name of a user entry if a mapping is specified for it. The attribute can be used to authenticate a user against a LDAP server. To enable this, the key attribute of the <font inherit/Courier New,Courier,monospace;;inherit;;inherit>ldap-provider</font> tag has to be set to that value.+      * The user attribute “authenticationUsername“ should contain the LDAP distinguished name of a user entry if a mapping is specified for it. The attribute can be used to authenticate a user against a LDAP server. To enable this, the key attribute of the <font inherit/Courier New,Courier,monospace;;inherit;;inherit>ldap-provider</font> tag has to be set to that value.
  
 === The id Attribute === === The id Attribute ===