directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stefan Seelmann (JIRA)" <>
Subject [jira] Commented: (DIRSTUDIO-528) Handle schema extension used for OpenLDAP attribute ordering
Date Mon, 12 Oct 2009 15:01:32 GMT


Stefan Seelmann commented on DIRSTUDIO-528:

Studio 1.5.0 will contain basic support for X-ORDERED 'VALUES':
Modifications are sent as replace operation (addition still using add operation, deletion
still using delete operation).
For reordering you have some options:
- You could toggle the the entry editor to save modifcations automatically or not, so you
could switch off 'save automatically', change the values and then save the editor which sends
all modifications using one changetype:modify.
- You could use the new 'LDIF Entry Editor' (right-click the entry and select Open With->LDIF
Entry Editor). There you could change the indices and safe the modifications.

A dedicated value editor with re-order support should be added in future.

> Handle schema extension used for OpenLDAP attribute ordering
> ------------------------------------------------------------
>                 Key: DIRSTUDIO-528
>                 URL:
>             Project: Directory Studio
>          Issue Type: Improvement
>          Components: studio-ldapbrowser
>    Affects Versions: 1.4.0
>            Reporter: Torsten Rehn
> From the OpenLDAP docs:
> "Since the ordering of olcAccess directives is essential to their proper evaluation,
but LDAP attributes normally do not preserve the ordering of their values, OpenLDAP uses a
custom schema extension to maintain a fixed ordering of these values. This ordering is maintained
by prepending a "{X}" numeric index to each value [...]"
> I don't know if ADStudio intends to support this, but if it does: it's a mess right now.
Editing and reordering those attributes is almost impossible. This is really needed when editing
access rules set via olcAccess in cn=config. Are there any plans for handling those attributes
better? The current situation makes me want to go back to slapd.conf.
> My guess is that this would require some special editor that reads all values of the
attribute being edited, strips the curly braced indexes and uses "changetype: replace" to
modify the entire attribute instead of a single value.
> I understand that OpenLDAP is probably not your main concern, but it would be nice.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message