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 2007/01/26 02:25:49 UTC

[jira] Commented: (DIRSERVER-835) Trying to modify operational attributes does not cause appropriate errors

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

Emmanuel Lecharny commented on DIRSERVER-835:
---------------------------------------------

Fixed in 1.0.1, with a test on NO_USER_MODIFICATION of each attribute. To be further ...

svn : http://svn.apache.org/viewvc?view=rev&rev=500080


> Trying to modify operational attributes does not cause appropriate errors
> -------------------------------------------------------------------------
>
>                 Key: DIRSERVER-835
>                 URL: https://issues.apache.org/jira/browse/DIRSERVER-835
>             Project: Directory ApacheDS
>          Issue Type: Bug
>    Affects Versions: 1.0.1
>         Environment: * ApacheDS 1.0.1 (SNAPSHOT)
> * Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_07-b03)
> * Windows XP Professional SP2 
>            Reporter: Stefan Zoerner
>         Assigned To: Emmanuel Lecharny
>             Fix For: 1.0.1, 1.5.0
>
>         Attachments: ModifyOperationalAttributeTest.java
>
>
> Trying to modify operational attributes of entries (modifiersName, creatorsName) does not cause approriate errors. FInd attached a JUnit test which performs three modify operations (adding/deleting/reoplacing an operational attribute) with the help of JNDI. All of them do not throw an exception.
> I have checked the test with three other LDAP servers. OpenLDAP and Sun Java System Directory Server return an LDAP code 19 (LDAP_CONSTRAINT_VIOLATION), IBM Tivoli Directory Server returns 50 (LDAP_INSUFFICIENT_ACCESS).

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