directory-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Martin Alderson (JIRA)" <>
Subject [jira] Commented: (DIRSTUDIO-115) Unable to edit operational attribute values
Date Fri, 01 Jun 2007 17:13:15 GMT


Martin Alderson commented on DIRSTUDIO-115:

This is not a problem for all operational attributes (most likely dependent on the user modification
flag in the attribute type).

The attribute in question is one I just added to the schema and as far as I know it is not
actually operational.  I cannot add a value of that type to an extensibleObject entry.

The attributeType is definately in the schema (I can see it in the cn=schema entry and I can
add a value of that type to an entry using another LDAP editor app) .

I think this bug is more to do with LDAP Studio not reading in the schema for some reason.
 I have also tried reconnecting by the way.

> Unable to edit operational attribute values
> -------------------------------------------
>                 Key: DIRSTUDIO-115
>                 URL:
>             Project: Directory LDAP Studio
>          Issue Type: Improvement
>          Components: ldapstudio-browser
>    Affects Versions: 0.9.0
>            Reporter: Martin Alderson
>            Priority: Minor
> In some cases I find myself wanting to edit the value of an operational attribute, but
find myself having to go to a different LDAP editor application to do it (or writing an LDIF).
 I guess Studio is doing this as it is assuming that operational attribute values are not
editable, but in this case it is.

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

View raw message