You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Emmanuel Lecharny (JIRA)" <ji...@apache.org> on 2015/09/24 15:13:04 UTC

[jira] [Commented] (DIRSERVER-1901) subschemaSubentry attribute only available under root DSE

    [ https://issues.apache.org/jira/browse/DIRSERVER-1901?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14906323#comment-14906323 ] 

Emmanuel Lecharny commented on DIRSERVER-1901:
----------------------------------------------

Actually, RFC 4512 has changed that :

"The subschema discovery mechanism was also clarified to
   indicate that subschema controlling an entry is obtained by reading
   the (sub)entry referred to by that entry's 'subschemaSubentry'
   attribute."

It then becoming mandatory to inject the subschemaSubentry operational attribute in every entry.

> subschemaSubentry attribute only available under root DSE
> ---------------------------------------------------------
>
>                 Key: DIRSERVER-1901
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-1901
>             Project: Directory ApacheDS
>          Issue Type: Improvement
>          Components: core
>    Affects Versions: 2.0.0-M15
>            Reporter: Konrad Windszus
>            Priority: Critical
>             Fix For: 2.0.0
>
>
> The operational attribute "subschemaSubentry" defined in RFC 2251, 6.2 should be exposed under all entries. ApacheDS does only expose that attribute on the root DSE but not under any other node. Some clients rely on that attribute being available under all nodes. Please expose that attribute always. Also compare with http://www.openldap.org/lists/ietf-ldapbis/200103/msg00018.html.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)