Title: Feature request for differently structured LDAP server
Last modified: August 21, 2016

---

# Feature request for differently structured LDAP server

 *  [Daniel H](https://wordpress.org/support/users/daniel-h/)
 * (@daniel-h)
 * [12 years, 4 months ago](https://wordpress.org/support/topic/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.
 * [https://wordpress.org/plugins/cas-maestro/](https://wordpress.org/plugins/cas-maestro/)

Viewing 1 replies (of 1 total)

 *  Plugin Author [Henrique Mouta](https://wordpress.org/support/users/vaurdan/)
 * (@vaurdan)
 * [12 years, 4 months ago](https://wordpress.org/support/topic/feature-request-for-differently-structured-ldap-server/#post-5002589)
 * Hey there.
    Thanks for your suggestion! We’ve made the LDAP integration using
   our current implementation, what’s why is really limited right now. We will try
   to analyze this suggestion and try to make the LDAP settings page more robust
   and global.
 * Any help and/or suggestions are appreciated!
 * Thanks!
    Henrique

Viewing 1 replies (of 1 total)

 The topic ‘Feature request for differently structured LDAP server’ is closed to
new replies.

 * ![](https://s.w.org/plugins/geopattern-icon/cas-maestro_009fe3.svg)
 * [CAS Maestro](https://wordpress.org/plugins/cas-maestro/)
 * [Frequently Asked Questions](https://wordpress.org/plugins/cas-maestro/#faq)
 * [Support Threads](https://wordpress.org/support/plugin/cas-maestro/)
 * [Active Topics](https://wordpress.org/support/plugin/cas-maestro/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/cas-maestro/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/cas-maestro/reviews/)

 * 1 reply
 * 2 participants
 * Last reply from: [Henrique Mouta](https://wordpress.org/support/users/vaurdan/)
 * Last activity: [12 years, 4 months ago](https://wordpress.org/support/topic/feature-request-for-differently-structured-ldap-server/#post-5002589)
 * Status: not resolved