Feature request for differently structured LDAP server
-
I’m currently working on setting up a WP site for a new project. Login is through CAS, then fetching data from an OpenLDAP server. This LDAP server has slightly different attributes than what CAS Maestro expects. For example, it uses “cn” instead of “uid” and has name split into “givenName” and “sn” (first and last name) instead of “displayname”.
It is fairly easy for me as a developer to modify the code to work with the OpenLDAP server (and with those minor modifications it works great by the way). However; it would require me to make the same modifications after each upgrade, introducing the risk of it being forgotten (for example by a system administrator applying a security update).
I would therefore be grateful if the attribute names could be added as modifiable options in the configuration. At least for “uid”/”cn” and “mail” due to mail being a required field in WP, and uid/cn is required to find that value.
Having attributes for firstname/lastname as options is not that important to me, but I think that too would benefit from being easily modifiable. Especially since the current way of splitting “displayname” only works reliably when the name is in the form “Firstname Lastname”. Any name with more than one first or last name – or when firstname and lastname are reversed – will be mapped incomplete or wrong.
The topic ‘Feature request for differently structured LDAP server’ is closed to new replies.
