You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@syncope.apache.org by "Francesco Chicchiriccò (JIRA)" <ji...@apache.org> on 2013/04/19 11:39:15 UTC

[jira] [Resolved] (SYNCOPE-360) Removing Role mapping from External Resource fails

     [ https://issues.apache.org/jira/browse/SYNCOPE-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Francesco Chicchiriccò resolved SYNCOPE-360.
--------------------------------------------

    Resolution: Fixed

1_1_X: http://svn.apache.org/r1469758
trunk: http://svn.apache.org/r1469759
                
> Removing Role mapping from External Resource fails
> --------------------------------------------------
>
>                 Key: SYNCOPE-360
>                 URL: https://issues.apache.org/jira/browse/SYNCOPE-360
>             Project: Syncope
>          Issue Type: Bug
>          Components: console
>    Affects Versions: 1.1.0
>         Environment: Linux/Tomcat
>            Reporter: Martin van Es
>            Assignee: Francesco Chicchiriccò
>             Fix For: 1.1.1, 1.2.0
>
>
> Today I was experimenting with role assignment and tried to map internal ROLE/RoleId to a column in my synchronisation CSVdir resource. While syncing I got an error of Objectclasses not matching so I wanted to remove this relationship by clicking the checkbox in from of it, which succeeded. But after saving the new settings and inspecting the resource role mapping, the old role relation was still there, effectively leaving me with a broken resource. I had to manually remove the role map using my database gui to be able to use the resource again.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira