[ 
https://issues.apache.org/jira/browse/DIRSTUDIO-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12618653#action_12618653
 ] 

Emmanuel Lecharny commented on DIRSTUDIO-365:
---------------------------------------------

That's very strange... As the server is returning a 50 error, it seems that the 
problem is on the server, not on studio. Now, if you are able to delete the 
entry with an old version of Studio ...

You have to know that to be able to delete an entry, some condition mut be 
fulfilled :
- the user 'own' the entry
- or the user has the right to delete the entry (check the ACI on your server)
- the entry must _not_ have sub-elements

Can you provide a LDIF dump of this entry, including _all_ the operational 
attributes ?

Now, as Studio is based on JNDI to operate. I don't think we have changed a lot 
the way the delete operation works on Studio since the first version (Stefan, 
can you confirm ?). A good way to check what is goind on would be to capture 
some network exchanges with WireShark to see what exactly is sent and received.

> Can't delete entry with studio 1.1.0. works with 1.0.1
> ------------------------------------------------------
>
>                 Key: DIRSTUDIO-365
>                 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-365
>             Project: Directory Studio
>          Issue Type: Bug
>          Components: studio-ldapbrowser
>    Affects Versions: 1.1.0
>         Environment: Studion 1.1.0 standalone or within an existing eclipse 
> installation. IBM directory server 
>            Reporter: Dominique Jean-Prost
>
> Using studio 1.0.1, I can delete an entry using the principal I usually use.
> With the same connection and studion 1.1.0, it fails telling me Error 50.
> !ENTRY org.apache.directory.studio.connection.core 4 4 2008-07-31 11:15:07.806
> !MESSAGE Error while deleting entry
> !STACK 0
> javax.naming.NoPermissionException: [LDAP: error code 50 - Insufficient 
> Access Rights]; remaining name 'cn=JLS,ou=appli,ou=frisco,o=INTERNET'
>       at com.sun.jndi.ldap.LdapCtx.mapErrorCode(LdapCtx.java:2993)
>       at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2931)
>       at com.sun.jndi.ldap.LdapCtx.processReturnCode(LdapCtx.java:2737)
>       at com.sun.jndi.ldap.LdapCtx.c_destroySubcontext(LdapCtx.java:826)
>       at 
> com.sun.jndi.toolkit.ctx.ComponentContext.p_destroySubcontext(ComponentContext.java:653)
>       at 
> com.sun.jndi.toolkit.ctx.PartialCompositeContext.destroySubcontext(PartialCompositeContext.java:336)
>       at 
> org.apache.directory.studio.connection.core.io.jndi.JNDIConnectionWrapper$5.run(JNDIConnectionWrapper.java:717)
>       at 
> org.apache.directory.studio.connection.core.io.jndi.JNDIConnectionWrapper.runAndMonitor(JNDIConnectionWrapper.java:1047)
>       at 
> org.apache.directory.studio.connection.core.io.jndi.JNDIConnectionWrapper.checkConnectionAndRunAndMonitor(JNDIConnectionWrapper.java:978)
>       at 
> org.apache.directory.studio.connection.core.io.jndi.JNDIConnectionWrapper.deleteEntry(JNDIConnectionWrapper.java:757)
>       at 
> org.apache.directory.studio.ldapbrowser.core.jobs.DeleteEntriesJob.deleteEntry(DeleteEntriesJob.java:361)
>       at 
> org.apache.directory.studio.ldapbrowser.core.jobs.DeleteEntriesJob.optimisticDeleteEntryRecursive(DeleteEntriesJob.java:221)
>       at 
> org.apache.directory.studio.ldapbrowser.core.jobs.DeleteEntriesJob.executeNotificationJob(DeleteEntriesJob.java:143)
>       at 
> org.apache.directory.studio.ldapbrowser.core.jobs.AbstractNotificationJob.executeAsyncJob(AbstractNotificationJob.java:43)
>       at 
> org.apache.directory.studio.ldapbrowser.core.jobs.AbstractEclipseJob.run(AbstractEclipseJob.java:101)
>       at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> !SUBENTRY 1 org.apache.directory.studio.connection.core 4 4 2008-07-31 
> 11:15:07.806
> !MESSAGE [LDAP: error code 50 - Insufficient Access Rights]

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

Reply via email to