[jira] [Commented] (SYNCOPE-441) Index on Activiti table boosts overall performance
[ https://issues.apache.org/jira/browse/SYNCOPE-441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13826712#comment-13826712 ] Hudson commented on SYNCOPE-441: SUCCESS: Integrated in Syncope-1_1_X #140 (See [https://builds.apache.org/job/Syncope-1_1_X/140/]) [SYNCOPE-441] Suggested index added to default set and tested on all supported DBMS (ilgrosso: rev 1543361) * /syncope/branches/1_1_X/core/src/main/resources/indexes.xml Index on Activiti table boosts overall performance -- Key: SYNCOPE-441 URL: https://issues.apache.org/jira/browse/SYNCOPE-441 Project: Syncope Issue Type: Improvement Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Fix For: 1.1.5, 1.2.0 As reported in mailing list [1], creating an index on ACT_RU_TASKS may improve significantly the overall system performance: CREATE INDEX RU_TEST ON ACT_RU_TASK (PARENT_TASK_ID_) The idea is to add such index to [2] in order to create it by default in every deployment. [1] http://markmail.org/message/qvriwnmaudm2vn27 [2] https://svn.apache.org/repos/asf/syncope/branches/1_1_X/core/src/main/resources/indexes.xml -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (SYNCOPE-423) Improve notifications
[ https://issues.apache.org/jira/browse/SYNCOPE-423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13826713#comment-13826713 ] Hudson commented on SYNCOPE-423: SUCCESS: Integrated in Syncope-1_1_X #140 (See [https://builds.apache.org/job/Syncope-1_1_X/140/]) SYNCOPE-422 and SYNCOPE-423 fixed on 1.1.X (fmartelli: rev 1543381) * /syncope/branches/1_1_X/client/src/main/java/org/apache/syncope/client/services/proxy/WorkflowServiceProxy.java * /syncope/branches/1_1_X/common/src/main/java/org/apache/syncope/common/services/WorkflowService.java * /syncope/branches/1_1_X/common/src/main/java/org/apache/syncope/common/to/EventCategoryTO.java * /syncope/branches/1_1_X/common/src/main/java/org/apache/syncope/common/types/AuditElements.java * /syncope/branches/1_1_X/common/src/main/java/org/apache/syncope/common/types/AuditLoggerName.java * /syncope/branches/1_1_X/common/src/main/java/org/apache/syncope/common/util/LoggerEventUtils.java * /syncope/branches/1_1_X/console/src/main/java/org/apache/syncope/console/pages/NotificationModalPage.java * /syncope/branches/1_1_X/console/src/main/java/org/apache/syncope/console/pages/Reports.java * /syncope/branches/1_1_X/console/src/main/java/org/apache/syncope/console/pages/Roles.java * /syncope/branches/1_1_X/console/src/main/java/org/apache/syncope/console/pages/panels/LoggerCategoryPanel.java * /syncope/branches/1_1_X/console/src/main/java/org/apache/syncope/console/pages/panels/RoleSearchPanel.java * /syncope/branches/1_1_X/console/src/main/java/org/apache/syncope/console/rest/NotificationRestClient.java * /syncope/branches/1_1_X/console/src/main/resources/org/apache/syncope/console/pages/NotificationModalPage.html * /syncope/branches/1_1_X/console/src/main/resources/org/apache/syncope/console/pages/NotificationModalPage.properties * /syncope/branches/1_1_X/console/src/main/resources/org/apache/syncope/console/pages/NotificationModalPage_it.properties * /syncope/branches/1_1_X/console/src/main/resources/org/apache/syncope/console/pages/NotificationModalPage_pt_BR.properties * /syncope/branches/1_1_X/console/src/main/resources/org/apache/syncope/console/pages/panels/LoggerCategoryPanel.html * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/rest/controller/WorkflowController.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/services/ControllerHandler.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/services/ServiceHandler.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/services/WorkflowServiceImpl.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/workflow/WorkflowAdapter.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/workflow/role/NoOpRoleWorkflowAdapter.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/workflow/user/NoOpUserWorkflowAdapter.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/workflow/user/activiti/ActivitiUserWorkflowAdapter.java * /syncope/branches/1_1_X/core/src/main/resources/restContext.xml * /syncope/branches/1_1_X/core/src/test/java/org/apache/syncope/core/rest/WorkflowTestITCase.java * /syncope/branches/1_1_X/core/src/test/resources/content.xml Improve notifications - Key: SYNCOPE-423 URL: https://issues.apache.org/jira/browse/SYNCOPE-423 Project: Syncope Issue Type: Bug Components: console, core Affects Versions: 1.1.5, 1.2.0 Reporter: fabio martelli Fix For: 1.1.5, 1.2.0 1. extend notification in case of failures 2. provide the possibility to define notification task for whatever event 3. create notification task per propagation task (if notification for propagation.resource name event has been defined) 4. create notification task per synchronization task and sched task (if notification for sync.task/sched.task event has been defined) 5. create notification task about global propagation status (if notification for propagation event has been defined) 6. extend NotificationManager.getNotificationTask(...) in order to provide generic parameters to be included into the e-mail template model -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (SYNCOPE-422) Improve audit info
[ https://issues.apache.org/jira/browse/SYNCOPE-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13826714#comment-13826714 ] Hudson commented on SYNCOPE-422: SUCCESS: Integrated in Syncope-1_1_X #140 (See [https://builds.apache.org/job/Syncope-1_1_X/140/]) SYNCOPE-422 and SYNCOPE-423 fixed on 1.1.X (fmartelli: rev 1543381) * /syncope/branches/1_1_X/client/src/main/java/org/apache/syncope/client/services/proxy/WorkflowServiceProxy.java * /syncope/branches/1_1_X/common/src/main/java/org/apache/syncope/common/services/WorkflowService.java * /syncope/branches/1_1_X/common/src/main/java/org/apache/syncope/common/to/EventCategoryTO.java * /syncope/branches/1_1_X/common/src/main/java/org/apache/syncope/common/types/AuditElements.java * /syncope/branches/1_1_X/common/src/main/java/org/apache/syncope/common/types/AuditLoggerName.java * /syncope/branches/1_1_X/common/src/main/java/org/apache/syncope/common/util/LoggerEventUtils.java * /syncope/branches/1_1_X/console/src/main/java/org/apache/syncope/console/pages/NotificationModalPage.java * /syncope/branches/1_1_X/console/src/main/java/org/apache/syncope/console/pages/Reports.java * /syncope/branches/1_1_X/console/src/main/java/org/apache/syncope/console/pages/Roles.java * /syncope/branches/1_1_X/console/src/main/java/org/apache/syncope/console/pages/panels/LoggerCategoryPanel.java * /syncope/branches/1_1_X/console/src/main/java/org/apache/syncope/console/pages/panels/RoleSearchPanel.java * /syncope/branches/1_1_X/console/src/main/java/org/apache/syncope/console/rest/NotificationRestClient.java * /syncope/branches/1_1_X/console/src/main/resources/org/apache/syncope/console/pages/NotificationModalPage.html * /syncope/branches/1_1_X/console/src/main/resources/org/apache/syncope/console/pages/NotificationModalPage.properties * /syncope/branches/1_1_X/console/src/main/resources/org/apache/syncope/console/pages/NotificationModalPage_it.properties * /syncope/branches/1_1_X/console/src/main/resources/org/apache/syncope/console/pages/NotificationModalPage_pt_BR.properties * /syncope/branches/1_1_X/console/src/main/resources/org/apache/syncope/console/pages/panels/LoggerCategoryPanel.html * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/rest/controller/WorkflowController.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/services/ControllerHandler.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/services/ServiceHandler.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/services/WorkflowServiceImpl.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/workflow/WorkflowAdapter.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/workflow/role/NoOpRoleWorkflowAdapter.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/workflow/user/NoOpUserWorkflowAdapter.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/workflow/user/activiti/ActivitiUserWorkflowAdapter.java * /syncope/branches/1_1_X/core/src/main/resources/restContext.xml * /syncope/branches/1_1_X/core/src/test/java/org/apache/syncope/core/rest/WorkflowTestITCase.java * /syncope/branches/1_1_X/core/src/test/resources/content.xml Improve audit info -- Key: SYNCOPE-422 URL: https://issues.apache.org/jira/browse/SYNCOPE-422 Project: Syncope Issue Type: Improvement Components: core Affects Versions: 1.1.5, 1.2.0 Reporter: fabio martelli Assignee: fabio martelli Fix For: 1.1.5, 1.2.0 1. provide info in case of operation failures as well (currently missing) 2. increase audit info message length bounds 3. increase audit info in case of create/delete/update user/role/membership/resource -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (SYNCOPE-436) Read-only virtual attribute values not retrieved from external resource
[ https://issues.apache.org/jira/browse/SYNCOPE-436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13825297#comment-13825297 ] Hudson commented on SYNCOPE-436: FAILURE: Integrated in Syncope-trunk #503 (See [https://builds.apache.org/job/Syncope-trunk/503/]) SYNCOPE-436 Merge from 1_1_X (mdisabatino: rev 1542946) * /syncope/trunk/build-tools/src/main/resources/content.ldif * /syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/data/AbstractAttributableDataBinder.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/util/MappingUtil.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/persistence/dao/VirSchemaTest.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/TaskTestITCase.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/UserTestITCase.java * /syncope/trunk/core/src/test/resources/content.xml Read-only virtual attribute values not retrieved from external resource --- Key: SYNCOPE-436 URL: https://issues.apache.org/jira/browse/SYNCOPE-436 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.1.4 Reporter: Marco Di Sabatino Di Diodoro Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.1.5, 1.2.0 If you set a virtual attribute to read only, Apache Syncope does not retrieve the value of the field. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (SYNCOPE-436) Read-only virtual attribute values not retrieved from external resource
[ https://issues.apache.org/jira/browse/SYNCOPE-436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13826144#comment-13826144 ] Hudson commented on SYNCOPE-436: SUCCESS: Integrated in Syncope-1_1_X #139 (See [https://builds.apache.org/job/Syncope-1_1_X/139/]) SYNCOPE-436 fix test for readonly virtual attributes (mdisabatino: rev 1543069) * /syncope/branches/1_1_X/core/src/test/java/org/apache/syncope/core/rest/TaskTestITCase.java Read-only virtual attribute values not retrieved from external resource --- Key: SYNCOPE-436 URL: https://issues.apache.org/jira/browse/SYNCOPE-436 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.1.4 Reporter: Marco Di Sabatino Di Diodoro Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.1.5, 1.2.0 If you set a virtual attribute to read only, Apache Syncope does not retrieve the value of the field. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (SYNCOPE-436) Read-only virtual attribute values not retrieved from external resource
[ https://issues.apache.org/jira/browse/SYNCOPE-436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13826149#comment-13826149 ] Hudson commented on SYNCOPE-436: SUCCESS: Integrated in Syncope-trunk #504 (See [https://builds.apache.org/job/Syncope-trunk/504/]) SYNCOPE-436 Merge from 1_1_X (mdisabatino: rev 1543073) * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/TaskTestITCase.java Read-only virtual attribute values not retrieved from external resource --- Key: SYNCOPE-436 URL: https://issues.apache.org/jira/browse/SYNCOPE-436 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.1.4 Reporter: Marco Di Sabatino Di Diodoro Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.1.5, 1.2.0 If you set a virtual attribute to read only, Apache Syncope does not retrieve the value of the field. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (SYNCOPE-439) Embed Activiti modeler for graphical workflow editing
[ https://issues.apache.org/jira/browse/SYNCOPE-439?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13823260#comment-13823260 ] Hudson commented on SYNCOPE-439: SUCCESS: Integrated in Syncope-trunk #502 (See [https://builds.apache.org/job/Syncope-trunk/502/]) Preparations for SYNCOPE-439: now Activiti workflow definition can be read and set either as XML and JSON (ilgrosso: rev 1541959) * /syncope/trunk/common/src/main/java/org/apache/syncope/common/services/ConfigurationService.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/services/WorkflowService.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/to/WorkflowDefinitionTO.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/types/AttributableType.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/types/AuditElements.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/types/RESTHeaders.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/types/ResourceOperation.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/SyncopeSession.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/commons/HttpResourceStream.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/Configuration.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/rest/WorkflowRestClient.java * /syncope/trunk/core/pom.xml * /syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/controller/WorkflowController.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/utils/RestServiceExceptionMapper.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/services/ConfigurationServiceImpl.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/services/ConnectorServiceImpl.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/services/NotificationServiceImpl.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/services/ReportServiceImpl.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/services/ResourceServiceImpl.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/services/RoleServiceImpl.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/services/SchemaServiceImpl.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/services/TaskServiceImpl.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/services/UserSelfServiceImpl.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/services/UserServiceImpl.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/services/WorkflowServiceImpl.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/workflow/WorkflowAdapter.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/workflow/WorkflowDefinitionFormat.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/workflow/role/NoOpRoleWorkflowAdapter.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/workflow/user/NoOpUserWorkflowAdapter.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/workflow/user/activiti/ActivitiImportUtils.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/workflow/user/activiti/ActivitiUserWorkflowAdapter.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/workflow/user/activiti/ActivitiWorkflowLoader.java * /syncope/trunk/core/src/main/resources/userWorkflow.bpmn20.xml * /syncope/trunk/core/src/main/resources/workflowContext.xml * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/AbstractTest.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/ConfigurationTestITCase.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/ReportTestITCase.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/WorkflowTestITCase.java * /syncope/trunk/core/src/test/resources/content.xml * /syncope/trunk/pom.xml Embed Activiti modeler for graphical workflow editing - Key: SYNCOPE-439 URL: https://issues.apache.org/jira/browse/SYNCOPE-439 Project: Syncope Issue Type: Improvement Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Labels: activiti, editor, workflow Fix For: 1.2.0 Activiti, the default user workflow engine, is shipping in its latest versions the open source version of the KIS BPM process solution. Basically, a web editor that can be used to author BPMN 2.0 compliant processes graphically. More information at: http://www.activiti.org/components.html The idea is to embed such component in the admin console, next to the current XML-based editor. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (SYNCOPE-437) Wrong ID generation for new Notification instances
[ https://issues.apache.org/jira/browse/SYNCOPE-437?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1380#comment-1380 ] Hudson commented on SYNCOPE-437: SUCCESS: Integrated in Syncope-1_1_X #137 (See [https://builds.apache.org/job/Syncope-1_1_X/137/]) [SYNCOPE-437] Patch applied, thanks (ilgrosso: rev 1541481) * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/persistence/beans/Notification.java * /syncope/branches/1_1_X/core/src/main/resources/META-INF/orm.xml * /syncope/branches/1_1_X/core/src/main/resources/META-INF/orm.xml.oracle * /syncope/branches/1_1_X/core/src/main/resources/META-INF/orm.xml.sqlserver * /syncope/branches/1_1_X/core/src/test/java/org/apache/syncope/core/persistence/dao/NotificationTest.java * /syncope/branches/1_1_X/core/src/test/java/org/apache/syncope/core/rest/NotificationTestITCase.java * /syncope/branches/1_1_X/core/src/test/resources/content.xml Wrong ID generation for new Notification instances -- Key: SYNCOPE-437 URL: https://issues.apache.org/jira/browse/SYNCOPE-437 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.1.4 Reporter: Andrea Patricelli Assignee: Andrea Patricelli Fix For: 1.1.5, 1.2.0 Attachments: SYNCOPE-437.patch When creating a new instance of Notification, IDs of created instances start from 1 and not from 100 as expected; this is due to the AUTO generation of IDs for Notification entity. This may lead to possible primary key violation errors; in particular if importing from content.xml notification instances as happens in dev profile. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (SYNCOPE-435) Password not mandatory when subscribing external resource
[ https://issues.apache.org/jira/browse/SYNCOPE-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13820409#comment-13820409 ] Hudson commented on SYNCOPE-435: SUCCESS: Integrated in Syncope-trunk #500 (See [https://builds.apache.org/job/Syncope-trunk/500/]) [SYNCOPE-435] Merge from 1_1_X (ilgrosso: rev 1540975) * /syncope/trunk/common/src/main/java/org/apache/syncope/common/types/ResourceOperation.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/connid/ConnObjectUtil.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/persistence/beans/AbstractDerAttr.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/persistence/beans/user/SyncopeUser.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/propagation/PropagationTaskExecutor.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/propagation/impl/AbstractPropagationTaskExecutor.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/propagation/impl/LDAPMembershipPropagationActions.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/propagation/impl/PropagationManager.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/data/AbstractAttributableDataBinder.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/data/ResourceDataBinder.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/data/SchemaDataBinder.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/data/TaskDataBinder.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/data/UserDataBinder.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/util/AttributableUtil.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/util/JexlUtil.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/util/MappingUtil.java * /syncope/trunk/core/src/main/resources/syncopeContext.xml * /syncope/trunk/core/src/test/java/org/apache/syncope/core/notification/NotificationTest.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/UserTestITCase.java Password not mandatory when subscribing external resource - Key: SYNCOPE-435 URL: https://issues.apache.org/jira/browse/SYNCOPE-435 Project: Syncope Issue Type: Bug Affects Versions: 1.1.4 Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Fix For: 1.1.5, 1.2.0 When users subscribe an external resource, if password mapping for that resource is mandatory, providing a password value should be mandatory as well: unfortunately, this does not happen, as reported in ML [1]. [1] http://syncope-user.1051894.n5.nabble.com/user-resource-removing-and-reassigning-tt5707401.html -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (SYNCOPE-435) Password not mandatory when subscribing external resource
[ https://issues.apache.org/jira/browse/SYNCOPE-435?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13820531#comment-13820531 ] Hudson commented on SYNCOPE-435: SUCCESS: Integrated in Syncope-1_1_X #136 (See [https://builds.apache.org/job/Syncope-1_1_X/136/]) [SYNCOPE-435] Adding logic to asses whether mandatory attributes defined in mapping are actually provided during create() or update() on connectors (ilgrosso: rev 1540775) * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/connid/ConnObjectUtil.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/persistence/beans/AbstractDerAttr.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/persistence/beans/user/SyncopeUser.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/propagation/PropagationException.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/propagation/PropagationTaskExecutor.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/propagation/impl/AbstractPropagationTaskExecutor.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/propagation/impl/LDAPMembershipPropagationActions.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/propagation/impl/PropagationManager.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/rest/data/AbstractAttributableDataBinder.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/rest/data/DerivedSchemaDataBinder.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/rest/data/ResourceDataBinder.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/rest/data/SchemaDataBinder.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/rest/data/TaskDataBinder.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/rest/data/UserDataBinder.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/util/AttributableUtil.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/util/JexlUtil.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/util/MappingUtil.java * /syncope/branches/1_1_X/core/src/main/resources/syncopeContext.xml * /syncope/branches/1_1_X/core/src/test/java/org/apache/syncope/core/rest/UserTestITCase.java Password not mandatory when subscribing external resource - Key: SYNCOPE-435 URL: https://issues.apache.org/jira/browse/SYNCOPE-435 Project: Syncope Issue Type: Bug Affects Versions: 1.1.4 Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Fix For: 1.1.5, 1.2.0 When users subscribe an external resource, if password mapping for that resource is mandatory, providing a password value should be mandatory as well: unfortunately, this does not happen, as reported in ML [1]. [1] http://syncope-user.1051894.n5.nabble.com/user-resource-removing-and-reassigning-tt5707401.html -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (SYNCOPE-422) Improve audit info
[ https://issues.apache.org/jira/browse/SYNCOPE-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13820530#comment-13820530 ] Hudson commented on SYNCOPE-422: SUCCESS: Integrated in Syncope-1_1_X #136 (See [https://builds.apache.org/job/Syncope-1_1_X/136/]) Provided before object about update coming from sync - SYNCOPE-422 and SYNCOPE-423 (fmartelli: rev 1540993) * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/sync/impl/SyncopeSyncResultHandler.java Added event details to the notification model about SYNCOPE-422 and SYNCOP-423 (fmartelli: rev 1540980) * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/notification/NotificationManager.java Improve audit info -- Key: SYNCOPE-422 URL: https://issues.apache.org/jira/browse/SYNCOPE-422 Project: Syncope Issue Type: Improvement Components: core Affects Versions: 1.1.5, 1.2.0 Reporter: fabio martelli Assignee: fabio martelli Fix For: 1.1.5, 1.2.0 1. provide info in case of operation failures as well (currently missing) 2. increase audit info message length bounds 3. increase audit info in case of create/delete/update user/role/membership/resource -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (SYNCOPE-422) Improve audit info
[ https://issues.apache.org/jira/browse/SYNCOPE-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13817645#comment-13817645 ] Hudson commented on SYNCOPE-422: FAILURE: Integrated in Syncope-1_1_X #134 (See [https://builds.apache.org/job/Syncope-1_1_X/134/]) fix attributable about SYNCOPE-422 and SYNCOPE-423 (fmartelli: rev 1540099) * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/sync/impl/SyncopeSyncResultHandler.java fix 'About' condition about SYNCOPE-422 Syncope-423 (fmartelli: rev 1540069) * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/notification/NotificationManager.java Improve audit info -- Key: SYNCOPE-422 URL: https://issues.apache.org/jira/browse/SYNCOPE-422 Project: Syncope Issue Type: Improvement Components: core Affects Versions: 1.1.5, 1.2.0 Reporter: fabio martelli Assignee: fabio martelli Fix For: 1.1.5, 1.2.0 1. provide info in case of operation failures as well (currently missing) 2. increase audit info message length bounds 3. increase audit info in case of create/delete/update user/role/membership/resource -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (SYNCOPE-434) Users can log in the admin console despite of their status
[ https://issues.apache.org/jira/browse/SYNCOPE-434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13816507#comment-13816507 ] Hudson commented on SYNCOPE-434: FAILURE: Integrated in Syncope-trunk #494 (See [https://builds.apache.org/job/Syncope-trunk/494/]) [SYNCOPE-434] Merge from 1_1_X (ilgrosso: rev 1539708) * /syncope/trunk/core/src/main/java/org/apache/syncope/core/security/SyncopeAuthenticationProvider.java * /syncope/trunk/core/src/main/resources/content.xml * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/AuthenticationTestITCase.java * /syncope/trunk/core/src/test/resources/content.xml Users can log in the admin console despite of their status -- Key: SYNCOPE-434 URL: https://issues.apache.org/jira/browse/SYNCOPE-434 Project: Syncope Issue Type: Bug Components: console Affects Versions: 1.1.4 Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Fix For: 1.1.5, 1.2.0 Referring to default user workflow, when an user is just 'created' or even 'suspended', the admin console allows the log in. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (SYNCOPE-434) Users can log in the admin console despite of their status
[ https://issues.apache.org/jira/browse/SYNCOPE-434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13816823#comment-13816823 ] Hudson commented on SYNCOPE-434: SUCCESS: Integrated in Syncope-1_1_X #132 (See [https://builds.apache.org/job/Syncope-1_1_X/132/]) [SYNCOPE-434] Introducing new conf parameter 'authentication.statuses' for user statuses allowed to authenticate (ilgrosso: rev 1539706) * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/security/SyncopeAuthenticationProvider.java * /syncope/branches/1_1_X/core/src/main/resources/content.xml * /syncope/branches/1_1_X/core/src/test/java/org/apache/syncope/core/rest/AuthenticationTestITCase.java * /syncope/branches/1_1_X/core/src/test/resources/content.xml Users can log in the admin console despite of their status -- Key: SYNCOPE-434 URL: https://issues.apache.org/jira/browse/SYNCOPE-434 Project: Syncope Issue Type: Bug Components: console Affects Versions: 1.1.4 Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Fix For: 1.1.5, 1.2.0 Referring to default user workflow, when an user is just 'created' or even 'suspended', the admin console allows the log in. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (SYNCOPE-422) Improve audit info
[ https://issues.apache.org/jira/browse/SYNCOPE-422?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13815121#comment-13815121 ] Hudson commented on SYNCOPE-422: SUCCESS: Integrated in Syncope-1_1_X #131 (See [https://builds.apache.org/job/Syncope-1_1_X/131/]) SYNCOPE-422 SYNCOPE-423 fix onEventAction (mdisabatino: rev 1539378) * /syncope/branches/1_1_X/console/src/main/java/org/apache/syncope/console/pages/panels/LoggerCategoryPanel.java Improve audit info -- Key: SYNCOPE-422 URL: https://issues.apache.org/jira/browse/SYNCOPE-422 Project: Syncope Issue Type: Improvement Components: core Affects Versions: 1.1.5, 1.2.0 Reporter: fabio martelli Assignee: fabio martelli Fix For: 1.1.5, 1.2.0 1. provide info in case of operation failures as well (currently missing) 2. increase audit info message length bounds 3. increase audit info in case of create/delete/update user/role/membership/resource -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (SYNCOPE-423) Improve notifications
[ https://issues.apache.org/jira/browse/SYNCOPE-423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13814368#comment-13814368 ] Hudson commented on SYNCOPE-423: SUCCESS: Integrated in Syncope-1_1_X #130 (See [https://builds.apache.org/job/Syncope-1_1_X/130/]) console improvement about SYNCOPE-422 and SYNCOPE-423 (fmartelli: rev 1539049) * /syncope/branches/1_1_X/console/src/main/java/org/apache/syncope/console/pages/panels/EventSelectionPanel.java * /syncope/branches/1_1_X/console/src/main/java/org/apache/syncope/console/pages/panels/LoggerCategoryPanel.java * /syncope/branches/1_1_X/console/src/main/java/org/apache/syncope/console/pages/panels/SelectedEventsPanel.java * /syncope/branches/1_1_X/console/src/main/resources/org/apache/syncope/console/pages/panels/LoggerCategoryPanel.html * /syncope/branches/1_1_X/console/src/main/resources/org/apache/syncope/console/pages/panels/SelectedEventsPanel.html Centralized notification and auditing message generation. Missing some improvement onto the console see issues SYNCOPE-422 SYNCOPE-423 (fmartelli: rev 1538902) * /syncope/branches/1_1_X/client/src/main/java/org/apache/syncope/client/services/proxy/LoggerServiceProxy.java * /syncope/branches/1_1_X/client/src/test/java/org/apache/syncope/client/test/JSONTest.java * /syncope/branches/1_1_X/common/src/main/java/org/apache/syncope/common/services/LoggerService.java * /syncope/branches/1_1_X/common/src/main/java/org/apache/syncope/common/to/EventCategoryTO.java * /syncope/branches/1_1_X/common/src/main/java/org/apache/syncope/common/types/AuditElements.java * /syncope/branches/1_1_X/common/src/main/java/org/apache/syncope/common/types/AuditLoggerName.java * /syncope/branches/1_1_X/common/src/main/java/org/apache/syncope/common/util/CollectionWrapper.java * /syncope/branches/1_1_X/common/src/main/java/org/apache/syncope/common/util/LoggerEventUtils.java * /syncope/branches/1_1_X/console/src/main/java/org/apache/syncope/console/pages/Configuration.java * /syncope/branches/1_1_X/console/src/main/java/org/apache/syncope/console/pages/NotificationModalPage.java * /syncope/branches/1_1_X/console/src/main/java/org/apache/syncope/console/pages/Reports.java * /syncope/branches/1_1_X/console/src/main/java/org/apache/syncope/console/pages/panels/EventSelectionPanel.java * /syncope/branches/1_1_X/console/src/main/java/org/apache/syncope/console/pages/panels/LoggerCategoryPanel.java * /syncope/branches/1_1_X/console/src/main/java/org/apache/syncope/console/pages/panels/SelectedEventsPanel.java * /syncope/branches/1_1_X/console/src/main/java/org/apache/syncope/console/rest/LoggerRestClient.java * /syncope/branches/1_1_X/console/src/main/java/org/apache/syncope/console/wicket/extensions/markup/html/repeater/data/table/CollectionPanel.java * /syncope/branches/1_1_X/console/src/main/java/org/apache/syncope/console/wicket/extensions/markup/html/repeater/data/table/CollectionPropertyColumn.java * /syncope/branches/1_1_X/console/src/main/resources/org/apache/syncope/console/pages/NotificationModalPage.html * /syncope/branches/1_1_X/console/src/main/resources/org/apache/syncope/console/pages/Reports$AuditCategoryPanel.html * /syncope/branches/1_1_X/console/src/main/resources/org/apache/syncope/console/pages/Reports.html * /syncope/branches/1_1_X/console/src/main/resources/org/apache/syncope/console/pages/panels/AuditEventsPanel.html * /syncope/branches/1_1_X/console/src/main/resources/org/apache/syncope/console/pages/panels/EventSelectionPanel.html * /syncope/branches/1_1_X/console/src/main/resources/org/apache/syncope/console/pages/panels/LoggerCategoryPanel.html * /syncope/branches/1_1_X/console/src/main/resources/org/apache/syncope/console/pages/panels/SelectedEventsPanel.html * /syncope/branches/1_1_X/console/src/main/resources/org/apache/syncope/console/wicket/extensions/markup/html/repeater/data/table/CollectionPanel.html * /syncope/branches/1_1_X/console/src/test/java/org/apache/syncope/console/ConfigurationTestITCase.java * /syncope/branches/1_1_X/console/src/test/java/org/apache/syncope/console/ReportTestITCase.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/audit/AuditManager.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/notification/NotificationJob.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/notification/NotificationManager.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/persistence/dao/impl/AttributableSearchDAOImpl.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/propagation/impl/AbstractPropagationTaskExecutor.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/propagation/impl/PriorityPropagationTaskExecutor.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/quartz/AbstractTaskJob.java *
[jira] [Commented] (SYNCOPE-425) Further REST refactoring
[ https://issues.apache.org/jira/browse/SYNCOPE-425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809014#comment-13809014 ] Hudson commented on SYNCOPE-425: SUCCESS: Integrated in Syncope-trunk #484 (See [https://builds.apache.org/job/Syncope-trunk/484/]) [SYNCOPE-425] Discussed changes and RESTful best practices applied (ilgrosso: rev 1537047) * /syncope/trunk/client/src/main/java/org/apache/syncope/client/rest/RestClientExceptionMapper.java * /syncope/trunk/client/src/main/java/org/apache/syncope/client/rest/RestClientFactoryBean.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/AbstractWrappable.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/SyncopeConstants.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/mod/StatusMod.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/mod/UserMod.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/services/ConfigurationService.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/services/ConnectorService.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/services/EntitlementService.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/services/LoggerService.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/services/NotificationService.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/services/PolicyService.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/services/ReportService.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/services/ResourceService.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/services/RoleService.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/services/SchemaService.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/services/TaskService.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/services/UserRequestService.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/services/UserService.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/services/UserWorkflowService.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/services/WorkflowService.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/to/BulkAssociationAction.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/to/CorrelationRuleClassTO.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/to/EntitlementTO.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/to/JobClassTO.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/to/MailTemplateTO.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/to/PropagationActionClassTO.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/to/PropagationRequestTO.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/to/PropagationTargetsTO.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/to/ResourceNameTO.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/to/SyncActionClassTO.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/to/UserTO.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/to/ValidatorTO.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/types/ClientExceptionType.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/types/RESTHeaders.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/types/ResourceAssociationActionType.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/util/CollectionWrapper.java * /syncope/trunk/common/src/test/java/org/apache/syncope/common/JSONTest.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/SyncopeSession.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/commons/AttributableDataProvider.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/commons/HttpResourceStream.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/commons/StatusBean.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/commons/StatusUtils.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/commons/status * /syncope/trunk/console/src/main/java/org/apache/syncope/console/commons/status/AbstractStatusBeanProvider.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/commons/status/ConnObjectWrapper.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/commons/status/Status.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/commons/status/StatusBean.java *
[jira] [Commented] (SYNCOPE-432) Replace role action labels with icons
[
https://issues.apache.org/jira/browse/SYNCOPE-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809314#comment-13809314
]
Hudson commented on SYNCOPE-432:
SUCCESS: Integrated in Syncope-1_1_X #127 (See
[https://builds.apache.org/job/Syncope-1_1_X/127/])
[SYNCOPE-432] Using ActionLinksPanel and removing TreeActionLinkPanel
(ilgrosso: rev 1537135)
*
/syncope/branches/1_1_X/console/src/main/java/org/apache/syncope/console/pages/panels/RoleSummaryPanel.java
*
/syncope/branches/1_1_X/console/src/main/java/org/apache/syncope/console/pages/panels/RoleTabPanel.java
*
/syncope/branches/1_1_X/console/src/main/java/org/apache/syncope/console/wicket/markup/html/tree/TreeActionLinkPanel.java
*
/syncope/branches/1_1_X/console/src/main/resources/org/apache/syncope/console/pages/panels/RoleSummaryPanel.html
*
/syncope/branches/1_1_X/console/src/main/resources/org/apache/syncope/console/pages/panels/RoleTabPanel.html
*
/syncope/branches/1_1_X/console/src/main/resources/org/apache/syncope/console/wicket/markup/html/tree/TreeActionLinkPanel.html
*
/syncope/branches/1_1_X/console/src/main/resources/org/apache/syncope/console/wicket/markup/html/tree/TreeActionLinkPanel.properties
*
/syncope/branches/1_1_X/console/src/main/resources/org/apache/syncope/console/wicket/markup/html/tree/TreeActionLinkPanel_it.properties
*
/syncope/branches/1_1_X/console/src/main/resources/org/apache/syncope/console/wicket/markup/html/tree/TreeActionLinkPanel_pt_BR.properties
* /syncope/branches/1_1_X/console/src/main/webapp/img/actions/create.png
*
/syncope/branches/1_1_X/console/src/test/java/org/apache/syncope/console/RoleTestITCase.java
Replace role action labels with icons
-
Key: SYNCOPE-432
URL: https://issues.apache.org/jira/browse/SYNCOPE-432
Project: Syncope
Issue Type: Improvement
Components: console
Reporter: Francesco Chicchiriccò
Assignee: Francesco Chicchiriccò
Priority: Minor
Fix For: 1.1.5, 1.2.0
As available throughout the admin console, replace the links for accessing
role management features ('Add child', 'Edit', 'Drop') with icons.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (SYNCOPE-432) Replace role action labels with icons
[
https://issues.apache.org/jira/browse/SYNCOPE-432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13809396#comment-13809396
]
Hudson commented on SYNCOPE-432:
FAILURE: Integrated in Syncope-trunk #485 (See
[https://builds.apache.org/job/Syncope-trunk/485/])
[SYNCOPE-432] Merge from 1_1_X (ilgrosso: rev 1537151)
* /syncope/trunk
*
/syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/panels/RoleSummaryPanel.java
*
/syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/panels/RoleTabPanel.java
*
/syncope/trunk/console/src/main/java/org/apache/syncope/console/wicket/markup/html/tree/TreeActionLinkPanel.java
*
/syncope/trunk/console/src/main/resources/org/apache/syncope/console/pages/panels/RoleSummaryPanel.html
*
/syncope/trunk/console/src/main/resources/org/apache/syncope/console/pages/panels/RoleTabPanel.html
*
/syncope/trunk/console/src/main/resources/org/apache/syncope/console/wicket/markup/html/tree/TreeActionLinkPanel.html
*
/syncope/trunk/console/src/main/resources/org/apache/syncope/console/wicket/markup/html/tree/TreeActionLinkPanel.properties
*
/syncope/trunk/console/src/main/resources/org/apache/syncope/console/wicket/markup/html/tree/TreeActionLinkPanel_it.properties
*
/syncope/trunk/console/src/main/resources/org/apache/syncope/console/wicket/markup/html/tree/TreeActionLinkPanel_pt_BR.properties
* /syncope/trunk/console/src/main/webapp/img/actions/create.png
*
/syncope/trunk/console/src/test/java/org/apache/syncope/console/RoleTestITCase.java
Replace role action labels with icons
-
Key: SYNCOPE-432
URL: https://issues.apache.org/jira/browse/SYNCOPE-432
Project: Syncope
Issue Type: Improvement
Components: console
Reporter: Francesco Chicchiriccò
Assignee: Francesco Chicchiriccò
Priority: Minor
Fix For: 1.1.5, 1.2.0
As available throughout the admin console, replace the links for accessing
role management features ('Add child', 'Edit', 'Drop') with icons.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (SYNCOPE-303) Mapping to SyncopeClientCompositeException on client side
[ https://issues.apache.org/jira/browse/SYNCOPE-303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13806680#comment-13806680 ] Hudson commented on SYNCOPE-303: SUCCESS: Integrated in Syncope-trunk #480 (See [https://builds.apache.org/job/Syncope-trunk/480/]) [SYNCOPE-303] Refactoring exception management, also by avoiding composite exceptions whenever possible (ilgrosso: rev 1536304) * /syncope/trunk/client/src/main/java/org/apache/syncope/client/rest/RestClientExceptionMapper.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/SyncopeConstants.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/types/ClientExceptionType.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/types/SyncopeClientExceptionType.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/validation/SyncopeClientCompositeException.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/validation/SyncopeClientException.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/SyncopeRequestCycleListener.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/AbstractSchedTaskModalPage.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/ApprovalModalPage.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/Configuration.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/ConfigurationModalPage.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/ConnectorModalPage.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/DerivedSchemaModalPage.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/Login.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/NotificationModalPage.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/PolicyModalPage.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/ProvisioningModalPage.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/ReportModalPage.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/Reports.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/RoleModalPage.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/SchemaModalPage.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/StatusModalPage.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/TaskModalPage.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/Todo.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/UserModalPage.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/VirtualSchemaModalPage.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/panels/NotificationTasks.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/panels/PoliciesPanel.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/panels/PropagationTasks.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/panels/RoleSearchResultPanel.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/panels/RoleSummaryPanel.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/panels/SchedTasks.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/panels/SyncTasks.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/panels/UserSearchResultPanel.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/rest/ConnectorRestClient.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/rest/ReportRestClient.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/rest/ResourceRestClient.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/rest/SchemaRestClient.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/rest/TaskRestClient.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/rest/UserRestClient.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/rest/WorkflowRestClient.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/wicket/markup/html/tree/TreeActionLinkPanel.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/persistence/dao/RoleDAO.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/persistence/dao/impl/RoleDAOImpl.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/persistence/validation/attrvalue/ParsingValidationException.java *
[jira] [Commented] (SYNCOPE-426) UserService#update and RoleService#update require entity id to be specified twice
[ https://issues.apache.org/jira/browse/SYNCOPE-426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13805209#comment-13805209 ] Hudson commented on SYNCOPE-426: SUCCESS: Integrated in Syncope-1_1_X #125 (See [https://builds.apache.org/job/Syncope-1_1_X/125/]) [SYNCOPE-426] Setting UserMod#id and RoleMod#id in service implementations, prior to call to controllers (ilgrosso: rev 1535655) * /syncope/branches/1_1_X/client/src/main/java/org/apache/syncope/client/services/proxy/RoleServiceProxy.java * /syncope/branches/1_1_X/client/src/main/java/org/apache/syncope/client/services/proxy/UserServiceProxy.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/services/RoleServiceImpl.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/services/UserServiceImpl.java * /syncope/branches/1_1_X/core/src/test/java/org/apache/syncope/core/rest/UserTestITCase.java UserService#update and RoleService#update require entity id to be specified twice - Key: SYNCOPE-426 URL: https://issues.apache.org/jira/browse/SYNCOPE-426 Project: Syncope Issue Type: Bug Affects Versions: 1.1.4 Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Priority: Minor Labels: rest Fix For: 1.1.5, 1.2.0 As recently reported in mailing list [1], updating an user requires to pass its id both as path parameter and embedded in the provided UserMod. While having both parameters (id and UserMod) seems to be unavoidable to adhere to REST best practices, it would be quite easy to allow an empty id in UserMod. Same applies to role update and RoleMod. [1] http://markmail.org/message/zgh27isscw3hvwfx -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (SYNCOPE-426) UserService#update and RoleService#update require entity id to be specified twice
[ https://issues.apache.org/jira/browse/SYNCOPE-426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13805211#comment-13805211 ] Hudson commented on SYNCOPE-426: FAILURE: Integrated in Syncope-trunk #476 (See [https://builds.apache.org/job/Syncope-trunk/476/]) [SYNCOPE-426] Merge from 1_1_X (ilgrosso: rev 1535657) * /syncope/trunk * /syncope/trunk/common/src/main/java/org/apache/syncope/common/services/UserService.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/services/RoleServiceImpl.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/services/UserServiceImpl.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/UserTestITCase.java UserService#update and RoleService#update require entity id to be specified twice - Key: SYNCOPE-426 URL: https://issues.apache.org/jira/browse/SYNCOPE-426 Project: Syncope Issue Type: Bug Affects Versions: 1.1.4 Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Priority: Minor Labels: rest Fix For: 1.1.5, 1.2.0 As recently reported in mailing list [1], updating an user requires to pass its id both as path parameter and embedded in the provided UserMod. While having both parameters (id and UserMod) seems to be unavoidable to adhere to REST best practices, it would be quite easy to allow an empty id in UserMod. Same applies to role update and RoleMod. [1] http://markmail.org/message/zgh27isscw3hvwfx -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (SYNCOPE-151) Document RESTful services
[ https://issues.apache.org/jira/browse/SYNCOPE-151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13802830#comment-13802830 ] Hudson commented on SYNCOPE-151: SUCCESS: Integrated in Syncope-trunk #469 (See [https://builds.apache.org/job/Syncope-trunk/469/]) [SYNCOPE-151] Introducing support for live RESTful API documentation based on XSLT transformation of WADL dynamically generated by CXF (ilgrosso: rev 1534986) * /syncope/trunk * /syncope/trunk/common/pom.xml * /syncope/trunk/common/src/main/java/org/apache/syncope/common/SyncopeConstants.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/mod/package-info.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/package-info.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/report/package-info.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/search/package-info.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/services/ReportService.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/services/ReportletConfClasses.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/services/UserService.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/services/WorkflowService.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/services/WorkflowTasks.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/to/PropagationTargetsTO.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/to/package-info.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/types/AuditLoggerName.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/types/ReportletConfClasses.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/types/WorkflowTasks.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/types/package-info.java * /syncope/trunk/common/src/test/java/org * /syncope/trunk/common/src/test/java/org/apache/syncope/common/JSONTest.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/rest/ReportRestClient.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/WADLServlet.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/services/ReportServiceImpl.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/services/UserServiceImpl.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/services/WorkflowServiceImpl.java * /syncope/trunk/core/src/main/resources/restContext.xml * /syncope/trunk/core/src/main/resources/wadl2html * /syncope/trunk/core/src/main/resources/wadl2html/index.xsl * /syncope/trunk/core/src/main/resources/wadl2html/schema.xsl * /syncope/trunk/core/src/main/webapp/WEB-INF/web.xml * /syncope/trunk/core/src/main/webapp/css * /syncope/trunk/core/src/main/webapp/css/highlight.css * /syncope/trunk/core/src/main/webapp/css/images * /syncope/trunk/core/src/main/webapp/css/images/ui-bg_flat_0_aa_40x100.png * /syncope/trunk/core/src/main/webapp/css/images/ui-bg_flat_75_ff_40x100.png * /syncope/trunk/core/src/main/webapp/css/images/ui-bg_glass_65_ff_1x400.png * /syncope/trunk/core/src/main/webapp/css/images/ui-bg_glass_75_dadada_1x400.png * /syncope/trunk/core/src/main/webapp/css/images/ui-bg_glass_75_e6e6e6_1x400.png * /syncope/trunk/core/src/main/webapp/css/images/ui-bg_highlight-soft_75_cc_1x100.png * /syncope/trunk/core/src/main/webapp/css/images/ui-icons_454545_256x240.png * /syncope/trunk/core/src/main/webapp/css/images/ui-icons_88_256x240.png * /syncope/trunk/core/src/main/webapp/css/jquery-ui.css * /syncope/trunk/core/src/main/webapp/css/style.css * /syncope/trunk/core/src/main/webapp/js * /syncope/trunk/core/src/main/webapp/js/highlight.pack.js * /syncope/trunk/core/src/main/webapp/js/jquery-ui.js * /syncope/trunk/core/src/main/webapp/js/jquery.js * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/ReportTestITCase.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/ResourceTestITCase.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/WorkflowTestITCase.java * /syncope/trunk/legal_ext/LICENSE * /syncope/trunk/legal_ext/NOTICE * /syncope/trunk/pom.xml Document RESTful services - Key: SYNCOPE-151 URL: https://issues.apache.org/jira/browse/SYNCOPE-151 Project: Syncope Issue Type: Improvement Components: core, documentation Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Labels: rest Fix For: 1.2.0 Provide dynamic documentation for RESTful services: the easiest and most effective way seems to be via XSLT processing of WADL information, auto-generated by CXF (see [1] for more information). Relevant discussion on dev ML: [2]. [1]
[jira] [Commented] (SYNCOPE-420) Provide user / role pre-processing mechanism
[ https://issues.apache.org/jira/browse/SYNCOPE-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13794992#comment-13794992 ] Hudson commented on SYNCOPE-420: SUCCESS: Integrated in Syncope-1_1_X #121 (See [https://builds.apache.org/job/Syncope-1_1_X/121/]) [SYNCOPE-420] Fixing jaxrs errors (ilgrosso: rev 1532232) * /syncope/branches/1_1_X/common/src/main/java/org/apache/syncope/common/mod/AbstractAttributableMod.java * /syncope/branches/1_1_X/common/src/main/java/org/apache/syncope/common/to/AbstractAttributableTO.java Provide user / role pre-processing mechanism Key: SYNCOPE-420 URL: https://issues.apache.org/jira/browse/SYNCOPE-420 Project: Syncope Issue Type: Improvement Components: core Affects Versions: 1.1.5, 1.2.0 Reporter: fabio martelli Assignee: Francesco Chicchiriccò Fix For: 1.1.5, 1.2.0 Before storing/propagating/synchronizing a specific user or role a pre-processor could be called in order to allow any kind of manipulation before any actual operation takes place. The idea is to provide an interface to be implemented into the overlay in order to perform custom pre-processing operations. The custom implementation class name could be defined into the global configuration. This new feature would give the handle to provide several attribute value manipulation like specific value translations, or something else. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (SYNCOPE-420) Provide user / role pre-processing mechanism
[ https://issues.apache.org/jira/browse/SYNCOPE-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13795033#comment-13795033 ] Hudson commented on SYNCOPE-420: SUCCESS: Integrated in Syncope-trunk #465 (See [https://builds.apache.org/job/Syncope-trunk/465/]) [SYNCOPE-420] Merge from 1_1_X (ilgrosso: rev 1532242) * /syncope/trunk * /syncope/trunk/core/pom.xml * /syncope/trunk/core/src/main/java/org/apache/syncope/core/propagation/PropagationHandler.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/propagation/PropagationReporter.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/propagation/PropagationTaskExecutor.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/propagation/impl/AbstractPropagationTaskExecutor.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/propagation/impl/DefaultPropagationHandler.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/propagation/impl/DefaultPropagationReporter.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/propagation/impl/PriorityPropagationTaskExecutor.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/propagation/impl/PropagationManager.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/controller/RoleController.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/controller/UserController.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/data/AbstractAttributableDataBinder.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/data/AttributableTransformer.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/data/DefaultAttributableTransformer.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/sync/impl/SyncopeSyncResultHandler.java * /syncope/trunk/core/src/main/resources/restContext.xml * /syncope/trunk/core/src/main/resources/syncopeContext.xml * /syncope/trunk/core/src/test/java/org/apache/syncope/core/persistence/dao/SchemaTest.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/UserTestITCase.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/data/DefaultAttributableTransformer.java * /syncope/trunk/core/src/test/resources/content.xml Provide user / role pre-processing mechanism Key: SYNCOPE-420 URL: https://issues.apache.org/jira/browse/SYNCOPE-420 Project: Syncope Issue Type: Improvement Components: core Affects Versions: 1.1.5, 1.2.0 Reporter: fabio martelli Assignee: Francesco Chicchiriccò Fix For: 1.1.5, 1.2.0 Before storing/propagating/synchronizing a specific user or role a pre-processor could be called in order to allow any kind of manipulation before any actual operation takes place. The idea is to provide an interface to be implemented into the overlay in order to perform custom pre-processing operations. The custom implementation class name could be defined into the global configuration. This new feature would give the handle to provide several attribute value manipulation like specific value translations, or something else. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (SYNCOPE-132) Don't expose some REST list methods for anonymous
[ https://issues.apache.org/jira/browse/SYNCOPE-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13792685#comment-13792685 ] Hudson commented on SYNCOPE-132: SUCCESS: Integrated in Syncope-trunk #464 (See [https://builds.apache.org/job/Syncope-trunk/464/]) [SYNCOPE-132] Introducing a special 'anonymous' user, with only fixed capabilities to perform self-registration via web console, distinct from actual unauthenticated user that cannot now access any REST resource (ilgrosso: rev 1531307) * /syncope/trunk/archetype/src/main/resources/META-INF/maven/archetype-metadata.xml * /syncope/trunk/archetype/src/main/resources/meta-pom.xml * /syncope/trunk/archetype/src/test/resources/projects/default/archetype.properties * /syncope/trunk/common/src/main/java/org/apache/syncope/common/SyncopeConstants.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/SyncopeApplication.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/SyncopeRequestCycleListener.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/SyncopeSession.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/BasePage.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/Login.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/ResultStatusModalPage.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/UserRequestModalPage.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/WelcomePage.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/panels/UserDetailsPanel.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/rest/UserRestClient.java * /syncope/trunk/console/src/main/resources/applicationContext.xml * /syncope/trunk/console/src/main/resources/authorizations.xml * /syncope/trunk/console/src/main/resources/org/apache/syncope/console/SyncopeApplication.properties * /syncope/trunk/console/src/main/resources/org/apache/syncope/console/SyncopeApplication_it.properties * /syncope/trunk/console/src/main/resources/org/apache/syncope/console/SyncopeApplication_pt_BR.properties * /syncope/trunk/console/src/main/resources/org/apache/syncope/console/pages/BasePage.html * /syncope/trunk/console/src/main/resources/org/apache/syncope/console/pages/WelcomePage.html * /syncope/trunk/console/src/test/java/org/apache/syncope/console/EditProfileTestITCase.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/persistence/validation/entity/SyncopeUserValidator.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/controller/ResourceController.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/controller/RoleController.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/controller/SchemaController.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/controller/UserController.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/controller/UserRequestController.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/data/UserDataBinder.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/security/SyncopeAuthenticationProvider.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/security/SyncopeUserDetailsService.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/util/EntitlementUtil.java * /syncope/trunk/core/src/main/resources/content.xml * /syncope/trunk/core/src/main/resources/security.properties * /syncope/trunk/core/src/main/resources/securityContext.xml * /syncope/trunk/core/src/main/resources/syncopeContext.xml * /syncope/trunk/core/src/test/java/org/apache/syncope/core/persistence/dao/EntitlementTest.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/AbstractTest.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/ResourceTestITCase.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/RoleTestITCase.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/SchemaTestITCase.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/UserRequestTestITCase.java * /syncope/trunk/core/src/test/resources/content.xml * /syncope/trunk/pom.xml Don't expose some REST list methods for anonymous - Key: SYNCOPE-132 URL: https://issues.apache.org/jira/browse/SYNCOPE-132 Project: Syncope Issue Type: Improvement Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Fix For: 1.2.0 Currently, in order to provide some authenticationless features through the console (mainly, self-registration), some REST services don't require any authentication. -- This message was
[jira] [Commented] (SYNCOPE-393) Resource unlink
[ https://issues.apache.org/jira/browse/SYNCOPE-393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13788273#comment-13788273 ] Hudson commented on SYNCOPE-393: SUCCESS: Integrated in Syncope-trunk #458 (See [https://builds.apache.org/job/Syncope-trunk/458/]) SYNCOPE-393 fixed (fmartelli: rev 1529856) * /syncope/trunk/common/src/main/java/org/apache/syncope/common/services/ResourceService.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/services/RoleService.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/services/UserService.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/to/AttributableTargetsTO.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/to/BulkAssociationAction.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/to/PropagationRequestTO.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/to/PropagationTargetsTO.java * /syncope/trunk/console/pom.xml * /syncope/trunk/console/src/main/java/org/apache/syncope/console/commons/ActionTableCheckGroup.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/commons/StatusBean.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/commons/StatusUtils.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/AbstractBasePage.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/AbstractStatusModlaPage.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/ProvisioningModalPage.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/ResourceModalPage.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/ResultStatusModalPage.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/StatusModalPage.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/TaskModalPage.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/Tasks.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/VirtualSchemaModalPage.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/panels/AbstractSearchResultPanel.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/panels/ActionDataTablePanel.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/panels/ImagePanel.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/panels/MembershipsPanel.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/panels/ResourcesPanel.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/panels/RoleSearchResultPanel.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/panels/StatusPanel.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/panels/UserSearchResultPanel.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/rest/ResourceRestClient.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/rest/RoleRestClient.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/rest/UserRestClient.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/wicket/ajax/markup/html/IndicatingDeleteOnConfirmAjaxLink.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/wicket/ajax/markup/html/IndicatingOnConfirmAjaxLink.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/wicket/extensions/markup/html/repeater/data/table/CheckBoxPanel.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/wicket/markup/html/form/ActionLink.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/wicket/markup/html/form/ActionLinksPanel.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/wicket/markup/html/tree/TreeActionLinkPanel.java * /syncope/trunk/console/src/main/resources/authorizations.xml * /syncope/trunk/console/src/main/resources/org/apache/syncope/console/SyncopeApplication.properties * /syncope/trunk/console/src/main/resources/org/apache/syncope/console/SyncopeApplication_it.properties * /syncope/trunk/console/src/main/resources/org/apache/syncope/console/SyncopeApplication_pt_BR.properties * /syncope/trunk/console/src/main/resources/org/apache/syncope/console/pages/AbstractStatusModlaPage.html * /syncope/trunk/console/src/main/resources/org/apache/syncope/console/pages/AbstractStatusModlaPage.properties * /syncope/trunk/console/src/main/resources/org/apache/syncope/console/pages/AbstractStatusModlaPage_it.properties * /syncope/trunk/console/src/main/resources/org/apache/syncope/console/pages/AbstractStatusModlaPage_pt_BR.properties *
[jira] [Commented] (SYNCOPE-424) Resolve OpenJPA dependency overlap
[
https://issues.apache.org/jira/browse/SYNCOPE-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13786282#comment-13786282
]
Hudson commented on SYNCOPE-424:
SUCCESS: Integrated in Syncope-1_1_X #116 (See
[https://builds.apache.org/job/Syncope-1_1_X/116/])
[SYNCOPE-424] Applying provided patch (ilgrosso: rev 1529191)
* /syncope/branches/1_1_X/core/pom.xml
* /syncope/branches/1_1_X/pom.xml
Resolve OpenJPA dependency overlap
--
Key: SYNCOPE-424
URL: https://issues.apache.org/jira/browse/SYNCOPE-424
Project: Syncope
Issue Type: Improvement
Components: core
Affects Versions: 1.1.4, 1.2.0
Reporter: Guido Wimmel
Assignee: Francesco Chicchiriccò
Priority: Minor
Fix For: 1.1.5, 1.2.0
Attachments: syncopeOpenJPADependencies.patch
As discussed on the dev ML [1], the OpenJPA-classes used by Syncope are both
included in openjpa-2.2.2.jar and in {openjpa-kernel-2.2.2.jar,
openjpa-jdbc-2.2.2.jar, openjpa-lib-2.2.2.jar, openjpa-persistence-2.2.2.jar,
openjpa-persistence-jdbc-2.2.2.jar}. Thus, openjpa-2.2.2.jar could be removed.
[1]
http://syncope-dev.1063484.n5.nabble.com/OpenJPA-dependency-overlaps-td5714289.html
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (SYNCOPE-424) Resolve OpenJPA dependency overlap
[
https://issues.apache.org/jira/browse/SYNCOPE-424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13786339#comment-13786339
]
Hudson commented on SYNCOPE-424:
SUCCESS: Integrated in Syncope-trunk #457 (See
[https://builds.apache.org/job/Syncope-trunk/457/])
[SYNCOPE-424] Merge from 1_1_X (ilgrosso: rev 1529193)
* /syncope/trunk
* /syncope/trunk/core/pom.xml
* /syncope/trunk/pom.xml
Resolve OpenJPA dependency overlap
--
Key: SYNCOPE-424
URL: https://issues.apache.org/jira/browse/SYNCOPE-424
Project: Syncope
Issue Type: Improvement
Components: core
Affects Versions: 1.1.4, 1.2.0
Reporter: Guido Wimmel
Assignee: Francesco Chicchiriccò
Priority: Minor
Fix For: 1.1.5, 1.2.0
Attachments: syncopeOpenJPADependencies.patch
As discussed on the dev ML [1], the OpenJPA-classes used by Syncope are both
included in openjpa-2.2.2.jar and in {openjpa-kernel-2.2.2.jar,
openjpa-jdbc-2.2.2.jar, openjpa-lib-2.2.2.jar, openjpa-persistence-2.2.2.jar,
openjpa-persistence-jdbc-2.2.2.jar}. Thus, openjpa-2.2.2.jar could be removed.
[1]
http://syncope-dev.1063484.n5.nabble.com/OpenJPA-dependency-overlaps-td5714289.html
--
This message was sent by Atlassian JIRA
(v6.1#6144)
[jira] [Commented] (SYNCOPE-419) Meaningless error message when attempting to delete user owning role
[ https://issues.apache.org/jira/browse/SYNCOPE-419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13783034#comment-13783034 ] Hudson commented on SYNCOPE-419: SUCCESS: Integrated in Syncope-1_1_X #115 (See [https://builds.apache.org/job/Syncope-1_1_X/115/]) [SYNCOPE-419] Providing dedicated exception type + audit message in case of user delete failure (ilgrosso: rev 1528106) * /syncope/branches/1_1_X/common/src/main/java/org/apache/syncope/common/types/SyncopeClientExceptionType.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/rest/controller/UserController.java Meaningless error message when attempting to delete user owning role Key: SYNCOPE-419 URL: https://issues.apache.org/jira/browse/SYNCOPE-419 Project: Syncope Issue Type: Bug Components: console, core Affects Versions: 1.1.4 Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Fix For: 1.1.5, 1.2.0 When attempting to delete from admin console an user owning one or more roles, a meaningless exception message is reported (try to delete user 5 from test data, for example). -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (SYNCOPE-419) Meaningless error message when attempting to delete user owning role
[ https://issues.apache.org/jira/browse/SYNCOPE-419?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13783074#comment-13783074 ] Hudson commented on SYNCOPE-419: SUCCESS: Integrated in Syncope-trunk #456 (See [https://builds.apache.org/job/Syncope-trunk/456/]) [SYNCOPE-419] Merge from 1_1_X (ilgrosso: rev 1528109) * /syncope/trunk * /syncope/trunk/common/src/main/java/org/apache/syncope/common/types/SyncopeClientExceptionType.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/controller/UserController.java Meaningless error message when attempting to delete user owning role Key: SYNCOPE-419 URL: https://issues.apache.org/jira/browse/SYNCOPE-419 Project: Syncope Issue Type: Bug Components: console, core Affects Versions: 1.1.4 Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Fix For: 1.1.5, 1.2.0 When attempting to delete from admin console an user owning one or more roles, a meaningless exception message is reported (try to delete user 5 from test data, for example). -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Commented] (SYNCOPE-405) Replace logback with log4j 2
[ https://issues.apache.org/jira/browse/SYNCOPE-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13774524#comment-13774524 ] Hudson commented on SYNCOPE-405: SUCCESS: Integrated in Syncope-trunk #453 (See [https://builds.apache.org/job/Syncope-trunk/453/]) [SYNCOPE-405] Completing log4j2 conf with latest features from 2.0-beta9 (ilgrosso: rev 1525566) * /syncope/trunk/console/src/main/resources/log4j2.xml * /syncope/trunk/console/src/main/webapp/WEB-INF/web.xml * /syncope/trunk/core/pom.xml * /syncope/trunk/core/src/main/resources/log4j2.xml * /syncope/trunk/core/src/main/webapp/WEB-INF/web.xml Replace logback with log4j 2 Key: SYNCOPE-405 URL: https://issues.apache.org/jira/browse/SYNCOPE-405 Project: Syncope Issue Type: Improvement Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Fix For: 1.2.0 As discussed in dev ML [1] [1] http://syncope-dev.1063484.n5.nabble.com/DISCUSS-Replace-logback-with-log4j-2-td5714012.html -- 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-417) Users are made active when updating in NoOpWorkflowAdapter
[ https://issues.apache.org/jira/browse/SYNCOPE-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13772881#comment-13772881 ] Hudson commented on SYNCOPE-417: SUCCESS: Integrated in Syncope-1_1_X #110 (See [https://builds.apache.org/job/Syncope-1_1_X/110/]) [SYNCOPE-417] Applying provided patch (ilgrosso: rev 1524937) * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/workflow/user/NoOpUserWorkflowAdapter.java Users are made active when updating in NoOpWorkflowAdapter -- Key: SYNCOPE-417 URL: https://issues.apache.org/jira/browse/SYNCOPE-417 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.1.3 Reporter: Jesse van Bekkum Assignee: Francesco Chicchiriccò Priority: Minor Fix For: 1.1.4, 1.2.0 Attachments: NoOpUserWorkflowAdapter.java.patch When using the NoOpWorkflow adapter a user is always set to active when an update is done, even if the user is suspended. This is undesirable, I think a user should stay in the state it is. This can be fixed by changing this line (117/118 of NoOpWorkflowAdapter.java): return new WorkflowResultMap.EntryLong, Boolean( new AbstractMap.SimpleEntryLong, Boolean(updated.getId(), true), propByRes, update); into this: return new WorkflowResultMap.EntryLong, Boolean( new AbstractMap.SimpleEntryLong, Boolean(updated.getId(), !user.isSuspended()), propByRes, update); -- 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-417) Users are made active when updating in NoOpWorkflowAdapter
[ https://issues.apache.org/jira/browse/SYNCOPE-417?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13772888#comment-13772888 ] Hudson commented on SYNCOPE-417: SUCCESS: Integrated in Syncope-trunk #451 (See [https://builds.apache.org/job/Syncope-trunk/451/]) [SYNCOPE-417] Merge from 1_1_X (ilgrosso: rev 1524938) * /syncope/trunk * /syncope/trunk/core/src/main/java/org/apache/syncope/core/workflow/user/NoOpUserWorkflowAdapter.java Users are made active when updating in NoOpWorkflowAdapter -- Key: SYNCOPE-417 URL: https://issues.apache.org/jira/browse/SYNCOPE-417 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.1.3 Reporter: Jesse van Bekkum Assignee: Francesco Chicchiriccò Priority: Minor Fix For: 1.1.4, 1.2.0 Attachments: NoOpUserWorkflowAdapter.java.patch When using the NoOpWorkflow adapter a user is always set to active when an update is done, even if the user is suspended. This is undesirable, I think a user should stay in the state it is. This can be fixed by changing this line (117/118 of NoOpWorkflowAdapter.java): return new WorkflowResultMap.EntryLong, Boolean( new AbstractMap.SimpleEntryLong, Boolean(updated.getId(), true), propByRes, update); into this: return new WorkflowResultMap.EntryLong, Boolean( new AbstractMap.SimpleEntryLong, Boolean(updated.getId(), !user.isSuspended()), propByRes, update); -- 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-418) Special chars break REST URLs
[ https://issues.apache.org/jira/browse/SYNCOPE-418?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13773046#comment-13773046 ] Hudson commented on SYNCOPE-418: SUCCESS: Integrated in Syncope-trunk #452 (See [https://builds.apache.org/job/Syncope-trunk/452/]) [SYNCOPE-418] Merge from 1_1_X (ilgrosso: rev 1525004) * /syncope/trunk * /syncope/trunk/common/src/main/java/org/apache/syncope/common/types/EntityViolationType.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/types/SyncopeClientExceptionType.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/persistence/beans/AbstractDerSchema.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/persistence/beans/AbstractSchema.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/persistence/beans/AbstractVirSchema.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/persistence/beans/SyncopeConf.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/persistence/beans/user/UDerSchema.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/persistence/beans/user/USchema.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/persistence/beans/user/UVirSchema.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/persistence/validation/attrvalue/EmailAddressValidator.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/persistence/validation/entity/AbstractValidator.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/persistence/validation/entity/AttrValidator.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/persistence/validation/entity/AttrValueValidator.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/persistence/validation/entity/ConnInstanceValidator.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/persistence/validation/entity/ExternalResourceValidator.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/persistence/validation/entity/NotificationValidator.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/persistence/validation/entity/PolicyValidator.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/persistence/validation/entity/PropagationTaskValidator.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/persistence/validation/entity/ReportValidator.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/persistence/validation/entity/SchedTaskValidator.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/persistence/validation/entity/SchemaNameCheck.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/persistence/validation/entity/SchemaNameValidator.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/persistence/validation/entity/SchemaValidator.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/persistence/validation/entity/SyncTaskValidator.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/persistence/validation/entity/SyncopeConfCheck.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/persistence/validation/entity/SyncopeConfValidator.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/persistence/validation/entity/SyncopeRoleValidator.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/persistence/validation/entity/SyncopeUserValidator.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/persistence/validation/entity/USchemaCheck.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/persistence/validation/entity/USchemaValidator.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/data/SchemaDataBinder.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/persistence/dao/AttrTest.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/persistence/dao/ConfTest.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/persistence/dao/DerSchemaTest.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/persistence/dao/ResourceTest.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/persistence/dao/SchemaTest.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/persistence/dao/VirSchemaTest.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/ConfigurationTestITCase.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/DerivedSchemaTestITCase.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/ResourceTestITCase.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/SchemaTestITCase.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/VirtualSchemaTestITCase.java Special chars break REST URLs - Key: SYNCOPE-418 URL:
[jira] [Commented] (SYNCOPE-415) Reduce log level of bean validation errors
[ https://issues.apache.org/jira/browse/SYNCOPE-415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13771719#comment-13771719 ] Hudson commented on SYNCOPE-415: SUCCESS: Integrated in Syncope-1_1_X #107 (See [https://builds.apache.org/job/Syncope-1_1_X/107/]) [SYNCOPE-415] Applying provided patch (ilgrosso: rev 1524643) * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/persistence/validation/entity/EntityValidationInterceptor.java Reduce log level of bean validation errors -- Key: SYNCOPE-415 URL: https://issues.apache.org/jira/browse/SYNCOPE-415 Project: Syncope Issue Type: Improvement Components: core Affects Versions: 1.1.3, 1.2.0 Reporter: Guido Wimmel Assignee: Francesco Chicchiriccò Priority: Minor Fix For: 1.1.4, 1.2.0 Attachments: syncopeBeanValidationLogLevel_1_1_X.patch, syncopeBeanValidationLogLevel_trunk.patch Bean validation errors should not be logged with log level ERROR, as they can be part of normal system behaviour (e.g. a user registers herself or is registered by an admin and accidentally or unknowingly enters invalid data and then gets an error message on the UI). See the discussion on the dev mailing list [1]. [1] http://syncope-dev.1063484.n5.nabble.com/EntityValidationInterceptor-log-level-of-bean-validation-errors-td5714156.html -- 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-415) Reduce log level of bean validation errors
[ https://issues.apache.org/jira/browse/SYNCOPE-415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13771721#comment-13771721 ] Hudson commented on SYNCOPE-415: SUCCESS: Integrated in Syncope-trunk #448 (See [https://builds.apache.org/job/Syncope-trunk/448/]) [SYNCOPE-415] Applying provided patch (ilgrosso: rev 1524644) * /syncope/trunk * /syncope/trunk/core/src/main/java/org/apache/syncope/core/persistence/validation/entity/EntityValidationListener.java Reduce log level of bean validation errors -- Key: SYNCOPE-415 URL: https://issues.apache.org/jira/browse/SYNCOPE-415 Project: Syncope Issue Type: Improvement Components: core Affects Versions: 1.1.3, 1.2.0 Reporter: Guido Wimmel Assignee: Francesco Chicchiriccò Priority: Minor Fix For: 1.1.4, 1.2.0 Attachments: syncopeBeanValidationLogLevel_1_1_X.patch, syncopeBeanValidationLogLevel_trunk.patch Bean validation errors should not be logged with log level ERROR, as they can be part of normal system behaviour (e.g. a user registers herself or is registered by an admin and accidentally or unknowingly enters invalid data and then gets an error message on the UI). See the discussion on the dev mailing list [1]. [1] http://syncope-dev.1063484.n5.nabble.com/EntityValidationInterceptor-log-level-of-bean-validation-errors-td5714156.html -- 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-150) Rich client library
[ https://issues.apache.org/jira/browse/SYNCOPE-150?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13771860#comment-13771860 ] Hudson commented on SYNCOPE-150: SUCCESS: Integrated in Syncope-trunk #449 (See [https://builds.apache.org/job/Syncope-trunk/449/]) [SYNCOPE-150] SyncopeClient and SyncopeClientFactoryBean now available and used both for core IT and console (ilgrosso: rev 1524710) * /syncope/trunk/client/pom.xml * /syncope/trunk/client/src/main/java/org/apache/syncope/client/SyncopeClient.java * /syncope/trunk/client/src/main/java/org/apache/syncope/client/SyncopeClientFactoryBean.java * /syncope/trunk/client/src/main/java/org/apache/syncope/client/rest/RestClientExceptionMapper.java * /syncope/trunk/client/src/main/java/org/apache/syncope/client/rest/RestClientFactoryBean.java * /syncope/trunk/common/pom.xml * /syncope/trunk/common/src/main/java/org/apache/syncope/common/to/MappingTO.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/validation/SyncopeClientCompositeErrorException.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/validation/SyncopeClientCompositeException.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/SyncopeSession.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/AbstractSchedTaskModalPage.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/ApprovalModalPage.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/Configuration.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/ConfigurationModalPage.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/ConnectorModalPage.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/DerivedSchemaModalPage.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/Login.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/NotificationModalPage.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/ReportModalPage.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/Reports.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/SchemaModalPage.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/TaskModalPage.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/Todo.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/VirtualSchemaModalPage.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/panels/NotificationTasks.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/panels/PoliciesPanel.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/panels/PropagationTasks.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/panels/RoleSearchResultPanel.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/panels/RoleSummaryPanel.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/panels/SchedTasks.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/panels/SyncTasks.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/panels/UserSearchResultPanel.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/rest/ConnectorRestClient.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/rest/ReportRestClient.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/rest/ResourceRestClient.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/rest/SchemaRestClient.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/rest/TaskRestClient.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/rest/UserRestClient.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/rest/WorkflowRestClient.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/wicket/markup/html/tree/TreeActionLinkPanel.java * /syncope/trunk/console/src/main/resources/applicationContext.xml * /syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/controller/ConnectorController.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/controller/LoggerController.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/controller/ReportController.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/controller/ResourceController.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/controller/SchemaController.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/controller/TaskController.java *
[jira] [Commented] (SYNCOPE-416) AttributableSearchDAOImpl / Avoid query construction with string concatenation
[
https://issues.apache.org/jira/browse/SYNCOPE-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13771862#comment-13771862
]
Hudson commented on SYNCOPE-416:
SUCCESS: Integrated in Syncope-1_1_X #108 (See
[https://builds.apache.org/job/Syncope-1_1_X/108/])
[SYNCOPE-416] Suggestion applied (ilgrosso: rev 1524713)
*
/syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/persistence/dao/impl/AttributableSearchDAOImpl.java
AttributableSearchDAOImpl / Avoid query construction with string concatenation
--
Key: SYNCOPE-416
URL: https://issues.apache.org/jira/browse/SYNCOPE-416
Project: Syncope
Issue Type: Improvement
Components: core
Affects Versions: 1.1.3, 1.2.0
Reporter: Guido Wimmel
Assignee: Francesco Chicchiriccò
Priority: Minor
Fix For: 1.1.4, 1.2.0
Is there any reason why in
org.apache.syncope.core.persistence.impl.AttributableSearchDAOImpl:419
the like condition is appended by string concatenation?
query.append( LIKE ').append(cond.getExpression()).append(');
IMO this could open up a possible SQL injection vulnerability.
In AttributableSearchDAOImpl:387 a query parameter is used, as I would have
expected.
--
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-413) Clean activiti history for unused variables
[ https://issues.apache.org/jira/browse/SYNCOPE-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13771898#comment-13771898 ] Hudson commented on SYNCOPE-413: SUCCESS: Integrated in Syncope-1_1_X #109 (See [https://builds.apache.org/job/Syncope-1_1_X/109/]) SYNCOPE-413 fixed on 1_0_X (fmartelli: rev 1524733) * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/workflow/user/activiti/ActivitiUserWorkflowAdapter.java Clean activiti history for unused variables --- Key: SYNCOPE-413 URL: https://issues.apache.org/jira/browse/SYNCOPE-413 Project: Syncope Issue Type: Improvement Components: core Affects Versions: 1.1.3 Reporter: fabio martelli Assignee: fabio martelli Fix For: 1.1.4, 1.2.0 Currently activiti history store valued variables like userTO and syncopeUser. Since this varables are not useful for the system unset them after moving to the history. -- 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-416) AttributableSearchDAOImpl / Avoid query construction with string concatenation
[
https://issues.apache.org/jira/browse/SYNCOPE-416?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13771909#comment-13771909
]
Hudson commented on SYNCOPE-416:
SUCCESS: Integrated in Syncope-trunk #450 (See
[https://builds.apache.org/job/Syncope-trunk/450/])
[SYNCOPE-416] Merge from 1_1_X (ilgrosso: rev 1524714)
* /syncope/trunk
*
/syncope/trunk/core/src/main/java/org/apache/syncope/core/persistence/dao/impl/AttributableSearchDAOImpl.java
AttributableSearchDAOImpl / Avoid query construction with string concatenation
--
Key: SYNCOPE-416
URL: https://issues.apache.org/jira/browse/SYNCOPE-416
Project: Syncope
Issue Type: Improvement
Components: core
Affects Versions: 1.1.3, 1.2.0
Reporter: Guido Wimmel
Assignee: Francesco Chicchiriccò
Priority: Minor
Fix For: 1.1.4, 1.2.0
Is there any reason why in
org.apache.syncope.core.persistence.impl.AttributableSearchDAOImpl:419
the like condition is appended by string concatenation?
query.append( LIKE ').append(cond.getExpression()).append(');
IMO this could open up a possible SQL injection vulnerability.
In AttributableSearchDAOImpl:387 a query parameter is used, as I would have
expected.
--
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-413) Clean activiti history for unused variables
[ https://issues.apache.org/jira/browse/SYNCOPE-413?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13771908#comment-13771908 ] Hudson commented on SYNCOPE-413: SUCCESS: Integrated in Syncope-trunk #450 (See [https://builds.apache.org/job/Syncope-trunk/450/]) SYNCOPE-413 fixed on trunk (fmartelli: rev 1524734) * /syncope/trunk * /syncope/trunk/core/src/main/java/org/apache/syncope/core/workflow/user/activiti/ActivitiUserWorkflowAdapter.java Clean activiti history for unused variables --- Key: SYNCOPE-413 URL: https://issues.apache.org/jira/browse/SYNCOPE-413 Project: Syncope Issue Type: Improvement Components: core Affects Versions: 1.1.3 Reporter: fabio martelli Assignee: fabio martelli Fix For: 1.1.4, 1.2.0 Currently activiti history store valued variables like userTO and syncopeUser. Since this varables are not useful for the system unset them after moving to the history. -- 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-414) Cannot successfully deploy on Weblogic 12c (12.1.1)
[ https://issues.apache.org/jira/browse/SYNCOPE-414?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13770583#comment-13770583 ] Hudson commented on SYNCOPE-414: SUCCESS: Integrated in Syncope-trunk #444 (See [https://builds.apache.org/job/Syncope-trunk/444/]) [SYNCOPE-414] Minor adjustments (ilgrosso: rev 1524335) * /syncope/trunk/core/src/main/webapp/WEB-INF/web.xml * /syncope/trunk/core/src/main/webapp/WEB-INF/weblogic.xml Cannot successfully deploy on Weblogic 12c (12.1.1) --- Key: SYNCOPE-414 URL: https://issues.apache.org/jira/browse/SYNCOPE-414 Project: Syncope Issue Type: Bug Components: console, core Affects Versions: 1.2.0 Environment: Weblogic 12c (12.1.1) Reporter: Francesco Chicchiriccò Fix For: 1.2.0 Due to LOG4J2-344 and / or LOG4J2-359, deploy core or console on Weblogic is not working -- 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-246) Remove collection setters in transfer objects for JAXB marshalling
[ https://issues.apache.org/jira/browse/SYNCOPE-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13770627#comment-13770627 ] Hudson commented on SYNCOPE-246: SUCCESS: Integrated in Syncope-trunk #445 (See [https://builds.apache.org/job/Syncope-trunk/445/]) [SYNCOPE-246] Residual invocation that cannot be checked at compile time due to non-generic nature of the collection (ListObject) (ilgrosso: rev 1524341) * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/ConnectorModalPage.java Remove collection setters in transfer objects for JAXB marshalling -- Key: SYNCOPE-246 URL: https://issues.apache.org/jira/browse/SYNCOPE-246 Project: Syncope Issue Type: Sub-task Components: core Affects Versions: 1.1.0 Environment: CXF branch Reporter: Andrei Shakirin Assignee: Francesco Chicchiriccò Fix For: 1.2.0 XML payload will be marshaled/unmarshaled using JAXB by migration to CXF Rest frontend. JAXB works with collections in a little bit different way as Spring Rest marshaling. JAXB uses only getter for the list (assumes that list is initialized due object creation) and adds elements into the list obtained by getter by unmarshaling. It doesn't need setter at all. The problem is that actual implementation of transfer objects doesn't work with JAXB. If TO provide setter for collection, JAXB gets the list, adds the elements and additionally calls setter for this list. As far as setter logic cleans the TO collection, the result collection is always empty. Solution is remove setters for collections in TOs by migration on CXF Rest. I find it also better from security and encapsulation aspects. Regards, Andrei. -- 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-412) Audit tables are reset after restart
[ https://issues.apache.org/jira/browse/SYNCOPE-412?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13770748#comment-13770748 ] Hudson commented on SYNCOPE-412: SUCCESS: Integrated in Syncope-1_1_X #106 (See [https://builds.apache.org/job/Syncope-1_1_X/106/]) [SYNCOPE-412] Backporting to 1_1_X part of audit SQL management from SYNCOPE-405 (ilgrosso: rev 1524383) * /syncope/branches/1_1_X/core/pom.xml * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/audit/JNDIFallbackConnectionSource.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/persistence/dao/impl/AbstractContentDealer.java * /syncope/branches/1_1_X/core/src/main/resources/audit.xml * /syncope/branches/1_1_X/core/src/main/resources/logback/h2.sql * /syncope/branches/1_1_X/core/src/main/resources/logback/hsqldb.sql * /syncope/branches/1_1_X/core/src/main/resources/logback/mysql.sql * /syncope/branches/1_1_X/core/src/main/resources/logback/oracle.sql * /syncope/branches/1_1_X/core/src/main/resources/logback/postgresql.sql * /syncope/branches/1_1_X/core/src/main/resources/logback/sqlserver.sql * /syncope/branches/1_1_X/core/src/main/resources/syncopeContext.xml Audit tables are reset after restart Key: SYNCOPE-412 URL: https://issues.apache.org/jira/browse/SYNCOPE-412 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.1.3 Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Labels: audit Fix For: 1.1.4 Due to the way how logback audit SQL init scripts are architected, audit tables are dropped and re-created at every Syncope restart. -- 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-407) Add claim for user requests and trace user request history into SyncopeUser bean
[ https://issues.apache.org/jira/browse/SYNCOPE-407?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13770967#comment-13770967 ] Hudson commented on SYNCOPE-407: SUCCESS: Integrated in Syncope-trunk #447 (See [https://builds.apache.org/job/Syncope-trunk/447/]) SYNCOPE-407 fixed (fmartelli: rev 1524459) * /syncope/trunk/common/src/main/java/org/apache/syncope/common/services/UserRequestService.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/to/UserRequestTO.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/types/AuditElements.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/types/SyncopeClientExceptionType.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/Todo.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/rest/ConnectorRestClient.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/rest/UserRequestRestClient.java * /syncope/trunk/console/src/main/resources/org/apache/syncope/console/pages/Todo.html * /syncope/trunk/console/src/main/resources/org/apache/syncope/console/pages/Todo.properties * /syncope/trunk/console/src/main/resources/org/apache/syncope/console/pages/Todo_it.properties * /syncope/trunk/console/src/main/resources/org/apache/syncope/console/pages/Todo_pt_BR.properties * /syncope/trunk/core/src/main/java/org/apache/syncope/core/persistence/beans/UserRequest.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/persistence/dao/UserRequestDAO.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/persistence/dao/impl/UserRequestDAOImpl.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/controller/UnauthorizedException.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/controller/UserRequestController.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/services/UserRequestServiceImpl.java * /syncope/trunk/core/src/main/resources/content.xml * /syncope/trunk/core/src/main/resources/quartz/tables_sqlServer.sql * /syncope/trunk/core/src/test/java/org/apache/syncope/core/persistence/dao/EntitlementTest.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/UserRequestTestITCase.java * /syncope/trunk/core/src/test/resources/content.xml Add claim for user requests and trace user request history into SyncopeUser bean Key: SYNCOPE-407 URL: https://issues.apache.org/jira/browse/SYNCOPE-407 Project: Syncope Issue Type: Improvement Components: client, console, core Affects Versions: 1.1.3, 1.2.0 Reporter: fabio martelli Assignee: fabio martelli Fix For: 1.2.0 Add claim for user requests and trace user request history into SyncopeUser bean -- 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-405) Replace logback with log4j 2
[ https://issues.apache.org/jira/browse/SYNCOPE-405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13769415#comment-13769415 ] Hudson commented on SYNCOPE-405: SUCCESS: Integrated in Syncope-trunk #440 (See [https://builds.apache.org/job/Syncope-trunk/440/]) [SYNCOPE-405] Replace completed, for audit and logging: currently on log4j 2.0-beta9-SNAPSHOT (ilgrosso: rev 1523969) * /syncope/trunk/archetype/src/main/resources/archetype-resources/console/pom.xml * /syncope/trunk/archetype/src/main/resources/archetype-resources/core/pom.xml * /syncope/trunk/archetype/src/main/resources/meta-pom.xml * /syncope/trunk/build-tools/pom.xml * /syncope/trunk/build-tools/src/main/webapp/WEB-INF/web.xml * /syncope/trunk/client/pom.xml * /syncope/trunk/client/src/main/java/org/apache/syncope/client/rest/RestClientExceptionMapper.java * /syncope/trunk/client/src/main/resources/META-INF * /syncope/trunk/client/src/main/resources/META-INF/cxf * /syncope/trunk/client/src/main/resources/META-INF/cxf/org.apache.cxf.Logger * /syncope/trunk/common/pom.xml * /syncope/trunk/common/src/main/java/org/apache/syncope/common/SyncopeConstants.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/to/LoggerTO.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/types/AuditLoggerName.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/types/LoggerLevel.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/types/LoggerType.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/types/SyncopeLoggerLevel.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/types/SyncopeLoggerType.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/util/CollectionWrapper.java * /syncope/trunk/console/pom.xml * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/Configuration.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/rest/LoggerRestClient.java * /syncope/trunk/console/src/main/resources/log4j2.xml * /syncope/trunk/console/src/main/resources/logback.xml * /syncope/trunk/core/pom.xml * /syncope/trunk/core/src/main/java/org/apache/syncope/core/audit/AuditConnectionFactory.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/audit/AuditManager.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/audit/JNDIFallbackConnectionSource.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/init/LoggerLoader.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/persistence/beans/SyncopeLogger.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/persistence/dao/LoggerDAO.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/persistence/dao/impl/AbstractContentDealer.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/persistence/dao/impl/LoggerDAOImpl.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/quartz/SpringBeanJobFactory.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/controller/LoggerController.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/services/LoggerServiceImpl.java * /syncope/trunk/core/src/main/resources/META-INF/cxf * /syncope/trunk/core/src/main/resources/META-INF/cxf/org.apache.cxf.Logger * /syncope/trunk/core/src/main/resources/audit * /syncope/trunk/core/src/main/resources/audit.xml * /syncope/trunk/core/src/main/resources/audit/audit.sql * /syncope/trunk/core/src/main/resources/audit/audit_mysql_innodb.sql * /syncope/trunk/core/src/main/resources/audit/audit_oracle.sql * /syncope/trunk/core/src/main/resources/audit/audit_sqlserver.sql * /syncope/trunk/core/src/main/resources/log4j2.xml * /syncope/trunk/core/src/main/resources/logback * /syncope/trunk/core/src/main/resources/logback.xml * /syncope/trunk/core/src/main/resources/persistence.properties * /syncope/trunk/core/src/main/resources/persistenceContext.xml * /syncope/trunk/core/src/main/resources/syncopeContext.xml * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/LoggerTestITCase.java * /syncope/trunk/core/src/test/resources/mysql/persistence.properties * /syncope/trunk/core/src/test/resources/oracle/persistence.properties * /syncope/trunk/core/src/test/resources/persistence.properties * /syncope/trunk/core/src/test/resources/persistenceTestEnv.xml * /syncope/trunk/core/src/test/resources/postgres/persistence.properties * /syncope/trunk/core/src/test/resources/sqlserver/persistence.properties * /syncope/trunk/legal_ext/LICENSE * /syncope/trunk/legal_ext/NOTICE * /syncope/trunk/pom.xml Replace logback with log4j 2 Key: SYNCOPE-405 URL: https://issues.apache.org/jira/browse/SYNCOPE-405 Project: Syncope Issue Type: Improvement Reporter: Francesco Chicchiriccò
[jira] [Commented] (SYNCOPE-15) Manage creator, lastmodifier and approvers information about each SyncopeUser bean
[ https://issues.apache.org/jira/browse/SYNCOPE-15?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13768415#comment-13768415 ] Hudson commented on SYNCOPE-15: --- SUCCESS: Integrated in Syncope-trunk #439 (See [https://builds.apache.org/job/Syncope-trunk/439/]) SYNCOPE-15 fixed (fmartelli: rev 1523644) * /syncope/trunk/common/src/main/java/org/apache/syncope/common/services/UserWorkflowService.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/controller/UserWorkflowController.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/services/UserWorkflowServiceImpl.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/workflow/WorkflowAdapter.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/workflow/role/NoOpRoleWorkflowAdapter.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/workflow/user/NoOpUserWorkflowAdapter.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/workflow/user/activiti/ActivitiUserWorkflowAdapter.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/UserTestITCase.java Manage creator, lastmodifier and approvers information about each SyncopeUser bean -- Key: SYNCOPE-15 URL: https://issues.apache.org/jira/browse/SYNCOPE-15 Project: Syncope Issue Type: Improvement Components: client, console, core Affects Versions: 1.0.0-incubating Reporter: fabio martelli Assignee: fabio martelli Fix For: 1.2.0 Add and populate/manage the following SyncopeUser bean attributes: 1. creator (who has created the user) 2. lastModifier (who has performed the last modification to the user profile) 3. approvers (every approver which approved some operation about the user) -- 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-409) Allow notifications with empty about field
[ https://issues.apache.org/jira/browse/SYNCOPE-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13747373#comment-13747373 ] Hudson commented on SYNCOPE-409: SUCCESS: Integrated in Syncope-1_1_X #101 (See [https://builds.apache.org/job/Syncope-1_1_X/101/]) Upgrading to Wicket 6.10.0 and adjusting Selenium tests for SYNCOPE-409 (ilgrosso: rev 1516377) * /syncope/branches/1_1_X/console/src/test/java/org/apache/syncope/console/ConfigurationTestITCase.java * /syncope/branches/1_1_X/pom.xml Allow notifications with empty about field -- Key: SYNCOPE-409 URL: https://issues.apache.org/jira/browse/SYNCOPE-409 Project: Syncope Issue Type: Improvement Components: console, core Affects Versions: 1.1.3 Reporter: Guido Wimmel Assignee: Francesco Chicchiriccò Priority: Minor Fix For: 1.1.4, 1.2.0 Attachments: syncopeNotificationsEmptyAbout.patch, syncopeNotificationsEmptyAbout.patch Currently, when one creates a new notification in Syncope, one is forced to enter a user search condition in the About tab that allows to restrict the notifications to specific users. IMO this is not always necessary - it should also be possible to leave the field empty such that the notification is sent for all users. Allowing the Notification.about field to be empty would also improve performance in this case, as an unnecessary search query to the database can be avoided. This is especially relevant for MySQL, as we observed full table scan behaviour for queries executed by AttributableSearchDAOImpl.matches() (called by NotificationManager) for even very simple search conditions. -- 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-411) Perform retries on failed notifications
[ https://issues.apache.org/jira/browse/SYNCOPE-411?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13742008#comment-13742008 ] Hudson commented on SYNCOPE-411: SUCCESS: Integrated in Syncope-1_1_X #99 (See [https://builds.apache.org/job/Syncope-1_1_X/99/]) [SYNCOPE-411] Applying provided patch + some minor tweaks + audit (ilgrosso: rev 1514600) * /syncope/branches/1_1_X/common/src/main/java/org/apache/syncope/common/types/AuditElements.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/notification/NotificationJob.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/notification/NotificationManager.java * /syncope/branches/1_1_X/core/src/main/resources/content.xml * /syncope/branches/1_1_X/core/src/test/java/org/apache/syncope/core/notification/NotificationTest.java * /syncope/branches/1_1_X/core/src/test/resources/content.xml Perform retries on failed notifications --- Key: SYNCOPE-411 URL: https://issues.apache.org/jira/browse/SYNCOPE-411 Project: Syncope Issue Type: Improvement Components: core Affects Versions: 1.1.3 Reporter: Guido Wimmel Assignee: Francesco Chicchiriccò Priority: Minor Fix For: 1.1.4, 1.2.0 Attachments: syncopeNotificationRetry.patch Currently, if an Email notification cannot be sent (e.g. because the SMTP server temporarily does not respond), the notification task is marked as NOT_SENT and as executed (class NotificationJob). It could be a useful improvement to extend Apache Syncope such that failed email notifications are retried a configurable number of times. -- 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-409) Allow notifications with empty about field
[ https://issues.apache.org/jira/browse/SYNCOPE-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13734749#comment-13734749 ] Hudson commented on SYNCOPE-409: SUCCESS: Integrated in Syncope-trunk #299 (See [https://builds.apache.org/job/Syncope-trunk/299/]) [SYNCOPE-409] Some changes needed for trunk (ilgrosso: rev 1512285) * /syncope/trunk/core/src/test/java/org/apache/syncope/core/notification/NotificationTest.java Allow notifications with empty about field -- Key: SYNCOPE-409 URL: https://issues.apache.org/jira/browse/SYNCOPE-409 Project: Syncope Issue Type: Improvement Components: console, core Affects Versions: 1.1.3 Reporter: Guido Wimmel Assignee: Francesco Chicchiriccò Priority: Minor Fix For: 1.1.4, 1.2.0 Attachments: syncopeNotificationsEmptyAbout.patch, syncopeNotificationsEmptyAbout.patch Currently, when one creates a new notification in Syncope, one is forced to enter a user search condition in the About tab that allows to restrict the notifications to specific users. IMO this is not always necessary - it should also be possible to leave the field empty such that the notification is sent for all users. Allowing the Notification.about field to be empty would also improve performance in this case, as an unnecessary search query to the database can be avoided. This is especially relevant for MySQL, as we observed full table scan behaviour for queries executed by AttributableSearchDAOImpl.matches() (called by NotificationManager) for even very simple search conditions. -- 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-409) Allow notifications with empty about field
[ https://issues.apache.org/jira/browse/SYNCOPE-409?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13734770#comment-13734770 ] Hudson commented on SYNCOPE-409: SUCCESS: Integrated in Syncope-1_1_X #97 (See [https://builds.apache.org/job/Syncope-1_1_X/97/]) [SYNCOPE-409] Latest patch applied (ilgrosso: rev 1512280) * /syncope/branches/1_1_X/console/src/main/java/org/apache/syncope/console/pages/NotificationModalPage.java * /syncope/branches/1_1_X/console/src/main/resources/org/apache/syncope/console/pages/NotificationModalPage.html * /syncope/branches/1_1_X/console/src/main/resources/org/apache/syncope/console/pages/NotificationModalPage.properties * /syncope/branches/1_1_X/console/src/main/resources/org/apache/syncope/console/pages/NotificationModalPage_it.properties * /syncope/branches/1_1_X/console/src/main/resources/org/apache/syncope/console/pages/NotificationModalPage_pt_BR.properties * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/notification/NotificationManager.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/persistence/beans/Notification.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/test/java/org/apache/syncope/core/notification/NotificationTest.java Allow notifications with empty about field -- Key: SYNCOPE-409 URL: https://issues.apache.org/jira/browse/SYNCOPE-409 Project: Syncope Issue Type: Improvement Components: console, core Affects Versions: 1.1.3 Reporter: Guido Wimmel Assignee: Francesco Chicchiriccò Priority: Minor Fix For: 1.1.4, 1.2.0 Attachments: syncopeNotificationsEmptyAbout.patch, syncopeNotificationsEmptyAbout.patch Currently, when one creates a new notification in Syncope, one is forced to enter a user search condition in the About tab that allows to restrict the notifications to specific users. IMO this is not always necessary - it should also be possible to leave the field empty such that the notification is sent for all users. Allowing the Notification.about field to be empty would also improve performance in this case, as an unnecessary search query to the database can be avoided. This is especially relevant for MySQL, as we observed full table scan behaviour for queries executed by AttributableSearchDAOImpl.matches() (called by NotificationManager) for even very simple search conditions. -- 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-410) Make username pattern configurable via account policy
[ https://issues.apache.org/jira/browse/SYNCOPE-410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13734995#comment-13734995 ] Hudson commented on SYNCOPE-410: SUCCESS: Integrated in Syncope-trunk #301 (See [https://builds.apache.org/job/Syncope-trunk/301/]) [SYNCOPE-410] Merge from 1_1_X (ilgrosso: rev 1512372) * /syncope/trunk * /syncope/trunk/common/src/main/java/org/apache/syncope/common/types/AccountPolicySpec.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/panels/PolicyBeanPanel.java * /syncope/trunk/console/src/main/resources/org/apache/syncope/console/pages/PolicyModalPage.properties * /syncope/trunk/console/src/main/resources/org/apache/syncope/console/pages/PolicyModalPage_it.properties * /syncope/trunk/console/src/main/resources/org/apache/syncope/console/pages/PolicyModalPage_pt_BR.properties * /syncope/trunk/core/src/main/java/org/apache/syncope/core/policy/AccountPolicyEnforcer.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/policy Make username pattern configurable via account policy - Key: SYNCOPE-410 URL: https://issues.apache.org/jira/browse/SYNCOPE-410 Project: Syncope Issue Type: Improvement Components: console, core Reporter: Guido Wimmel Assignee: Francesco Chicchiriccò Priority: Minor Fix For: 1.1.4, 1.2.0 Attachments: syncopeAccountPolicyPattern.patch Currently, the pattern for allowed usernames in Syncope is fixed to [a-zA-Z0-9-_@. ]+ (see AccountPolicyEnforcer). There are use cases for which this pattern does not fit (e.g. if one uses email addresses as usernames, e.g. the character '+' is also valid). I'd suggest making the username pattern configurable via the account policy. See also the corresponding discussion on the mailing list starting with [1]. [1] http://syncope-dev.1063484.n5.nabble.com/AccountPolicyEnforcer-allowed-characters-in-username-td5714080.html -- 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-410) Make username pattern configurable via account policy
[ https://issues.apache.org/jira/browse/SYNCOPE-410?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13735015#comment-13735015 ] Hudson commented on SYNCOPE-410: SUCCESS: Integrated in Syncope-1_1_X #98 (See [https://builds.apache.org/job/Syncope-1_1_X/98/]) [SYNCOPE-410] Applying provided patch (ilgrosso: rev 1512363) * /syncope/branches/1_1_X/common/src/main/java/org/apache/syncope/common/types/AccountPolicySpec.java * /syncope/branches/1_1_X/console/src/main/java/org/apache/syncope/console/pages/panels/PolicyBeanPanel.java * /syncope/branches/1_1_X/console/src/main/resources/org/apache/syncope/console/pages/PolicyModalPage.properties * /syncope/branches/1_1_X/console/src/main/resources/org/apache/syncope/console/pages/PolicyModalPage_it.properties * /syncope/branches/1_1_X/console/src/main/resources/org/apache/syncope/console/pages/PolicyModalPage_pt_BR.properties * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/policy/AccountPolicyEnforcer.java * /syncope/branches/1_1_X/core/src/test/java/org/apache/syncope/core/policy * /syncope/branches/1_1_X/core/src/test/java/org/apache/syncope/core/policy/AccountPolicyEnforcerTest.java Make username pattern configurable via account policy - Key: SYNCOPE-410 URL: https://issues.apache.org/jira/browse/SYNCOPE-410 Project: Syncope Issue Type: Improvement Components: console, core Reporter: Guido Wimmel Assignee: Francesco Chicchiriccò Priority: Minor Fix For: 1.1.4, 1.2.0 Attachments: syncopeAccountPolicyPattern.patch Currently, the pattern for allowed usernames in Syncope is fixed to [a-zA-Z0-9-_@. ]+ (see AccountPolicyEnforcer). There are use cases for which this pattern does not fit (e.g. if one uses email addresses as usernames, e.g. the character '+' is also valid). I'd suggest making the username pattern configurable via the account policy. See also the corresponding discussion on the mailing list starting with [1]. [1] http://syncope-dev.1063484.n5.nabble.com/AccountPolicyEnforcer-allowed-characters-in-username-td5714080.html -- 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-408) Add index on task.executed
[ https://issues.apache.org/jira/browse/SYNCOPE-408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13729349#comment-13729349 ] Hudson commented on SYNCOPE-408: SUCCESS: Integrated in Syncope-trunk #286 (See [https://builds.apache.org/job/Syncope-trunk/286/]) [SYNCOPE-408] Merge from 1_1_X (ilgrosso: rev 1510392) * /syncope/trunk * /syncope/trunk/core/src/main/resources/indexes.xml Add index on task.executed -- Key: SYNCOPE-408 URL: https://issues.apache.org/jira/browse/SYNCOPE-408 Project: Syncope Issue Type: Improvement Components: core Affects Versions: 1.1.3 Reporter: Guido Wimmel Assignee: Francesco Chicchiriccò Priority: Minor Fix For: 1.1.4, 1.2.0 Attachments: indexes.xml.patch In our Syncope installation (1.1.3 on Tomcat/MySQL) we observed long execution times (1s) for TaskDAO.findToExec(), which is called periodically from NotificationJob to determine which notifications should be sent. According to our analysis, this is due to the fact that TaskDAO.findToExec() performs a full scan on all entries of the task table with DTYPE=NotificationTask (which could be a large number as all executed tasks are kept), although only very few tasks are selected (those with executed=0). Creating an index on task.executed solved this problem; attached is a corresponding patch against the branch 1.1.X. -- 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-408) Add index on task.executed
[ https://issues.apache.org/jira/browse/SYNCOPE-408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13729351#comment-13729351 ] Hudson commented on SYNCOPE-408: SUCCESS: Integrated in Syncope-1_1_X #95 (See [https://builds.apache.org/job/Syncope-1_1_X/95/]) [SYNCOPE-408] Applying provided patch, successfully tested against all supported databases (ilgrosso: rev 1510390) * /syncope/branches/1_1_X/core/src/main/resources/indexes.xml Add index on task.executed -- Key: SYNCOPE-408 URL: https://issues.apache.org/jira/browse/SYNCOPE-408 Project: Syncope Issue Type: Improvement Components: core Affects Versions: 1.1.3 Reporter: Guido Wimmel Assignee: Francesco Chicchiriccò Priority: Minor Fix For: 1.1.4, 1.2.0 Attachments: indexes.xml.patch In our Syncope installation (1.1.3 on Tomcat/MySQL) we observed long execution times (1s) for TaskDAO.findToExec(), which is called periodically from NotificationJob to determine which notifications should be sent. According to our analysis, this is due to the fact that TaskDAO.findToExec() performs a full scan on all entries of the task table with DTYPE=NotificationTask (which could be a large number as all executed tasks are kept), although only very few tasks are selected (those with executed=0). Creating an index on task.executed solved this problem; attached is a corresponding patch against the branch 1.1.X. -- 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-402) Inconsistent status of user edit form after exception returned by bad propagation on primary resource
[ https://issues.apache.org/jira/browse/SYNCOPE-402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13712203#comment-13712203 ] Hudson commented on SYNCOPE-402: SUCCESS: Integrated in Syncope-1_1_X #84 (See [https://builds.apache.org/job/Syncope-1_1_X/84/]) SYNCOPE-402 Fix RoleController, add propagation status to assigned resource when primary resource failed. (mdisabatino: rev 1504397) * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/propagation/impl/DefaultPropagationHandler.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/rest/controller/RoleController.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/rest/controller/UserController.java Inconsistent status of user edit form after exception returned by bad propagation on primary resource - Key: SYNCOPE-402 URL: https://issues.apache.org/jira/browse/SYNCOPE-402 Project: Syncope Issue Type: Improvement Components: console, core Affects Versions: 1.1.2, 1.1.3 Reporter: Andrea Patricelli Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.1.4, 1.2.0 During creation (and save) of user to be propagated on a primary resource, if propagation fails (due to an error) it returns a propagation exception to console and to user edit form, which goes in an inconsistent status and stucks. A possible solution is to go directly, in case of propagation exception, to summary page reporting propagation status on resource(s); in particular propagation signaling icon of failure may be abled to show exception message caught from PropagationStatusTO. -- 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-402) Inconsistent status of user edit form after exception returned by bad propagation on primary resource
[ https://issues.apache.org/jira/browse/SYNCOPE-402?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13712244#comment-13712244 ] Hudson commented on SYNCOPE-402: SUCCESS: Integrated in Syncope-1_1_X #85 (See [https://builds.apache.org/job/Syncope-1_1_X/85/]) Syncope-402 Removed PropagationException from rest service mapper (mdisabatino: rev 1504416) * /syncope/branches/1_1_X/common/src/main/java/org/apache/syncope/common/types/SyncopeClientExceptionType.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/rest/utils/RestServiceExceptionMapper.java * /syncope/branches/1_1_X/core/src/main/webapp/syncopeClientError.jsp * /syncope/branches/1_1_X/core/src/test/java/org/apache/syncope/core/rest/UserTestITCase.java Inconsistent status of user edit form after exception returned by bad propagation on primary resource - Key: SYNCOPE-402 URL: https://issues.apache.org/jira/browse/SYNCOPE-402 Project: Syncope Issue Type: Improvement Components: console, core Affects Versions: 1.1.2, 1.1.3 Reporter: Andrea Patricelli Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.1.4, 1.2.0 During creation (and save) of user to be propagated on a primary resource, if propagation fails (due to an error) it returns a propagation exception to console and to user edit form, which goes in an inconsistent status and stucks. A possible solution is to go directly, in case of propagation exception, to summary page reporting propagation status on resource(s); in particular propagation signaling icon of failure may be abled to show exception message caught from PropagationStatusTO. -- 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-399) Role attribute mapping for user mapping item doesn't result in a multivalue property
[
https://issues.apache.org/jira/browse/SYNCOPE-399?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13700127#comment-13700127
]
Hudson commented on SYNCOPE-399:
Integrated in Syncope-trunk #244 (See
[https://builds.apache.org/job/Syncope-trunk/244/])
merged from branch 1_1_X for SYNCOPE-399 (Revision 1499764)
Result = SUCCESS
fmartelli :
Files :
* /syncope/trunk
*
/syncope/trunk/core/src/main/java/org/apache/syncope/core/util/MappingUtil.java
Role attribute mapping for user mapping item doesn't result in a multivalue
property
Key: SYNCOPE-399
URL: https://issues.apache.org/jira/browse/SYNCOPE-399
Project: Syncope
Issue Type: Bug
Components: core
Affects Versions: 1.1.2, 1.2.0
Reporter: fabio martelli
Assignee: fabio martelli
Fix For: 1.1.3, 1.2.0
Role attribute mapping for user mapping item doesn't result in a multivalue
property.
Take a look at MappingUtil.prepareAttribute() method: at the end of this
method the cardinality of the attribute to be propagated has been retrieved
by the following code
if (schema != null schema.isMultivalue()) {
result = new AbstractMap.SimpleEntryString, Attribute(null,
AttributeBuilder.build(extAttrName,
objValues));
} else {
result = new AbstractMap.SimpleEntryString, Attribute(null,
objValues.isEmpty()
? AttributeBuilder.build(extAttrName)
: AttributeBuilder.build(extAttrName,
objValues.iterator().next()));
}
In case of user mapping item related to a merbership or role attribute (non
multivalued) a single value will be propagated.
--
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-370) HTTP Status 404 adding a role to a user with IE8
[ https://issues.apache.org/jira/browse/SYNCOPE-370?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13697635#comment-13697635 ] Hudson commented on SYNCOPE-370: Integrated in Syncope-1_1_X #74 (See [https://builds.apache.org/job/Syncope-1_1_X/74/]) [SYNCOPE-370] Upgrade to Wicket 6.9.0 (that contains WICKET-5071) (Revision 1498805) Result = SUCCESS ilgrosso : Files : * /syncope/branches/1_1_X/pom.xml HTTP Status 404 adding a role to a user with IE8 - Key: SYNCOPE-370 URL: https://issues.apache.org/jira/browse/SYNCOPE-370 Project: Syncope Issue Type: Bug Components: console Affects Versions: 1.1.1 Environment: IE8 Reporter: fabio martelli Assignee: Francesco Chicchiriccò Priority: Minor Fix For: 1.1.3, 1.2.0 Trying to add a role to a user with IE8 a HTTP Status 404 /syncope-console/wicket/bookmarkable/page is returned -- 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-398) secretKey does not get resolved during archetype:generate
[
https://issues.apache.org/jira/browse/SYNCOPE-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13696850#comment-13696850
]
Hudson commented on SYNCOPE-398:
Integrated in Syncope-1_1_X #73 (See
[https://builds.apache.org/job/Syncope-1_1_X/73/])
[SYNCOPE-398] Adding provided secretKey to generated root pom.xml, as
property (Revision 1498451)
Result = SUCCESS
ilgrosso :
Files :
* /syncope/branches/1_1_X/archetype/src/main/resources/meta-pom.xml
secretKey does not get resolved during archetype:generate
-
Key: SYNCOPE-398
URL: https://issues.apache.org/jira/browse/SYNCOPE-398
Project: Syncope
Issue Type: Bug
Components: archetype
Affects Versions: 1.1.2
Reporter: Francesco Chicchiriccò
Assignee: Francesco Chicchiriccò
Fix For: 1.1.3, 1.2.0
How to replicate: just generate new project [1] and provide any value for
secretKey: you will end up with the following content in
core/src/main/resources/security.properties:
adminUser=admin
adminPassword=5baa61e4c9b93f3f0682250b6cf8331b7ee68fd8
adminPasswordAlgorithm=SHA1
secretKey=${secretKey}
which shows an unresolved ${secretKey}.
--
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-398) secretKey does not get resolved during archetype:generate
[
https://issues.apache.org/jira/browse/SYNCOPE-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13696852#comment-13696852
]
Hudson commented on SYNCOPE-398:
Integrated in Syncope-trunk #242 (See
[https://builds.apache.org/job/Syncope-trunk/242/])
[SYNCOPE-398] Merge from 1_1_X (Revision 1498453)
Result = SUCCESS
ilgrosso :
Files :
* /syncope/trunk
* /syncope/trunk/archetype/src/main/resources/meta-pom.xml
secretKey does not get resolved during archetype:generate
-
Key: SYNCOPE-398
URL: https://issues.apache.org/jira/browse/SYNCOPE-398
Project: Syncope
Issue Type: Bug
Components: archetype
Affects Versions: 1.1.2
Reporter: Francesco Chicchiriccò
Assignee: Francesco Chicchiriccò
Fix For: 1.1.3, 1.2.0
How to replicate: just generate new project [1] and provide any value for
secretKey: you will end up with the following content in
core/src/main/resources/security.properties:
adminUser=admin
adminPassword=5baa61e4c9b93f3f0682250b6cf8331b7ee68fd8
adminPasswordAlgorithm=SHA1
secretKey=${secretKey}
which shows an unresolved ${secretKey}.
--
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-397) Double update propagation with virtual attributes on already associated resource when changing password and adding new resource
[ https://issues.apache.org/jira/browse/SYNCOPE-397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13694672#comment-13694672 ] Hudson commented on SYNCOPE-397: Integrated in Syncope-trunk #240 (See [https://builds.apache.org/job/Syncope-trunk/240/]) Fixes SYNCOPE-397 (Revision 1497312) Result = SUCCESS fmartelli : Files : * /syncope/trunk * /syncope/trunk/console/src/test/java/org/apache/syncope/console/UserTestITCase.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/propagation/impl/LDAPMembershipPropagationActions.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/controller/UserController.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/UserTestITCase.java Double update propagation with virtual attributes on already associated resource when changing password and adding new resource --- Key: SYNCOPE-397 URL: https://issues.apache.org/jira/browse/SYNCOPE-397 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.1.2 Reporter: Andrea Patricelli Fix For: 1.1.3, 1.2.0 Attachments: SYNCOPE-397.patch steps (run Syncope with -Pdev profile): 1. modify resource-csv mapping external attribute mail with virtual attribute virtualdata (assign BOTH purpose to the attribute, it may also work with SYNCHRONIZATION). 2. create a new user with all required (for csv) fields set to value (username, surname, mail, type, ecc), in particular add derived attributes csvuserid and cn and virtual attribute virtualdata 3. add to user resource-csv as resource, save and open it in edit mode. 4. add new resource to user, ws-target-resource-2, edit virtual attribute virtualdata. 5. edit password and check the checkbox to change password also on Syncope (don't check all resouces, csv must not be checked), checkbox for ws-target-resource-2 is already set. Save user It will be noticed a double propagation of user on both resources due to method fillVirtual() in PropagationManager.java -- 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-397) Double update propagation with virtual attributes on already associated resource when changing password and adding new resource
[ https://issues.apache.org/jira/browse/SYNCOPE-397?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13694678#comment-13694678 ] Hudson commented on SYNCOPE-397: Integrated in Syncope-1_1_X #71 (See [https://builds.apache.org/job/Syncope-1_1_X/71/]) SYNCOPE-397 fixed on the branch 1.1.X. Thank you Andrea for your contribution (Revision 1497304) Result = SUCCESS fmartelli : Files : * /syncope/branches/1_1_X/console/src/test/java/org/apache/syncope/console/UserTestITCase.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/propagation/impl/LDAPMembershipPropagationActions.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/rest/controller/UserController.java * /syncope/branches/1_1_X/core/src/test/java/org/apache/syncope/core/rest/UserTestITCase.java Double update propagation with virtual attributes on already associated resource when changing password and adding new resource --- Key: SYNCOPE-397 URL: https://issues.apache.org/jira/browse/SYNCOPE-397 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.1.2 Reporter: Andrea Patricelli Fix For: 1.1.3, 1.2.0 Attachments: SYNCOPE-397.patch steps (run Syncope with -Pdev profile): 1. modify resource-csv mapping external attribute mail with virtual attribute virtualdata (assign BOTH purpose to the attribute, it may also work with SYNCHRONIZATION). 2. create a new user with all required (for csv) fields set to value (username, surname, mail, type, ecc), in particular add derived attributes csvuserid and cn and virtual attribute virtualdata 3. add to user resource-csv as resource, save and open it in edit mode. 4. add new resource to user, ws-target-resource-2, edit virtual attribute virtualdata. 5. edit password and check the checkbox to change password also on Syncope (don't check all resouces, csv must not be checked), checkbox for ws-target-resource-2 is already set. Save user It will be noticed a double propagation of user on both resources due to method fillVirtual() in PropagationManager.java -- 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-394) Scheduled tasks are execute without transaction support
[ https://issues.apache.org/jira/browse/SYNCOPE-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13681275#comment-13681275 ] Hudson commented on SYNCOPE-394: Integrated in Syncope-1_1_X #67 (See [https://builds.apache.org/job/Syncope-1_1_X/67/]) [SYNCOPE-394] Adding new AbstractTransactionalTaskJob class for jobs needing to execute in transaction (Revision 1492210) Result = SUCCESS ilgrosso : Files : * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/init/ImplementationClassNamesLoader.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/init/JobInstanceLoader.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/quartz/AbstractTaskJob.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/quartz/AbstractTransactionalTaskJob.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/quartz/SampleJob.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/quartz/TaskJob.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/rest/controller/TaskController.java Scheduled tasks are execute without transaction support --- Key: SYNCOPE-394 URL: https://issues.apache.org/jira/browse/SYNCOPE-394 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.1.2 Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Fix For: 1.1.3, 1.2.0 Any class extending AbstractTaskJob cannot operate with transaction support because there is no method annotated as @Transactional -- 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-394) Scheduled tasks are execute without transaction support
[ https://issues.apache.org/jira/browse/SYNCOPE-394?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13681326#comment-13681326 ] Hudson commented on SYNCOPE-394: Integrated in Syncope-trunk #237 (See [https://builds.apache.org/job/Syncope-trunk/237/]) [SYNCOPE-394] Merge from 1_1_X (Revision 1492217) Result = SUCCESS ilgrosso : Files : * /syncope/trunk/core/src/main/java/org/apache/syncope/core/init/ImplementationClassNamesLoader.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/init/JobInstanceLoader.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/quartz/AbstractTaskJob.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/quartz/AbstractTransactionalTaskJob.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/quartz/SampleJob.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/quartz/TaskJob.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/controller/TaskController.java Scheduled tasks are execute without transaction support --- Key: SYNCOPE-394 URL: https://issues.apache.org/jira/browse/SYNCOPE-394 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.1.2 Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Fix For: 1.1.3, 1.2.0 Any class extending AbstractTaskJob cannot operate with transaction support because there is no method annotated as @Transactional -- 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-385) NPE when reading user assigned to resource with no mapping
[ https://issues.apache.org/jira/browse/SYNCOPE-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13672871#comment-13672871 ] Hudson commented on SYNCOPE-385: Integrated in Syncope-1_1_X #55 (See [https://builds.apache.org/job/Syncope-1_1_X/55/]) [SYNCOPE-385] Checking null before further processing (Revision 1488862) Result = SUCCESS ilgrosso : Files : * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/rest/controller/ResourceController.java NPE when reading user assigned to resource with no mapping -- Key: SYNCOPE-385 URL: https://issues.apache.org/jira/browse/SYNCOPE-385 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.1.1 Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Fix For: 1.1.2, 1.2.0 1. create a resource without any (user, role) mapping 2. create a user with that resource associated 3. enable DEBUG logging on core 4. get NPE (with HTTP 500) on logs due to null account id mapping item -- 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-385) NPE when reading user assigned to resource with no mapping
[ https://issues.apache.org/jira/browse/SYNCOPE-385?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13672872#comment-13672872 ] Hudson commented on SYNCOPE-385: Integrated in Syncope-trunk #229 (See [https://builds.apache.org/job/Syncope-trunk/229/]) [SYNCOPE-385] Checking null before further processing (Revision 1488863) Result = SUCCESS ilgrosso : Files : * /syncope/trunk * /syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/controller/ResourceController.java NPE when reading user assigned to resource with no mapping -- Key: SYNCOPE-385 URL: https://issues.apache.org/jira/browse/SYNCOPE-385 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.1.1 Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Fix For: 1.1.2, 1.2.0 1. create a resource without any (user, role) mapping 2. create a user with that resource associated 3. enable DEBUG logging on core 4. get NPE (with HTTP 500) on logs due to null account id mapping item -- 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-386) Database sync (no full reconciliation) fails with Unsupported object class
[ https://issues.apache.org/jira/browse/SYNCOPE-386?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13672962#comment-13672962 ] Hudson commented on SYNCOPE-386: Integrated in Syncope-1_1_X #56 (See [https://builds.apache.org/job/Syncope-1_1_X/56/]) [SYNCOPE-386] Checking mapping of the given kind (user, role) before attempting to get latest sync token (Revision 1488907) Result = SUCCESS ilgrosso : Files : * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/sync/impl/SyncJob.java Database sync (no full reconciliation) fails with Unsupported object class Key: SYNCOPE-386 URL: https://issues.apache.org/jira/browse/SYNCOPE-386 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.1.1 Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Fix For: 1.1.2, 1.2.0 When attempting an actual synchronization (not a full reconciliation) against an external database, an error is returned from the underlying connector about the fact that the only ObjectClass supported is ACCOUNT. -- 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-381) Adding and saving roles with resources during save
[ https://issues.apache.org/jira/browse/SYNCOPE-381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13671644#comment-13671644 ] Hudson commented on SYNCOPE-381: Integrated in Syncope-trunk #228 (See [https://builds.apache.org/job/Syncope-trunk/228/]) [SYNCOPE-381] bug introduced from builder (Revision 1488291) Result = SUCCESS massi : Files : * /syncope/trunk * /syncope/trunk/console/src/main/java/org/apache/syncope/console/SyncopeSession.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/ResultStatusModalPage.java Adding and saving roles with resources during save -- Key: SYNCOPE-381 URL: https://issues.apache.org/jira/browse/SYNCOPE-381 Project: Syncope Issue Type: Bug Components: console Affects Versions: 1.1.1 Environment: Glassfish Reporter: Nik Tetteh-Lartey Assignee: Massimiliano Perrone Priority: Minor Fix For: 1.1.2, 1.2.0 add a new role which is connected to an ldap by a resource connector. Then after pressing save the role popup window appears hung, so press save several times and eventually use the x to cancel. You end up with many duplicate roles. If you delete all the duplicates until you end with one role and then try and create a new role we get the following exception thrown: 2013-05-31 11:13:07.514+0200 (21) StandardWrapperValve[syncope-core-rest]: PWC1406: Servlet.service() for servlet syncope-core-rest threw exception org.apache.syncope.core.persistence.dao.NotFoundException: Role 101 at org.apache.syncope.core.rest.data.RoleDataBinder.getRoleFromId(RoleDataBinder.java:73) at org.apache.syncope.core.rest.data.RoleDataBinder$$FastClassByCGLIB$$75f19568.invoke(generated) at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204) at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:698) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.springframework.transaction.interceptor.TransactionInterceptor$1.proceedWithInvocation(TransactionInterceptor.java:96) at org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:260) at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:94) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:631) at org.apache.syncope.core.rest.data.RoleDataBinder$$EnhancerByCGLIB$$bff86965.getRoleFromId(generated) at org.apache.syncope.core.rest.controller.RoleController.read(RoleController.java:109) at org.apache.syncope.core.rest.controller.RoleController$$FastClassByCGLIB$$77c6d55e.invoke(generated) at org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204) at org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:698) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:150) at org.springframework.transaction.interceptor.TransactionInterceptor$1.proceedWithInvocation(TransactionInterceptor.java:96) at org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:260) at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:94) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.security.access.intercept.aopalliance.MethodSecurityInterceptor.invoke(MethodSecurityInterceptor.java:64) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:172) at org.springframework.aop.framework.CglibAopProxy$DynamicAdvisedInterceptor.intercept(CglibAopProxy.java:631) at org.apache.syncope.core.rest.controller.RoleController$$EnhancerByCGLIB$$1acaf620.read(generated) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at
[jira] [Commented] (SYNCOPE-383) Failure assigning resource to an existing user
[ https://issues.apache.org/jira/browse/SYNCOPE-383?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13671645#comment-13671645 ] Hudson commented on SYNCOPE-383: Integrated in Syncope-trunk #228 (See [https://builds.apache.org/job/Syncope-trunk/228/]) [SYNCOPE-383] merged from 1_1_X (Revision 1488260) Result = SUCCESS fmartelli : Files : * /syncope/trunk * /syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/data/UserDataBinder.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/UserTestITCase.java Failure assigning resource to an existing user -- Key: SYNCOPE-383 URL: https://issues.apache.org/jira/browse/SYNCOPE-383 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.1.1 Environment: Development Reporter: fabio martelli Assignee: fabio martelli Fix For: 1.1.2, 1.2.0 Resource assignment to an existing user fails if the resource require password but a password change is not forced on syncope itself. Steps: 1. create a new user; 2. update user by assigning resource (the resource must require password) and specifying a new pwd 3. ... error returned ... -- 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-384) Issues with CXF and Glassfish
[ https://issues.apache.org/jira/browse/SYNCOPE-384?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13671646#comment-13671646 ] Hudson commented on SYNCOPE-384: Integrated in Syncope-trunk #228 (See [https://builds.apache.org/job/Syncope-trunk/228/]) [SYNCOPE-384] glassfish-web.xml file to set the class loader delegation to false (Revision 1488225) Result = SUCCESS massi : Files : * /syncope/trunk/console/src/main/webapp/WEB-INF/glassfish-web.xml Issues with CXF and Glassfish - Key: SYNCOPE-384 URL: https://issues.apache.org/jira/browse/SYNCOPE-384 Project: Syncope Issue Type: Bug Affects Versions: 1.1.1 Environment: Glassfish Reporter: Francesco Chicchiriccò Assignee: Massimiliano Perrone Fix For: 1.1.2, 1.2.0 As reported in ML [1] there are currently problems running CXF services in Glassfish. [1] http://syncope-dev.1063484.n5.nabble.com/CXF-problem-deploying-Syncope-in-Glasshfish-tt5713799.html -- 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-376) Console webapp does not start on Glassfish
[ https://issues.apache.org/jira/browse/SYNCOPE-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13670347#comment-13670347 ] Hudson commented on SYNCOPE-376: Integrated in Syncope-trunk #227 (See [https://builds.apache.org/job/Syncope-trunk/227/]) [SYNCOPE-376] Merge from 1_1_X (Revision 1487838) Result = SUCCESS ilgrosso : Files : * /syncope/trunk * /syncope/trunk/console/src/main/resources/applicationContext.xml Console webapp does not start on Glassfish -- Key: SYNCOPE-376 URL: https://issues.apache.org/jira/browse/SYNCOPE-376 Project: Syncope Issue Type: Bug Components: console Affects Versions: 1.1.1 Environment: Glassfish 3.1.2 Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Fix For: 1.1.2, 1.2.0 As reported in [1], the admin console webapp does not start on Glassfish, with exception: java.lang.IllegalArgumentException: PWC2788: setAttribute: Non-serializable attribute with name restTemplate [1] http://syncope-user.1051894.n5.nabble.com/help-needed-please-to-build-1-1-2-SNAPSHOT-or-1-2-0-SNAPSHOT-project-tp5707061p5707079.html -- 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-376) Console webapp does not start on Glassfish
[ https://issues.apache.org/jira/browse/SYNCOPE-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13670367#comment-13670367 ] Hudson commented on SYNCOPE-376: Integrated in Syncope-1_1_X #53 (See [https://builds.apache.org/job/Syncope-1_1_X/53/]) [SYNCOPE-376] Changing RestTemplate's spring scope to 'prototype' (Revision 1487837) Result = SUCCESS ilgrosso : Files : * /syncope/branches/1_1_X/console/src/main/resources * /syncope/branches/1_1_X/console/src/main/resources/applicationContext.xml Console webapp does not start on Glassfish -- Key: SYNCOPE-376 URL: https://issues.apache.org/jira/browse/SYNCOPE-376 Project: Syncope Issue Type: Bug Components: console Affects Versions: 1.1.1 Environment: Glassfish 3.1.2 Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Fix For: 1.1.2, 1.2.0 As reported in [1], the admin console webapp does not start on Glassfish, with exception: java.lang.IllegalArgumentException: PWC2788: setAttribute: Non-serializable attribute with name restTemplate [1] http://syncope-user.1051894.n5.nabble.com/help-needed-please-to-build-1-1-2-SNAPSHOT-or-1-2-0-SNAPSHOT-project-tp5707061p5707079.html -- 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-375) QUARTZ tables are not written into an innodb mysql DB for an mvn generated and created project
[ https://issues.apache.org/jira/browse/SYNCOPE-375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13669061#comment-13669061 ] Hudson commented on SYNCOPE-375: Integrated in Syncope-1_1_X #51 (See [https://builds.apache.org/job/Syncope-1_1_X/51/]) [SYNCOPE-375] Patch applied (changing 'TYPE=InnoDB' into 'ENGINE=InnoDB') (Revision 1487333) Result = SUCCESS ilgrosso : Files : * /syncope/branches/1_1_X/core/src/main/resources/quartz/tables_mysql_innodb.sql QUARTZ tables are not written into an innodb mysql DB for an mvn generated and created project -- Key: SYNCOPE-375 URL: https://issues.apache.org/jira/browse/SYNCOPE-375 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.1.1 Environment: linux fedora 17 Fedora release 17 (Beefy Miracle) and Mac OSX Mountain lion Reporter: Nik Tetteh-Lartey Assignee: Francesco Chicchiriccò Fix For: 1.1.2, 1.2.0 Attachments: tables_mysql_innodb.sql building a snapshot 1.1.2 project (as per the wiki) and deploying the war file on a glassfish container using a mysql DB as persistant storage (re: wiki) results in a target DB being built without any of the QUARTZ tables used by syncope idm. WORK AROUND: 1. drop and create syncope db again (or just make empty) with current MySQL database 2. download attached file, save it under core/src/main/resources/quartz/ (create required path) 3. rebuild and redeploy 4. verify Quartz tables are now created as follows: bash-4.1# mysql -uroot -pwelcome syncope -A : mysql show tables like 'QRTZ%'; +---+ | Tables_in_syncope (QRTZ%) | +---+ | QRTZ_BLOB_TRIGGERS| | QRTZ_CALENDARS| | QRTZ_CRON_TRIGGERS| | QRTZ_FIRED_TRIGGERS | | QRTZ_JOB_DETAILS | | QRTZ_LOCKS| | QRTZ_PAUSED_TRIGGER_GRPS | | QRTZ_SCHEDULER_STATE | | QRTZ_SIMPLE_TRIGGERS | | QRTZ_SIMPROP_TRIGGERS | | QRTZ_TRIGGERS | +---+ 11 rows in set (0.00 sec) mysql -- 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-375) QUARTZ tables are not written into an innodb mysql DB for an mvn generated and created project
[ https://issues.apache.org/jira/browse/SYNCOPE-375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13669060#comment-13669060 ] Hudson commented on SYNCOPE-375: Integrated in Syncope-trunk #225 (See [https://builds.apache.org/job/Syncope-trunk/225/]) [SYNCOPE-375] Merge from 1_1_X (Revision 1487334) Result = SUCCESS ilgrosso : Files : * /syncope/trunk * /syncope/trunk/core/src/main/resources/quartz/tables_mysql_innodb.sql QUARTZ tables are not written into an innodb mysql DB for an mvn generated and created project -- Key: SYNCOPE-375 URL: https://issues.apache.org/jira/browse/SYNCOPE-375 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.1.1 Environment: linux fedora 17 Fedora release 17 (Beefy Miracle) and Mac OSX Mountain lion Reporter: Nik Tetteh-Lartey Assignee: Francesco Chicchiriccò Fix For: 1.1.2, 1.2.0 Attachments: tables_mysql_innodb.sql building a snapshot 1.1.2 project (as per the wiki) and deploying the war file on a glassfish container using a mysql DB as persistant storage (re: wiki) results in a target DB being built without any of the QUARTZ tables used by syncope idm. WORK AROUND: 1. drop and create syncope db again (or just make empty) with current MySQL database 2. download attached file, save it under core/src/main/resources/quartz/ (create required path) 3. rebuild and redeploy 4. verify Quartz tables are now created as follows: bash-4.1# mysql -uroot -pwelcome syncope -A : mysql show tables like 'QRTZ%'; +---+ | Tables_in_syncope (QRTZ%) | +---+ | QRTZ_BLOB_TRIGGERS| | QRTZ_CALENDARS| | QRTZ_CRON_TRIGGERS| | QRTZ_FIRED_TRIGGERS | | QRTZ_JOB_DETAILS | | QRTZ_LOCKS| | QRTZ_PAUSED_TRIGGER_GRPS | | QRTZ_SCHEDULER_STATE | | QRTZ_SIMPLE_TRIGGERS | | QRTZ_SIMPROP_TRIGGERS | | QRTZ_TRIGGERS | +---+ 11 rows in set (0.00 sec) mysql -- 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-373) 500 when self reading admin user
[ https://issues.apache.org/jira/browse/SYNCOPE-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13668178#comment-13668178 ] Hudson commented on SYNCOPE-373: Integrated in Syncope-trunk #222 (See [https://builds.apache.org/job/Syncope-trunk/222/]) [SYNCOPE-373] Merge from 1_1_X (Revision 1486803) Result = FAILURE ilgrosso : Files : * /syncope/trunk * /syncope/trunk/build-tools/pom.xml * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/BulkActionResultModalPage.java * /syncope/trunk/console/src/main/resources/org/apache/syncope/console/markup/html/CrontabContainer_pt_BR.properties * /syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/data/UserDataBinder.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/security/SyncopeAuthenticationProvider.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/security/SyncopeUserDetailsService.java * /syncope/trunk/core/src/main/resources/restContext.xml * /syncope/trunk/core/src/main/resources/securityContext.xml * /syncope/trunk/core/src/main/resources/syncopeContext.xml * /syncope/trunk/core/src/main/resources/workflowContext.xml * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/AbstractTest.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/UserTestITCase.java 500 when self reading admin user Key: SYNCOPE-373 URL: https://issues.apache.org/jira/browse/SYNCOPE-373 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.1.1 Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Fix For: 1.1.2, 1.2.0 When accessing [1] or [2], an error 500 is returned and the following stacktrace is found in the logs: 08:43:48.525 ERROR org.apache.syncope.core.rest.controller.AbstractController - Exception thrown by REST methods java.lang.IllegalArgumentException: Source must not be null at org.springframework.util.Assert.notNull(Assert.java:112) ~[spring-core-3.2.3.RELEASE.jar:3.2.3.RELEASE] at org.springframework.beans.BeanUtils.copyProperties(BeanUtils.java:589) ~[spring-beans-3.2.3.RELEASE.jar:3.2.3.RELEASE] at org.springframework.beans.BeanUtils.copyProperties(BeanUtils.java:571) ~[spring-beans-3.2.3.RELEASE.jar:3.2.3.RELEASE] at org.apache.syncope.core.rest.data.UserDataBinder.getUserTO(UserDataBinder.java:394) ~[UserDataBinder.class:na] at org.apache.syncope.core.rest.data.UserDataBinder.getAuthenticatedUserTO(UserDataBinder.java:100) ~[UserDataBinder.class:na] [1] /syncope/cxf/users/self [2] /syncope/rest/user/read/self.json -- 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-373) 500 when self reading admin user
[ https://issues.apache.org/jira/browse/SYNCOPE-373?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13668188#comment-13668188 ] Hudson commented on SYNCOPE-373: Integrated in Syncope-1_1_X #48 (See [https://builds.apache.org/job/Syncope-1_1_X/48/]) [SYNCOPE-373] Return fake UserTO for admin when self-reading (Revision 1486793) Result = SUCCESS ilgrosso : Files : * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/rest/data/UserDataBinder.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/security/SyncopeAuthenticationProvider.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/security/SyncopeUserDetailsService.java * /syncope/branches/1_1_X/core/src/main/resources/restContext.xml * /syncope/branches/1_1_X/core/src/main/resources/securityContext.xml * /syncope/branches/1_1_X/core/src/main/resources/syncopeContext.xml * /syncope/branches/1_1_X/core/src/main/resources/workflowContext.xml * /syncope/branches/1_1_X/core/src/test/java/org/apache/syncope/core/rest/AbstractTest.java * /syncope/branches/1_1_X/core/src/test/java/org/apache/syncope/core/rest/UserTestITCase.java 500 when self reading admin user Key: SYNCOPE-373 URL: https://issues.apache.org/jira/browse/SYNCOPE-373 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.1.1 Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Fix For: 1.1.2, 1.2.0 When accessing [1] or [2], an error 500 is returned and the following stacktrace is found in the logs: 08:43:48.525 ERROR org.apache.syncope.core.rest.controller.AbstractController - Exception thrown by REST methods java.lang.IllegalArgumentException: Source must not be null at org.springframework.util.Assert.notNull(Assert.java:112) ~[spring-core-3.2.3.RELEASE.jar:3.2.3.RELEASE] at org.springframework.beans.BeanUtils.copyProperties(BeanUtils.java:589) ~[spring-beans-3.2.3.RELEASE.jar:3.2.3.RELEASE] at org.springframework.beans.BeanUtils.copyProperties(BeanUtils.java:571) ~[spring-beans-3.2.3.RELEASE.jar:3.2.3.RELEASE] at org.apache.syncope.core.rest.data.UserDataBinder.getUserTO(UserDataBinder.java:394) ~[UserDataBinder.class:na] at org.apache.syncope.core.rest.data.UserDataBinder.getAuthenticatedUserTO(UserDataBinder.java:100) ~[UserDataBinder.class:na] [1] /syncope/cxf/users/self [2] /syncope/rest/user/read/self.json -- 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-374) SyncopeUser tokens do not use secure random strings
[ https://issues.apache.org/jira/browse/SYNCOPE-374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13668328#comment-13668328 ] Hudson commented on SYNCOPE-374: Integrated in Syncope-trunk #224 (See [https://builds.apache.org/job/Syncope-trunk/224/]) merge from 1_1_X to close [SYNCOPE-374] (Revision 1486919) Result = SUCCESS massi : Files : * /syncope/trunk * /syncope/trunk/core/src/main/java/org/apache/syncope/core/connid/ConnObjectUtil.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/persistence/beans/user/SyncopeUser.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/util/MappingUtil.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/util/SecureRandomUtil.java SyncopeUser tokens do not use secure random strings --- Key: SYNCOPE-374 URL: https://issues.apache.org/jira/browse/SYNCOPE-374 Project: Syncope Issue Type: Improvement Components: core Affects Versions: 1.1.1 Reporter: Jesse van Bekkum Assignee: Massimiliano Perrone Priority: Minor Fix For: 1.1.2, 1.2.0 The SyncopeUser.generateToken() function generates a token using the RandomStringUtils class. This class uses the normal java random class, which uses the current time in milliseconds as seed. This means that the generated tokens can be predicted by an attacker. This forum post explains the issue: http://stackoverflow.com/questions/1741160/how-can-i-create-a-password It also lists some solutions. It is more secure to use a cryptographically secure string, as explained here: http://commons.apache.org/proper/commons-math/userguide/random.html -- 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-285) Complete CXF migration
[ https://issues.apache.org/jira/browse/SYNCOPE-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13666263#comment-13666263 ] Hudson commented on SYNCOPE-285: Integrated in Syncope-trunk #221 (See [https://builds.apache.org/job/Syncope-trunk/221/]) SYNCOPE-285 Added missing JAX-B Annotations (Revision 1485957) Result = SUCCESS jbernhardt : Files : * /syncope/trunk/common/src/main/java/org/apache/syncope/common/mod/ReferenceMod.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/mod/RoleMod.java Complete CXF migration -- Key: SYNCOPE-285 URL: https://issues.apache.org/jira/browse/SYNCOPE-285 Project: Syncope Issue Type: Bug Reporter: Francesco Chicchiriccò Fix For: 1.2.0 Complete the migration to Apache CXF. -- 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-371) Console RuntimeException with multiple sessions for the same user
[ https://issues.apache.org/jira/browse/SYNCOPE-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13662970#comment-13662970 ] Hudson commented on SYNCOPE-371: Integrated in Syncope-trunk #218 (See [https://builds.apache.org/job/Syncope-trunk/218/]) merge from 1_1_X to fix SYNCOPE-371 (Revision 1484737) Result = SUCCESS massi : Files : * /syncope/trunk/console/src/main/resources/applicationContext.xml Console RuntimeException with multiple sessions for the same user - Key: SYNCOPE-371 URL: https://issues.apache.org/jira/browse/SYNCOPE-371 Project: Syncope Issue Type: Bug Components: console Affects Versions: 1.1.1 Reporter: Massimiliano Perrone Assignee: Massimiliano Perrone Fix For: 1.1.2, 1.2.0 1) Open two browsers 2) Authenticate in both browsers 3) Logout from one of them 4) Click on Reports Tab of the browser where the user is still authenticated: Runtime Exception -- 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-371) Console RuntimeException with multiple sessions for the same user
[ https://issues.apache.org/jira/browse/SYNCOPE-371?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13662971#comment-13662971 ] Hudson commented on SYNCOPE-371: Integrated in Syncope-1_1_X #44 (See [https://builds.apache.org/job/Syncope-1_1_X/44/]) RestTemplate scope has to be session, Fixed SYNCOPE-371 (Revision 1484736) Result = SUCCESS massi : Files : * /syncope/branches/1_1_X/console/src/main/resources/applicationContext.xml Console RuntimeException with multiple sessions for the same user - Key: SYNCOPE-371 URL: https://issues.apache.org/jira/browse/SYNCOPE-371 Project: Syncope Issue Type: Bug Components: console Affects Versions: 1.1.1 Reporter: Massimiliano Perrone Assignee: Massimiliano Perrone Fix For: 1.1.2, 1.2.0 1) Open two browsers 2) Authenticate in both browsers 3) Logout from one of them 4) Click on Reports Tab of the browser where the user is still authenticated: Runtime Exception -- 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-369) Wrong error message on failed login
[ https://issues.apache.org/jira/browse/SYNCOPE-369?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13652914#comment-13652914 ] Hudson commented on SYNCOPE-369: Integrated in Syncope-1_1_X #32 (See [https://builds.apache.org/job/Syncope-1_1_X/32/]) [SYNCOPE-369] Adapting login form to 1.1.X SyncopeClientErrorHanlder (Revision 1480575) Result = SUCCESS ilgrosso : Files : * /syncope/branches/1_1_X/console/src/main/java/org/apache/syncope/console/pages/Login.java * /syncope/branches/1_1_X/console/src/main/java/org/apache/syncope/console/pages/Reports.java Wrong error message on failed login --- Key: SYNCOPE-369 URL: https://issues.apache.org/jira/browse/SYNCOPE-369 Project: Syncope Issue Type: Bug Components: console Affects Versions: 1.1.1 Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Fix For: 1.1.2, 1.2.0 As originally reported in dev ML [1], the admin console gives a wrong message (Session expired: Please login again) instead of Wrong username and / or password, as correctly working with 1.0.X. [1] http://markmail.org/message/eycwemkdjaykvf2f -- 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-368) Cannot add 'RoleOwnerSchema' mapping item via console
[ https://issues.apache.org/jira/browse/SYNCOPE-368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=1366#comment-1366 ] Hudson commented on SYNCOPE-368: Integrated in Syncope-1_1_X #28 (See [https://builds.apache.org/job/Syncope-1_1_X/28/]) [SYNCOPE-368] RoleOwnerSchema was not included as embeeded internal attribute type (Revision 1476962) Result = SUCCESS ilgrosso : Files : * /syncope/branches/1_1_X/common/src/main/java/org/apache/syncope/common/types/IntMappingType.java * /syncope/branches/1_1_X/core/src/test/java/org/apache/syncope/core/rest/AbstractTest.java * /syncope/branches/1_1_X/core/src/test/java/org/apache/syncope/core/rest/AuthenticationTestITCase.java * /syncope/branches/1_1_X/core/src/test/java/org/apache/syncope/core/rest/DerivedSchemaTestITCase.java * /syncope/branches/1_1_X/core/src/test/java/org/apache/syncope/core/rest/PolicyTestITCase.java * /syncope/branches/1_1_X/core/src/test/java/org/apache/syncope/core/rest/ResourceTestITCase.java * /syncope/branches/1_1_X/core/src/test/java/org/apache/syncope/core/rest/RoleTestITCase.java * /syncope/branches/1_1_X/core/src/test/java/org/apache/syncope/core/rest/SchemaTestITCase.java * /syncope/branches/1_1_X/core/src/test/java/org/apache/syncope/core/rest/VirtualSchemaTestITCase.java Cannot add 'RoleOwnerSchema' mapping item via console - Key: SYNCOPE-368 URL: https://issues.apache.org/jira/browse/SYNCOPE-368 Project: Syncope Issue Type: Bug Components: common Affects Versions: 1.1.0 Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Fix For: 1.1.1, 1.2.0 When trying to add role mapping with intAttrType RoleOwnerSchema, an error is returned [RequiredValuesMissing [intAttrName]] -- 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-367) ConfigurationTestITCase#browseAccountPolicy Selenium test fails
[ https://issues.apache.org/jira/browse/SYNCOPE-367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13644635#comment-13644635 ] Hudson commented on SYNCOPE-367: Integrated in Syncope-1_1_X #29 (See [https://builds.apache.org/job/Syncope-1_1_X/29/]) [SYNCOPE-367] Performing no changes since all Selenium tests are passing on Linux with latest Firefox (Revision 1477104) Result = SUCCESS ilgrosso : Files : * /syncope/branches/1_1_X/console/src/main/resources/org/apache/syncope/console/pages/Configuration.html * /syncope/branches/1_1_X/console/src/main/resources/org/apache/syncope/console/pages/panels/PoliciesPanel.html * /syncope/branches/1_1_X/console/src/test/java/org/apache/syncope/console/ConfigurationTestITCase.java ConfigurationTestITCase#browseAccountPolicy Selenium test fails --- Key: SYNCOPE-367 URL: https://issues.apache.org/jira/browse/SYNCOPE-367 Project: Syncope Issue Type: Bug Components: console Affects Versions: 1.1.1 Reporter: fabio martelli Assignee: Francesco Chicchiriccò Priority: Minor Labels: selenium, test Fix For: 1.1.1, 1.2.0 Selenium test org.apache.syncope.console.ConfigurationTestITCase#browseAccountPolicy * fails if executed with all other Selenium tests * doesn't fail if execute alone -- 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-tabpanelfocusedCommentId=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-357) When deleting role on external resource, also remove from there users with resource assigned only via that role
[ https://issues.apache.org/jira/browse/SYNCOPE-357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13640972#comment-13640972 ] Hudson commented on SYNCOPE-357: Integrated in Syncope-1_1_X #25 (See [https://builds.apache.org/job/Syncope-1_1_X/25/]) [SYNCOPE-357] RoleController#delete() now checks for assigned users and generates delete propagation tasks if needed (Revision 1471476) Result = SUCCESS ilgrosso : Files : * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/persistence/beans/user/SyncopeUser.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/propagation/impl/PropagationManager.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/rest/controller/RoleController.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/rest/data/RoleDataBinder.java * /syncope/branches/1_1_X/core/src/test/java/org/apache/syncope/core/rest/UserTestITCase.java When deleting role on external resource, also remove from there users with resource assigned only via that role --- Key: SYNCOPE-357 URL: https://issues.apache.org/jira/browse/SYNCOPE-357 Project: Syncope Issue Type: Bug Affects Versions: 1.1.0 Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Fix For: 1.1.1, 1.2.0 Scenario: * resource RES with mapping for both users and roles * role ROLE with RES assigned * user USER with role ROLE assigned, and no RES assigned for other reasons (directly or via another role) As result, USER is present on the physical resource represented by RES (e.g. an actual LDAP server, for example). When removing ROLE from Syncope, ROLE is also removed from the physical resource represented by RES, while USER is not removed from the physical resource: this must be fixed, USER is needed to be also removed from there. If, instead, USER has RES assigned directly or via another role, no action must be performed onto the physical resource. -- 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-354) LDAP Membership propagation does not remove memberships
[ https://issues.apache.org/jira/browse/SYNCOPE-354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13640973#comment-13640973 ] Hudson commented on SYNCOPE-354: Integrated in Syncope-1_1_X #25 (See [https://builds.apache.org/job/Syncope-1_1_X/25/]) [SYNCOPE-354] ResourceOperation.DELETE not always resolve to delete() on connector, it might also become update() - removing the condition from LDAPMembershipSyncActions (Revision 1471403) Result = SUCCESS ilgrosso : Files : * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/propagation/impl/LDAPMembershipPropagationActions.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/util/URIUtil.java * /syncope/branches/1_1_X/core/src/test/java/org/apache/syncope/core/rest/UserTestITCase.java LDAP Membership propagation does not remove memberships --- Key: SYNCOPE-354 URL: https://issues.apache.org/jira/browse/SYNCOPE-354 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.1.0 Environment: n/a Reporter: James Flemer Assignee: Francesco Chicchiriccò Labels: delete, ldap, propagation, role Fix For: 1.1.1, 1.2.0 Configure a LDAP connector and resource, use the LDAPMembershipPropagationActions propagator class, add a LDAP role to a user, then try to remove that role. The role is removed in Syncope but not LDAP; the next sync will add it back in Syncope. In LDAPMembershipPropagationActions, line 75 (Syncope 1.1.0), there is a conditional on: ResourceOperation.DELETE != task.getPropagationOperation So LDAPMembershipPropagationActions refuses to process any delete operations. Should the operation be DELETE here (vs UPDATE)? If so, LDAPMembershipPropagationActions needs to deal with DELETE appropriately. -- 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-365) External attribute disabled in case of schema info not available
[ https://issues.apache.org/jira/browse/SYNCOPE-365?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13640974#comment-13640974 ] Hudson commented on SYNCOPE-365: Integrated in Syncope-1_1_X #25 (See [https://builds.apache.org/job/Syncope-1_1_X/25/]) SYNCOPE-365 fixed (Revision 1471489) Result = SUCCESS fmartelli : Files : * /syncope/branches/1_1_X/console/src/main/java/org/apache/syncope/console/pages/panels/ResourceMappingPanel.java * /syncope/branches/1_1_X/console/src/test/java/org/apache/syncope/console/ConfigurationTestITCase.java * /syncope/branches/1_1_X/console/src/test/java/org/apache/syncope/console/ConnInstanceTestITCase.java External attribute disabled in case of schema info not available Key: SYNCOPE-365 URL: https://issues.apache.org/jira/browse/SYNCOPE-365 Project: Syncope Issue Type: Bug Affects Versions: 1.1.0, 1.1.1 Reporter: fabio martelli Assignee: fabio martelli Fix For: 1.1.1, 1.2.0 External attribute disabled in case of schema info not available -- 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-354) LDAP Membership propagation does not remove memberships
[ https://issues.apache.org/jira/browse/SYNCOPE-354?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13641012#comment-13641012 ] Hudson commented on SYNCOPE-354: Integrated in Syncope-trunk #202 (See [https://builds.apache.org/job/Syncope-trunk/202/]) [SYNCOPE-354] Merge from 1_1_X (Revision 1471405) Result = SUCCESS ilgrosso : Files : * /syncope/trunk * /syncope/trunk/core/src/main/java/org/apache/syncope/core/propagation/impl/LDAPMembershipPropagationActions.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/util/URIUtil.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/UserTestITCase.java LDAP Membership propagation does not remove memberships --- Key: SYNCOPE-354 URL: https://issues.apache.org/jira/browse/SYNCOPE-354 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.1.0 Environment: n/a Reporter: James Flemer Assignee: Francesco Chicchiriccò Labels: delete, ldap, propagation, role Fix For: 1.1.1, 1.2.0 Configure a LDAP connector and resource, use the LDAPMembershipPropagationActions propagator class, add a LDAP role to a user, then try to remove that role. The role is removed in Syncope but not LDAP; the next sync will add it back in Syncope. In LDAPMembershipPropagationActions, line 75 (Syncope 1.1.0), there is a conditional on: ResourceOperation.DELETE != task.getPropagationOperation So LDAPMembershipPropagationActions refuses to process any delete operations. Should the operation be DELETE here (vs UPDATE)? If so, LDAPMembershipPropagationActions needs to deal with DELETE appropriately. -- 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-361) When creating new report, the modal window does not close and an exception is logged
[ https://issues.apache.org/jira/browse/SYNCOPE-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13636687#comment-13636687 ] Hudson commented on SYNCOPE-361: Integrated in Syncope-1_1_X #22 (See [https://builds.apache.org/job/Syncope-1_1_X/22/]) [SYNCOPE-361] Handling mapping reset (Revision 1469758) [SYNCOPE-361] Fixing ReportService#create invocation (Revision 1469739) Result = SUCCESS ilgrosso : Files : * /syncope/branches/1_1_X/console/src/main/java/org/apache/syncope/console/pages/ResourceModalPage.java * /syncope/branches/1_1_X/console/src/main/java/org/apache/syncope/console/pages/panels/ResourceMappingPanel.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/rest/data/ResourceDataBinder.java * /syncope/branches/1_1_X/core/src/test/java/org/apache/syncope/core/persistence/relationships/ResourceTest.java * /syncope/branches/1_1_X/core/src/test/java/org/apache/syncope/core/rest/ResourceTestITCase.java ilgrosso : Files : * /syncope/branches/1_1_X/console/src/main/java/org/apache/syncope/console/rest/ReportRestClient.java When creating new report, the modal window does not close and an exception is logged Key: SYNCOPE-361 URL: https://issues.apache.org/jira/browse/SYNCOPE-361 Project: Syncope Issue Type: Bug Components: console Affects Versions: 1.1.0 Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Priority: Minor Fix For: 1.1.1, 1.2.0 When creating new report from the admin console, everything goes smooth until the Save button is pressed:at that point the modal window does not close and an exception is logged. The new report, however, is correctly created. -- 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-362) Disable mapping tab when the underlying connector does not support correspondent ObjectClass
[ https://issues.apache.org/jira/browse/SYNCOPE-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13636686#comment-13636686 ] Hudson commented on SYNCOPE-362: Integrated in Syncope-1_1_X #22 (See [https://builds.apache.org/job/Syncope-1_1_X/22/]) [SYNCOPE-362] Added new REST method for enquerying supported ConnId object classes + used such method from admin console to enable / disable related schema mapping (Revision 1469812) Result = SUCCESS ilgrosso : Files : * /syncope/branches/1_1_X/client/src/main/java/org/apache/syncope/client/services/proxy/ConnectorServiceProxy.java * /syncope/branches/1_1_X/common/src/main/java/org/apache/syncope/common/services/ConnectorService.java * /syncope/branches/1_1_X/common/src/main/java/org/apache/syncope/common/to/ConnIdObjectClassTO.java * /syncope/branches/1_1_X/common/src/main/java/org/apache/syncope/common/types/AuditElements.java * /syncope/branches/1_1_X/console/src/main/java/org/apache/syncope/console/pages/panels/ResourceDetailsPanel.java * /syncope/branches/1_1_X/console/src/main/java/org/apache/syncope/console/pages/panels/ResourceMappingPanel.java * /syncope/branches/1_1_X/console/src/main/java/org/apache/syncope/console/rest/ConnectorRestClient.java * /syncope/branches/1_1_X/console/src/main/resources/org/apache/syncope/console/pages/panels/ResourceDetailsPanel.html * /syncope/branches/1_1_X/core/pom.xml * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/propagation/Connector.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/propagation/impl/AsyncConnectorFacade.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/propagation/impl/ConnectorFacadeProxy.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/rest/controller/ConnInstanceController.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/services/ConnectorServiceImpl.java * /syncope/branches/1_1_X/core/src/test/java/org/apache/syncope/core/rest/ConnInstanceTestITCase.java Disable mapping tab when the underlying connector does not support correspondent ObjectClass Key: SYNCOPE-362 URL: https://issues.apache.org/jira/browse/SYNCOPE-362 Project: Syncope Issue Type: Improvement Components: console, core Affects Versions: 1.1.0 Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Fix For: 1.1.1, 1.2.0 If a given connector supports ObjectClass.ACCOUNT, enable the User mapping tab, otherwise keep it disabled. If a given connector supports ObjectClass.GROUP, enable the Role mapping tab, otherwise keep it disabled. -- 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-364) Rejected users are anyway propagate to associated resources
[ https://issues.apache.org/jira/browse/SYNCOPE-364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13636688#comment-13636688 ] Hudson commented on SYNCOPE-364: Integrated in Syncope-1_1_X #22 (See [https://builds.apache.org/job/Syncope-1_1_X/22/]) [SYNCOPE-364] Merge from 1_0_X (Revision 1469880) Result = SUCCESS ilgrosso : Files : * /syncope/branches/1_1_X * /syncope/branches/1_1_X/CHANGES * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/rest/controller/UserController.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/workflow/user/activiti/ActivitiUserWorkflowAdapter.java * /syncope/branches/1_1_X/core/src/main/resources/userWorkflow.bpmn20.xml * /syncope/branches/1_1_X/core/src/test/java/org/apache/syncope/core/rest/UserTestITCase.java Rejected users are anyway propagate to associated resources --- Key: SYNCOPE-364 URL: https://issues.apache.org/jira/browse/SYNCOPE-364 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.0.8, 1.1.0 Reporter: Francesco Chicchiriccò Fix For: 1.0.9, 1.1.1, 1.2.0 Using the default worklfow, when an user is created with an external resource, goes through approval and is rejected, a propagation towards the given external resource is anyway performed. -- 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-363) ApacheDS not available since second run of the standalone distribution
[ https://issues.apache.org/jira/browse/SYNCOPE-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13636689#comment-13636689 ] Hudson commented on SYNCOPE-363: Integrated in Syncope-1_1_X #22 (See [https://builds.apache.org/job/Syncope-1_1_X/22/]) [SYNCOPE-363] Creating ApacheDS work directory and loading default content only for first run (Revision 1469830) Result = SUCCESS ilgrosso : Files : * /syncope/branches/1_1_X/build-tools/src/main/java/org/apache/syncope/buildtools/ApacheDSStartStopListener.java ApacheDS not available since second run of the standalone distribution -- Key: SYNCOPE-363 URL: https://issues.apache.org/jira/browse/SYNCOPE-363 Project: Syncope Issue Type: Bug Components: build-tools, standalone Affects Versions: 1.1.0 Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Fix For: 1.1.1, 1.2.0 When starting the standalone distribution, from the second time on the build-tools webapp will refuse to start, leaving Syncope without connectors. This happens since the ApacheDSStartStopListener fails creating its work directory - that is actually already there, used during the first run. -- 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-362) Disable mapping tab when the underlying connector does not support correspondent ObjectClass
[ https://issues.apache.org/jira/browse/SYNCOPE-362?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13636692#comment-13636692 ] Hudson commented on SYNCOPE-362: Integrated in Syncope-trunk #200 (See [https://builds.apache.org/job/Syncope-trunk/200/]) [SYNCOPE-362] Merge from 1_1_X (Revision 1469814) Result = SUCCESS ilgrosso : Files : * /syncope/trunk * /syncope/trunk/client/src/main/java/org/apache/syncope/client/services/proxy/ConnectorServiceProxy.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/services/ConnectorService.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/to/ConnIdObjectClassTO.java * /syncope/trunk/common/src/main/java/org/apache/syncope/common/types/AuditElements.java * /syncope/trunk/console/src/main/java/org/apache/syncope/console/pages/panels/ResourceDetailsPanel.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/rest/ConnectorRestClient.java * /syncope/trunk/console/src/main/resources/org/apache/syncope/console/pages/panels/ResourceDetailsPanel.html * /syncope/trunk/core/pom.xml * /syncope/trunk/core/src/main/java/org/apache/syncope/core/propagation/Connector.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/propagation/impl/AsyncConnectorFacade.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/propagation/impl/ConnectorFacadeProxy.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/controller/ConnInstanceController.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/services/ConnectorServiceImpl.java * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/ConnInstanceTestITCase.java Disable mapping tab when the underlying connector does not support correspondent ObjectClass Key: SYNCOPE-362 URL: https://issues.apache.org/jira/browse/SYNCOPE-362 Project: Syncope Issue Type: Improvement Components: console, core Affects Versions: 1.1.0 Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Fix For: 1.1.1, 1.2.0 If a given connector supports ObjectClass.ACCOUNT, enable the User mapping tab, otherwise keep it disabled. If a given connector supports ObjectClass.GROUP, enable the Role mapping tab, otherwise keep it disabled. -- 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-364) Rejected users are anyway propagate to associated resources
[ https://issues.apache.org/jira/browse/SYNCOPE-364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13636694#comment-13636694 ] Hudson commented on SYNCOPE-364: Integrated in Syncope-trunk #200 (See [https://builds.apache.org/job/Syncope-trunk/200/]) [SYNCOPE-364] Merge from 1_1_X (Revision 1469883) Result = SUCCESS ilgrosso : Files : * /syncope/trunk * /syncope/trunk/CHANGES * /syncope/trunk/core/src/main/java/org/apache/syncope/core/rest/controller/UserController.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/workflow/user/activiti/ActivitiUserWorkflowAdapter.java * /syncope/trunk/core/src/main/resources/userWorkflow.bpmn20.xml * /syncope/trunk/core/src/test/java/org/apache/syncope/core/rest/UserTestITCase.java Rejected users are anyway propagate to associated resources --- Key: SYNCOPE-364 URL: https://issues.apache.org/jira/browse/SYNCOPE-364 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.0.8, 1.1.0 Reporter: Francesco Chicchiriccò Fix For: 1.0.9, 1.1.1, 1.2.0 Using the default worklfow, when an user is created with an external resource, goes through approval and is rejected, a propagation towards the given external resource is anyway performed. -- 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-363) ApacheDS not available since second run of the standalone distribution
[ https://issues.apache.org/jira/browse/SYNCOPE-363?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13636695#comment-13636695 ] Hudson commented on SYNCOPE-363: Integrated in Syncope-trunk #200 (See [https://builds.apache.org/job/Syncope-trunk/200/]) [SYNCOPE-363] Merge from 1_1_X (Revision 1469831) Result = SUCCESS ilgrosso : Files : * /syncope/trunk * /syncope/trunk/build-tools/src/main/java/org/apache/syncope/buildtools/ApacheDSStartStopListener.java ApacheDS not available since second run of the standalone distribution -- Key: SYNCOPE-363 URL: https://issues.apache.org/jira/browse/SYNCOPE-363 Project: Syncope Issue Type: Bug Components: build-tools, standalone Affects Versions: 1.1.0 Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Fix For: 1.1.1, 1.2.0 When starting the standalone distribution, from the second time on the build-tools webapp will refuse to start, leaving Syncope without connectors. This happens since the ApacheDSStartStopListener fails creating its work directory - that is actually already there, used during the first run. -- 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-364) Rejected users are anyway propagate to associated resources
[ https://issues.apache.org/jira/browse/SYNCOPE-364?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13636884#comment-13636884 ] Hudson commented on SYNCOPE-364: Integrated in Syncope-1_0_X #191 (See [https://builds.apache.org/job/Syncope-1_0_X/191/]) [SYNCOPE-364] Disabling propagation from workflow definition (Revision 1469875) Result = FAILURE ilgrosso : Files : * /syncope/branches/1_0_X/core/src/main/java/org/apache/syncope/core/rest/controller/UserController.java * /syncope/branches/1_0_X/core/src/main/resources/userWorkflow.bpmn20.xml * /syncope/branches/1_0_X/core/src/test/java/org/apache/syncope/core/rest/UserTestITCase.java Rejected users are anyway propagate to associated resources --- Key: SYNCOPE-364 URL: https://issues.apache.org/jira/browse/SYNCOPE-364 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.0.8, 1.1.0 Reporter: Francesco Chicchiriccò Fix For: 1.0.9, 1.1.1, 1.2.0 Using the default worklfow, when an user is created with an external resource, goes through approval and is rejected, a propagation towards the given external resource is anyway performed. -- 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-359) Ignore propagation if no schema mapping is provided
[ https://issues.apache.org/jira/browse/SYNCOPE-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13634030#comment-13634030 ] Hudson commented on SYNCOPE-359: Integrated in Syncope-1_1_X #19 (See [https://builds.apache.org/job/Syncope-1_1_X/19/]) [SYNCOPE-359] Not generating PropagationTask instances when no mapping is provided (Revision 1468807) Result = SUCCESS ilgrosso : Files : * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/propagation/impl/PropagationManager.java * /syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/util/AttributableUtil.java Ignore propagation if no schema mapping is provided --- Key: SYNCOPE-359 URL: https://issues.apache.org/jira/browse/SYNCOPE-359 Project: Syncope Issue Type: Improvement Components: core Affects Versions: 1.1.0 Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Fix For: 1.1.1, 1.2.0 When, for a given external resource, no mapping is defined (for users, for roles or both), the PropagationManager should not generate any propagation task. This is a safer alternative to the current handling, where tasks are generated but will fail because of missing schema mapping. -- 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-358) ConnectorService#list invocation with null parameter actually calls ConnectorService#readByResource
[
https://issues.apache.org/jira/browse/SYNCOPE-358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13631732#comment-13631732
]
Hudson commented on SYNCOPE-358:
Integrated in Syncope-1_1_X #16 (See
[https://builds.apache.org/job/Syncope-1_1_X/16/])
[SYNCOPE-358] Applying JAX-RS annotation change to
ConnectorService#readByResource and reverting changes to ConnInstanceTestITCase
(Revision 1467953)
[SYNCOPE-358] Fixing typo QueryResourceInfoComperator instead of
QueryResourceInfoComperator (Revision 1467948)
Result = SUCCESS
ilgrosso :
Files :
*
/syncope/branches/1_1_X/common/src/main/java/org/apache/syncope/common/services/ConnectorService.java
*
/syncope/branches/1_1_X/core/src/test/java/org/apache/syncope/core/rest/ConnInstanceTestITCase.java
ilgrosso :
Files :
*
/syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/rest/utils/QueryResourceInfoComparator.java
*
/syncope/branches/1_1_X/core/src/main/java/org/apache/syncope/core/rest/utils/QueryResourceInfoComperator.java
* /syncope/branches/1_1_X/core/src/main/resources/restContext.xml
ConnectorService#list invocation with null parameter actually calls
ConnectorService#readByResource
---
Key: SYNCOPE-358
URL: https://issues.apache.org/jira/browse/SYNCOPE-358
Project: Syncope
Issue Type: Bug
Components: client, common, core
Affects Versions: 1.1.0
Reporter: Francesco Chicchiriccò
Assignee: Francesco Chicchiriccò
Fix For: 1.1.1, 1.2.0
As discussed in mailing list [1], this can be fixed by changing
@GET
ConnInstanceTO readByResource(@MatrixParam(resourceName) String
resourceName);
into
@GET
@Path(byResource/{resourceName})
ConnInstanceTO readByResource(@PathParam(resourceName) String
resourceName);
[1]
http://syncope-dev.1063484.n5.nabble.com/DISCUSS-ConnectorService-Java-7-and-MatrixParam-tt5713486.html
--
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
