[ https://issues.apache.org/jira/browse/SYNCOPE-215?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Colm O hEigeartaigh updated SYNCOPE-215: ---------------------------------------- Attachment: syncope-215-console.patch I've merged the core/common change to trunk to support this. See attached for the console patch. As per my mail to dev@syncope, I can't get the virtual attribute textfield to go "read-only" when a new read-only virtual attribute is selected: http://syncope-dev.1063484.n5.nabble.com/Wicket-question-td5712680.html Colm. > ReadOnly option for virtual attributes > -------------------------------------- > > Key: SYNCOPE-215 > URL: https://issues.apache.org/jira/browse/SYNCOPE-215 > Project: Syncope > Issue Type: Improvement > Components: core > Affects Versions: 1.0.1-incubating > Environment: Tomcat 7, Microsoft 2008 Server with ActiveDirectory, > PostgreSQL 9.2.1 > Reporter: Jan Bernhardt > Assignee: Colm O hEigeartaigh > Fix For: 1.1.0 > > Attachments: syncope-215-console.patch > > > There are situations when you can not change an attribute value of a remote > resource, since it is read only at the remote resource. To avoid exceptions > within syncope it would be important to set virtual attributes to read only > also. > This would prevent administrators of changing an attribute that can not be > changed within the backend systems. -- 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