[
https://issues.apache.org/jira/browse/DIRSERVER-837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Zoerner updated DIRSERVER-837:
-------------------------------------
Attachment: ModifySubschemaSubentryAttributeTest.java
Here is the test case for this issue. I have successfully tested it on
* Sun Java System Directory Server 5.2
* IBM Tivoli Directory Server 6.0
* OpenLDAP 2.3
On the current ApacheDS 1.5.0 snapshot, the test method fails.
> LDAP clients are able to modify the subschemaSubentry attribute
> ---------------------------------------------------------------
>
> Key: DIRSERVER-837
> URL: https://issues.apache.org/jira/browse/DIRSERVER-837
> Project: Directory ApacheDS
> Issue Type: Bug
> Affects Versions: 1.5.0
> Environment: * ApacheDS 1.5.0 (SNAPSHOT)
> * Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-b03)
> * Windows XP Professional SP2
> Reporter: Stefan Zoerner
> Fix For: 1.5.0
>
> Attachments: ModifySubschemaSubentryAttributeTest.java
>
>
> RFC 2251 states
> --->8---
> Entries MAY contain, among others, the following operational attributes,
> defined in [...]. These attributes are maintained automatically by the server
> and are not modifiable by clients:
> - creatorsName: ...
> - createTimestamp: ...
> - modifiersName: ...
> - modifyTimestamp: ...
> - subschemaSubentry: ...
> ---8<---
> In the current 1.5.0, clients can add a subschemaSubentry attribute value via
> a modify operation. I'll attach a JUnit testcase which demonstrates the
> problem.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
