LDAP value order

David Bantz dabantz at alaska.edu
Thu Nov 24 19:04:04 GMT 2011

FWIW, we build attribute values in our directory to represent hierarchy precisely because LDAP attribute values are explicitly 
an unordered set of values, e.g.,

Employee Affiliation: 	 	UAF Main|CLA Anthropology

(i.e., University of Alaska Fairbanks, main campus, College of Liberal Arts, Dept. of Anthropology)

David Bantz <db at alaska.edu>   iam.alaska.edu
Chief Information Architect; Manager, Identity & Access Management Services
University of Alaska Office of Information Technology
✉ 103 Butrovich, 910 Yukon Dr, Fairbanks, AK  99775-5320
✆ +1 907 450 8314 (o) +1 907 460 6321 (m)

On Thu, 24 Nov 2011, at 24:11 , Manuel Haim wrote:

> Am 23.11.2011 18:34, schrieb Daniel Fisher:
>> What use case do you have for attribute ordering?
> Well, it's more a cosmetic issue... we have a user's ou field populated
> with values in hierarchical order (so it's something like
> [University,Institute,Department,Group]), and the mail field values are
> in logical order (like [uid at domain,givenName.sn at domain]), and some other
> fields contain values ordered by last change (i.e. last inserted).
> Keeping the order from LDAP would result in a better understandable
> overview of attributes e.g. in uApprove or in any other page which
> displays attribute values.
> -Manuel
> --
> To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net

-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://shibboleth.net/pipermail/users/attachments/20111124/fc4b7c16/attachment.html 

More information about the users mailing list