[ https://issues.apache.org/jira/browse/SYNCOPE-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Francesco Chicchiriccò updated SYNCOPE-360: ------------------------------------------- Fix Version/s: 1.2.0 1.1.1 > 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 > 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