[Building Sakai] use preferred name in JLDAP if it exists

Steve Swinsburg steve.swinsburg at gmail.com
Sat Jan 9 04:20:40 PST 2010


Hello all,

I am looking to gauge interest in the following issue relating to the JLDAP provider being applied to trunk:
http://jira.sakaiproject.org/browse/SAK-17238

-----
The JLDAP Provider has a set of fields that you can override in jldap-beans.xml. If you don't specify them, their values come from the defaults. However if you do override them and a value does not exist, no value is given at all. 

For instance in our LDAP setup we have the fields for first names: 
* givenName - full set of first name parts, ie Jonathon Edward where Jonathon is this person's firstname and Edward is his middle name. Cannot be changed. 
* ANUPreferredName - user specified, Jon, as that's what he prefers to be called. 

However to complicate matters, givenName is always set, ANUPreferredName not always, for instance with John Smith, his preferred name is John so it's no change. So we cannot just set ANUPreferredName as the mapping for a user's first name, otherwise some people will get nothing as their first name. 

There should be a preferredName field we can map that will be used preferentially, but will fall back to the givenName field if not set.
-----

Would you find this useful? I have applied a patch to implement this behaviour and it is backwards compatible with current implementations. We are using this in production.

regards,
Steve
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20100109/185424f3/attachment.html 
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 3823 bytes
Desc: not available
Url : http://collab.sakaiproject.org/pipermail/sakai-dev/attachments/20100109/185424f3/attachment.bin 


More information about the sakai-dev mailing list