You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@syncope.apache.org by "fabio martelli (JIRA)" <ji...@apache.org> on 2012/07/12 12:56:35 UTC

[jira] [Created] (SYNCOPE-108) Wrong de-provisioning in case of different role with the same externat resource

fabio martelli created SYNCOPE-108:
--------------------------------------

             Summary: Wrong de-provisioning in case of different role with the same externat resource
                 Key: SYNCOPE-108
                 URL: https://issues.apache.org/jira/browse/SYNCOPE-108
             Project: Syncope
          Issue Type: Bug
          Components: core
    Affects Versions: 1.0.0-incubating
         Environment: Let's considering a user with two different memberships about two different roles.
Let's supposing to have linked the same resource to the roles above then, removing a membership a de-provisioning request will be propagated towards this resource. This is a very bad behavior: de-provisioning mustn't be propagated because resource remains indirectly linked to the user by the other membership.
            Reporter: fabio martelli
             Fix For: 1.0.0-incubating




--
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

        

[jira] [Resolved] (SYNCOPE-108) Wrong de-provisioning in case of different role with the same externat resource

Posted by "fabio martelli (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SYNCOPE-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

fabio martelli resolved SYNCOPE-108.
------------------------------------

    Resolution: Fixed
    
> Wrong de-provisioning in case of different role with the same externat resource
> -------------------------------------------------------------------------------
>
>                 Key: SYNCOPE-108
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-108
>             Project: Syncope
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.0.0-incubating
>         Environment: Let's considering a user with two different memberships about two different roles.
> Let's supposing to have linked the same resource to the roles above then, removing a membership a de-provisioning request will be propagated towards this resource. This is a very bad behavior: de-provisioning mustn't be propagated because resource remains indirectly linked to the user by the other membership.
>            Reporter: fabio martelli
>            Assignee: fabio martelli
>             Fix For: 1.0.0-incubating
>
>


--
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

        

[jira] [Closed] (SYNCOPE-108) Wrong de-provisioning in case of different role with the same externat resource

Posted by "fabio martelli (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SYNCOPE-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

fabio martelli closed SYNCOPE-108.
----------------------------------


1.0.0-RC3-incubating
                
> Wrong de-provisioning in case of different role with the same externat resource
> -------------------------------------------------------------------------------
>
>                 Key: SYNCOPE-108
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-108
>             Project: Syncope
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.0.0-incubating
>         Environment: Let's considering a user with two different memberships about two different roles.
> Let's supposing to have linked the same resource to the roles above then, removing a membership a de-provisioning request will be propagated towards this resource. This is a very bad behavior: de-provisioning mustn't be propagated because resource remains indirectly linked to the user by the other membership.
>            Reporter: fabio martelli
>            Assignee: fabio martelli
>             Fix For: 1.0.0-incubating
>
>


--
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

        

[jira] [Assigned] (SYNCOPE-108) Wrong de-provisioning in case of different role with the same externat resource

Posted by "fabio martelli (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/SYNCOPE-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

fabio martelli reassigned SYNCOPE-108:
--------------------------------------

    Assignee: fabio martelli
    
> Wrong de-provisioning in case of different role with the same externat resource
> -------------------------------------------------------------------------------
>
>                 Key: SYNCOPE-108
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-108
>             Project: Syncope
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 1.0.0-incubating
>         Environment: Let's considering a user with two different memberships about two different roles.
> Let's supposing to have linked the same resource to the roles above then, removing a membership a de-provisioning request will be propagated towards this resource. This is a very bad behavior: de-provisioning mustn't be propagated because resource remains indirectly linked to the user by the other membership.
>            Reporter: fabio martelli
>            Assignee: fabio martelli
>             Fix For: 1.0.0-incubating
>
>


--
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