[
https://issues.apache.org/jira/browse/SYNCOPE-1853?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17914889#comment-17914889
]
ASF subversion and git services commented on SYNCOPE-1853:
----------------------------------------------------------
Commit 4b13569785933e6ab0e795ac2931374c4fd1e398 in syncope's branch
refs/heads/master from Andrea Patricelli
[ https://gitbox.apache.org/repos/asf?p=syncope.git;h=4b13569785 ]
SYNCOPE-1853 avoid unwanted user/any deprovision on group delete (#958) (#961)
* [SYNCOPE-1853] Avoid unwanted user/any object propagation on group delete
> Deprovision is wrongly fired on group delete
> --------------------------------------------
>
> Key: SYNCOPE-1853
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1853
> Project: Syncope
> Issue Type: Bug
> Components: core
> Affects Versions: 3.0.10
> Reporter: Andrea Patricelli
> Assignee: Andrea Patricelli
> Priority: Major
> Fix For: 3.0.11, 4.0.0
>
>
> Having three groups GA, GB and GC, resource RA and user UA that belongs to
> all of these groups:
> # Group {{GA}} creation and resource {{RA}} association
> # Group {{GB}} creation and resource {{RA}} association
> # Group {{GC}} creation and resource {{RA}} association
> # Create a user {{UA}} and configure it as a member of {{{}GA{}}},
> {{{}GB{}}}, or {{{}GC{}}}.
> # Delete Group {{GA}}
> This results in a deprovision of User UA from resource RA though user is
> still linked to RA through GB and GC memberships.
> Deprovision in this case must not be fired.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
