[
https://issues.apache.org/jira/browse/SYNCOPE-185?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13434173#comment-13434173
]
fabio martelli commented on SYNCOPE-185:
----------------------------------------
This issue has been introduced fixing
https://issues.apache.org/jira/browse/SYNCOPE-108.
If I well remember, the case is: a user with two memberships related to two
different roles referring the same resource.
If a membership is removed syncope mustn't perform a delete but an update in
order to perform changes on remote attributes mapped on role or membership
attributes.
> Could not delete an user with LDAP resource
> -------------------------------------------
>
> Key: SYNCOPE-185
> URL: https://issues.apache.org/jira/browse/SYNCOPE-185
> Project: Syncope
> Issue Type: Bug
> Affects Versions: 1.0.0-incubating
> Environment: embedded
> Reporter: Francesco Chicchiriccò
> Fix For: 1.0.1-incubating, 1.1.0-incubating
>
>
> An update operation is issued instead of delete, returning the following
> exception:
> 17:00:11.708 DEBUG
> org.identityconnectors.framework.api.operations.UpdateApiOp.update Exception:
> org.identityconnectors.framework.common.exceptions.ConnectorException:
> javax.naming.NameAlreadyBoundException: [LDAP: error code 68 - Attempt to
> move entry onto itself.]; remaining name '[email protected],ou=people,o=isp'
> [...]
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
