[jira] [Commented] (SYNCOPE-336) Use a auto-complete textfield to chose for external attribute to be mapped during schema mapping creation
[ https://issues.apache.org/jira/browse/SYNCOPE-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13643408#comment-13643408 ] Hudson commented on SYNCOPE-336: Integrated in Syncope-1_1_X #27 (See [https://builds.apache.org/job/Syncope-1_1_X/27/]) SYNCOPE-336 resolved (Revision 1476262) Result = SUCCESS fmartelli : Files : * /syncope/branches/1_1_X/common/src/main/java/org/apache/syncope/common/types/EntityViolationType.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/persistence/validation/entity/AbstractValidator.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/persistence/validation/entity/AttrValidator.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/persistence/validation/entity/AttrValueValidator.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/persistence/validation/entity/ConnInstanceValidator.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/persistence/validation/entity/EntitlementValidator.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/persistence/validation/entity/ExternalResourceValidator.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/persistence/validation/entity/InvalidEntityException.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/persistence/validation/entity/NotificationValidator.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/persistence/validation/entity/PolicyValidator.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/persistence/validation/entity/PropagationTaskValidator.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/persistence/validation/entity/ReportValidator.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/persistence/validation/entity/SchedTaskValidator.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/persistence/validation/entity/SchemaValidator.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/persistence/validation/entity/SyncTaskValidator.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/persistence/validation/entity/SyncopeRoleValidator.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/persistence/validation/entity/SyncopeUserValidator.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/persistence/validation/entity/USchemaValidator.java * /syncope/branches/1_1_X/core/src/main/webapp/syncopeClientError.jsp > Use a auto-complete textfield to chose for external attribute to be mapped > during schema mapping creation > - > > Key: SYNCOPE-336 > URL: https://issues.apache.org/jira/browse/SYNCOPE-336 > Project: Syncope > Issue Type: Bug > Components: console >Reporter: fabio martelli >Assignee: fabio martelli > Fix For: 1.0.7, 1.1.0 > > > Sometimes external resource can expect one or more special attribute, not > explicitly included into the schema, to perform a certain operation. Think > about ldapGroups for AD or LDAPv3 connectors. > If a resource implement the schema method, the administration console won't > give the possibility to map external attribute not included into the resource > schema. > This seems to be a great limitation that can be simply removed by changing > the dropdown choice used to chose for an external attribute to be mapped with > an auto-complete textfield. -- 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
[jira] [Commented] (SYNCOPE-336) Use a auto-complete textfield to chose for external attribute to be mapped during schema mapping creation
[ https://issues.apache.org/jira/browse/SYNCOPE-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13606425#comment-13606425 ] Hudson commented on SYNCOPE-336: Integrated in Syncope-trunk #160 (See [https://builds.apache.org/job/Syncope-trunk/160/]) SYNCOPE-336 fixed (Revision 1458310) Result = SUCCESS fmartelli : Files : * /syncope/trunk/common/src/main/java/org/apache/syncope/common/types/MappingPurpose.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/Resources.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/panels/ResourceMappingPanel.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/wicket/markup/html/form/AjaxTextFieldPanel.java * /syncope/trunk/console/src/main/resources/org/apache/syncope/console/pages/BaseModalPage.html * /syncope/trunk/console/src/main/resources/org/apache/syncope/console/pages/BasePage.html > Use a auto-complete textfield to chose for external attribute to be mapped > during schema mapping creation > - > > Key: SYNCOPE-336 > URL: https://issues.apache.org/jira/browse/SYNCOPE-336 > Project: Syncope > Issue Type: Bug > Components: console >Reporter: fabio martelli >Assignee: fabio martelli > Fix For: 1.0.7, 1.1.0 > > > Sometimes external resource can expect one or more special attribute, not > explicitly included into the schema, to perform a certain operation. Think > about ldapGroups for AD or LDAPv3 connectors. > If a resource implement the schema method, the administration console won't > give the possibility to map external attribute not included into the resource > schema. > This seems to be a great limitation that can be simply removed by changing > the dropdown choice used to chose for an external attribute to be mapped with > an auto-complete textfield. -- 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
[jira] [Commented] (SYNCOPE-336) Use a auto-complete textfield to chose for external attribute to be mapped during schema mapping creation
[ https://issues.apache.org/jira/browse/SYNCOPE-336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13601031#comment-13601031 ] Hudson commented on SYNCOPE-336: Integrated in Syncope-1_0_X #160 (See [https://builds.apache.org/job/Syncope-1_0_X/160/]) SYNCOPE-336 fixed into the branch 1_0_X (Revision 1455848) Result = SUCCESS fmartelli : Files : * /syncope/branches/1_0_X/console/src/main/java/org/apache/syncope/console/pages/panels/ResourceMappingPanel.java * /syncope/branches/1_0_X/console/src/main/java/org/apache/syncope/console/wicket/markup/html/form/AjaxTextFieldPanel.java > Use a auto-complete textfield to chose for external attribute to be mapped > during schema mapping creation > - > > Key: SYNCOPE-336 > URL: https://issues.apache.org/jira/browse/SYNCOPE-336 > Project: Syncope > Issue Type: Bug > Components: console >Reporter: fabio martelli >Assignee: fabio martelli > Fix For: 1.0.7, 1.1.0 > > > Sometimes external resource can expect one or more special attribute, not > explicitly included into the schema, to perform a certain operation. Think > about ldapGroups for AD or LDAPv3 connectors. > If a resource implement the schema method, the administration console won't > give the possibility to map external attribute not included into the resource > schema. > This seems to be a great limitation that can be simply removed by changing > the dropdown choice used to chose for an external attribute to be mapped with > an auto-complete textfield. -- 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
