[jira] [Created] (SYNCOPE-272) Apache Syncope updates all attributes from an user
Marco Di Sabatino Di Diodoro created SYNCOPE-272: Summary: Apache Syncope updates all attributes from an user Key: SYNCOPE-272 URL: https://issues.apache.org/jira/browse/SYNCOPE-272 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.0.5 Reporter: Marco Di Sabatino Di Diodoro Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.0.5, 1.1.0 During synchronization task, Apache Syncope updates all attributes from an user, specially the attributes that come from the synched resource and the calculed attributes(JEXL) of the user template. If an attribute is not present in the schema mapping of the synched resource, but is present in the user template with null value, Apache Syncope clear the attribute value. If an attribute of the user template is not valued, it must not be considered. I attach a test for solve this issue. -- 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] [Updated] (SYNCOPE-272) Apache Syncope updates all attributes from an user
[ https://issues.apache.org/jira/browse/SYNCOPE-272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro updated SYNCOPE-272: - Attachment: testissueSYNCOPE272.patch Apache Syncope updates all attributes from an user -- Key: SYNCOPE-272 URL: https://issues.apache.org/jira/browse/SYNCOPE-272 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.0.5 Reporter: Marco Di Sabatino Di Diodoro Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.0.5, 1.1.0 Attachments: testissueSYNCOPE272.patch During synchronization task, Apache Syncope updates all attributes from an user, specially the attributes that come from the synched resource and the calculed attributes(JEXL) of the user template. If an attribute is not present in the schema mapping of the synched resource, but is present in the user template with null value, Apache Syncope clear the attribute value. If an attribute of the user template is not valued, it must not be considered. I attach a test for solve this issue. -- 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-272) Apache Syncope updates all attributes from an user
[ https://issues.apache.org/jira/browse/SYNCOPE-272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13552520#comment-13552520 ] Marco Di Sabatino Di Diodoro commented on SYNCOPE-272: -- Fix for 1_0_X http://svn.apache.org/viewvc?view=revisionrevision=1432844 Apache Syncope updates all attributes from an user -- Key: SYNCOPE-272 URL: https://issues.apache.org/jira/browse/SYNCOPE-272 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.0.5 Reporter: Marco Di Sabatino Di Diodoro Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.0.5, 1.1.0 Attachments: testissueSYNCOPE272.patch During synchronization task, Apache Syncope updates all attributes from an user, specially the attributes that come from the synched resource and the calculed attributes(JEXL) of the user template. If an attribute is not present in the schema mapping of the synched resource, but is present in the user template with null value, Apache Syncope clear the attribute value. If an attribute of the user template is not valued, it must not be considered. I attach a test for solve this issue. -- 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] [Resolved] (SYNCOPE-272) During sync null attributes from template are considered
[ https://issues.apache.org/jira/browse/SYNCOPE-272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-272. -- Resolution: Fixed http://svn.apache.org/viewvc?rev=1432929view=rev During sync null attributes from template are considered Key: SYNCOPE-272 URL: https://issues.apache.org/jira/browse/SYNCOPE-272 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.0.5 Reporter: Marco Di Sabatino Di Diodoro Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.0.5 Attachments: testissueSYNCOPE272.patch During execution of synchronization tasks, all user attributes are considered for update, with values coming from the syncing resource and from evaluated JEXL properties in the user template. If an attribute is not present in the schema mapping of the syncing resource but is present in the user template with null value, the value is cleared and the attribute removed. This is not correct: if an attribute of the user template has no value, it must not be considered. A test for proving this issue is attached. -- 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] [Created] (SYNCOPE-274) Sync: during update with user template existing memberships break update
Marco Di Sabatino Di Diodoro created SYNCOPE-274: Summary: Sync: during update with user template existing memberships break update Key: SYNCOPE-274 URL: https://issues.apache.org/jira/browse/SYNCOPE-274 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.0.4 Reporter: Marco Di Sabatino Di Diodoro Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.0.5, 1.1.0 Suppose user A has membership (ID=100) for role R. During synchronization from an external resource, if A is picked up for update and an user template is configured with membership for role R, the ongoing transaction breaks with error AttributableTO's id must be the same -- 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-274) Sync: during update with user template existing memberships break update
[ https://issues.apache.org/jira/browse/SYNCOPE-274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13553703#comment-13553703 ] Marco Di Sabatino Di Diodoro commented on SYNCOPE-274: -- Fix for branch 1_0_X http://svn.apache.org/viewvc?rev=1433361view=rev Sync: during update with user template existing memberships break update Key: SYNCOPE-274 URL: https://issues.apache.org/jira/browse/SYNCOPE-274 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.0.4 Reporter: Marco Di Sabatino Di Diodoro Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.0.5, 1.1.0 Suppose user A has membership (ID=100) for role R. During synchronization from an external resource, if A is picked up for update and an user template is configured with membership for role R, the ongoing transaction breaks with error AttributableTO's id must be the same -- 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] [Resolved] (SYNCOPE-199) Refocus on user deletion page
[ https://issues.apache.org/jira/browse/SYNCOPE-199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-199. -- Resolution: Fixed http://svn.apache.org/viewvc?rev=1434678view=rev Refocus on user deletion page - Key: SYNCOPE-199 URL: https://issues.apache.org/jira/browse/SYNCOPE-199 Project: Syncope Issue Type: Improvement Reporter: Colm O hEigeartaigh Assignee: Marco Di Sabatino Di Diodoro Priority: Trivial Fix For: 1.1.0 SYNCOPE-189 added the ability to close a window on pressing ESC. It would be nice when deleting a user to automatically reselect the deletion page, so that the user can just press ESC to close the window. Currently you need to click on the deletion page before pressing ESC. -- 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] [Resolved] (SYNCOPE-229) Allow to change the bundle version associated to an existing connector instance
[ https://issues.apache.org/jira/browse/SYNCOPE-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-229. -- Resolution: Fixed http://svn.apache.org/viewvc?rev=1437380view=rev Allow to change the bundle version associated to an existing connector instance --- Key: SYNCOPE-229 URL: https://issues.apache.org/jira/browse/SYNCOPE-229 Project: Syncope Issue Type: Improvement Reporter: Francesco Chicchiriccò Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.1.0 Use case: a new version of a connector bundle is released. It should be possible then to install this new connector bundle in Syncope, then change the bundle version in the corresponding ConnInstance(s) (currently not allowed). All this by taking care of merging existing ConnInstance configuration. [1] http://syncope-user.1051894.n5.nabble.com/csvdir-connector-td5706733.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] [Assigned] (SYNCOPE-198) Add checkboxes to tables headers and rows
[ https://issues.apache.org/jira/browse/SYNCOPE-198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro reassigned SYNCOPE-198: Assignee: Marco Di Sabatino Di Diodoro Add checkboxes to tables headers and rows - Key: SYNCOPE-198 URL: https://issues.apache.org/jira/browse/SYNCOPE-198 Project: Syncope Issue Type: Improvement Components: console Affects Versions: 1.0.1-incubating Reporter: Colm O hEigeartaigh Assignee: Marco Di Sabatino Di Diodoro Priority: Trivial Fix For: 1.1.0 Add checkbox to each row and each header of all tables in the admin console UI. The purpose is to select some (or all) rows for some of available operations (delete, for example). -- 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-135) Password reset
[ https://issues.apache.org/jira/browse/SYNCOPE-135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13562664#comment-13562664 ] Marco Di Sabatino Di Diodoro commented on SYNCOPE-135: -- +1 M -- Dott. Marco Di Sabatino Di Diodoro Tel. +39 3939065570 Tirasa S.r.l. Viale D'Annunzio 267 - 65127 Pescara Tel +39 0859116307 / FAX +39 085973 http://www.tirasa.net Apache Syncope PMC Member http://people.apache.org/~mdisabatino Password reset -- Key: SYNCOPE-135 URL: https://issues.apache.org/jira/browse/SYNCOPE-135 Project: Syncope Issue Type: New Feature Reporter: Francesco Chicchiriccò Fix For: 1.1.0 Provide password reset feature, that can be accessed either trough the console and via REST call. -- 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] [Resolved] (SYNCOPE-138) Scripted SQL connector bundle
[ https://issues.apache.org/jira/browse/SYNCOPE-138?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-138. -- Resolution: Fixed https://cwiki.apache.org/confluence/display/SYNCOPE/Configure+a+Scripted+SQL+resource Scripted SQL connector bundle - Key: SYNCOPE-138 URL: https://issues.apache.org/jira/browse/SYNCOPE-138 Project: Syncope Issue Type: New Feature Reporter: Francesco Chicchiriccò Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.1.0 Provide a scripted SQL connector bundle. Probably connector instance configuration must be reviewed. Check whether OpenICF connector bundle [1] can be used. [1] http://openicf.forgerock.org/connectors/openicf-scriptedsql-connector/ -- 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] [Updated] (SYNCOPE-198) Add checkboxes to tables headers and rows
[ https://issues.apache.org/jira/browse/SYNCOPE-198?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro updated SYNCOPE-198: - Attachment: groupselector.diff Beginning of the development of the console for add checkboxes to tables. Add checkboxes to tables headers and rows - Key: SYNCOPE-198 URL: https://issues.apache.org/jira/browse/SYNCOPE-198 Project: Syncope Issue Type: Improvement Components: console Affects Versions: 1.0.1-incubating Reporter: Colm O hEigeartaigh Assignee: Marco Di Sabatino Di Diodoro Priority: Trivial Fix For: 1.1.0 Attachments: groupselector.diff Add checkbox to each row and each header of all tables in the admin console UI. The purpose is to select some (or all) rows for some of available operations (delete, for example). -- 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-126) Database import / export and related tasks
[ https://issues.apache.org/jira/browse/SYNCOPE-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13588505#comment-13588505 ] Marco Di Sabatino Di Diodoro commented on SYNCOPE-126: -- Case Insensitive Table And Column Names In MySQL While you should always uphold the case-sensitive tablenames, it can be troublesome when migrating from a host that had this option enabled (table column names become case insensitive), to a host that doesn't have this option -- so you suddenly find yourself stuck with case sensitive table and column names. To solve this, edit your /etc/my.cnf file and add the following line into mysqld: lower_case_table_names=1 Database import / export and related tasks -- Key: SYNCOPE-126 URL: https://issues.apache.org/jira/browse/SYNCOPE-126 Project: Syncope Issue Type: Task Components: documentation Reporter: Francesco Chicchiriccò Fix For: 1.1.0 Provide some documentation about how to export / import database content, in particular about sequence tables and their initialization for import. -- 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] [Resolved] (SYNCOPE-396) Method removeAll and retainAll in PropagationByResource does not evaluate correctly boolean expression
[ https://issues.apache.org/jira/browse/SYNCOPE-396?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-396. -- Resolution: Fixed http://svn.apache.org/r1496065 Method removeAll and retainAll in PropagationByResource does not evaluate correctly boolean expression -- Key: SYNCOPE-396 URL: https://issues.apache.org/jira/browse/SYNCOPE-396 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.1.3 Reporter: Marco Di Sabatino Di Diodoro Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.1.3, 1.2.0 || operator short-circuit evaluation in boolean expression. -- 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] [Assigned] (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:all-tabpanel ] Marco Di Sabatino Di Diodoro reassigned SYNCOPE-402: Assignee: Marco Di Sabatino Di Diodoro 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] [Resolved] (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:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-402. -- Resolution: Fixed http://svn.apache.org/viewvc?view=revisionrevision=r1504416 http://svn.apache.org/viewvc?view=revisionrevision=r1504404 http://svn.apache.org/viewvc?view=revisionrevision=r1503757 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] [Resolved] (SYNCOPE-403) Enrich PropagationStatusTO to report possible propagation exception message
[ https://issues.apache.org/jira/browse/SYNCOPE-403?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-403. -- Resolution: Fixed http://svn.apache.org/viewvc?view=revisionrevision=r1504872 Thanks Andrea for your contribution. Enrich PropagationStatusTO to report possible propagation exception message --- Key: SYNCOPE-403 URL: https://issues.apache.org/jira/browse/SYNCOPE-403 Project: Syncope Issue Type: Improvement Components: common, 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 Attachments: SYNCOPE-403.patch PropagationStatusTO may be enriched with a field reporting possible propagation exception message, so that trace exception returned by a resource and get its specific message. -- 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] [Comment Edited] (SYNCOPE-427) Add CSV report format
[ https://issues.apache.org/jira/browse/SYNCOPE-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13810392#comment-13810392 ] Marco Di Sabatino Di Diodoro edited comment on SYNCOPE-427 at 10/31/13 4:13 PM: 1.1.X: http://svn.apache.org/r1537537 trunk: http://svn.apache.org/r1537541 was (Author: mdisabatino): http://svn.apache.org/r1537537 Add CSV report format - Key: SYNCOPE-427 URL: https://issues.apache.org/jira/browse/SYNCOPE-427 Project: Syncope Issue Type: Improvement Components: console, core Reporter: Francesco Chicchiriccò Assignee: Marco Di Sabatino Di Diodoro Priority: Minor Fix For: 1.1.5, 1.2.0 -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (SYNCOPE-436) Read only virtual attribute does not retrieve value from remote resource
[ https://issues.apache.org/jira/browse/SYNCOPE-436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro updated SYNCOPE-436: - Affects Version/s: (was: 1.1.5) (was: 1.2.0) 1.1.4 Fix Version/s: 1.2.0 1.1.5 Read only virtual attribute does not retrieve value from remote 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 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] [Assigned] (SYNCOPE-436) Read only virtual attribute does not retrieve value from remote resource
[ https://issues.apache.org/jira/browse/SYNCOPE-436?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro reassigned SYNCOPE-436: Assignee: Marco Di Sabatino Di Diodoro Read only virtual attribute does not retrieve value from remote 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] [Resolved] (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:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-436. -- Resolution: Fixed Trunk: https://svn.apache.org/r1542946 1_1_X: http://svn.apache.org/r1542229 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] [Resolved] (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:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-436. -- Resolution: Fixed http://svn.apache.org/r1543069 https://svn.apache.org/r1543073 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] [Assigned] (SYNCOPE-445) Provide a text field to specify whatever notification recipient
[ https://issues.apache.org/jira/browse/SYNCOPE-445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro reassigned SYNCOPE-445: Assignee: Marco Di Sabatino Di Diodoro Provide a text field to specify whatever notification recipient --- Key: SYNCOPE-445 URL: https://issues.apache.org/jira/browse/SYNCOPE-445 Project: Syncope Issue Type: Improvement Components: common, console, core Affects Versions: 1.2.0 Reporter: fabio martelli Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.2.0 Provide a text field to specify whatever notification recipient -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (SYNCOPE-485) Upgrade to Activiti 5.15.1
[ https://issues.apache.org/jira/browse/SYNCOPE-485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro reassigned SYNCOPE-485: Assignee: Marco Di Sabatino Di Diodoro Upgrade to Activiti 5.15.1 -- Key: SYNCOPE-485 URL: https://issues.apache.org/jira/browse/SYNCOPE-485 Project: Syncope Issue Type: Improvement Reporter: Francesco Chicchiriccò Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.1.8, 1.2.0 Today Activiti 5.15.1 was released [1]: upgrade needed both for branch 1_1_X and trunk: in the latter case additional care must be taken in order to check if modeler is working from admin console. [1] http://bpmn20inaction.blogspot.it/2014/04/activiti-5151-released.html -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (SYNCOPE-485) Upgrade to Activiti 5.15.1
[ https://issues.apache.org/jira/browse/SYNCOPE-485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-485. -- Resolution: Fixed 1_1_X: https://svn.apache.org/viewvc?view=revisionrevision=r1593516 1.2.0: http://svn.apache.org/viewvc?view=revisionrevision=1593543 Upgrade to Activiti 5.15.1 -- Key: SYNCOPE-485 URL: https://issues.apache.org/jira/browse/SYNCOPE-485 Project: Syncope Issue Type: Improvement Reporter: Francesco Chicchiriccò Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.1.8, 1.2.0 Today Activiti 5.15.1 was released [1]: upgrade needed both for branch 1_1_X and trunk: in the latter case additional care must be taken in order to check if modeler is working from admin console. [1] http://bpmn20inaction.blogspot.it/2014/04/activiti-5151-released.html -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (SYNCOPE-444) Remove selfAsRecipient from Notification
[ https://issues.apache.org/jira/browse/SYNCOPE-444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro reassigned SYNCOPE-444: Assignee: Marco Di Sabatino Di Diodoro Remove selfAsRecipient from Notification Key: SYNCOPE-444 URL: https://issues.apache.org/jira/browse/SYNCOPE-444 Project: Syncope Issue Type: Improvement Components: common, console, core Affects Versions: 1.2.0 Reporter: fabio martelli Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.2.0 Notification event targets are not users only: selfAsRecipient have to be removed. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (SYNCOPE-445) Provide a text field to specify whatever notification recipient
[ https://issues.apache.org/jira/browse/SYNCOPE-445?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-445. -- Resolution: Fixed http://svn.apache.org/r1594549 Provide a text field to specify whatever notification recipient --- Key: SYNCOPE-445 URL: https://issues.apache.org/jira/browse/SYNCOPE-445 Project: Syncope Issue Type: Improvement Components: common, console, core Affects Versions: 1.2.0 Reporter: fabio martelli Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.2.0 Provide a text field to specify whatever notification recipient -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SYNCOPE-444) Remove selfAsRecipient from Notification
[ https://issues.apache.org/jira/browse/SYNCOPE-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13999857#comment-13999857 ] Marco Di Sabatino Di Diodoro commented on SYNCOPE-444: -- The selfAsRecipient field can not be removed otherwise it is not possible to notify the “matched About” user. Improved handling of notification recipients. Remove selfAsRecipient from Notification Key: SYNCOPE-444 URL: https://issues.apache.org/jira/browse/SYNCOPE-444 Project: Syncope Issue Type: Improvement Components: common, console, core Affects Versions: 1.2.0 Reporter: fabio martelli Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.2.0 Notification event targets are not users only: selfAsRecipient have to be removed. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (SYNCOPE-444) Remove selfAsRecipient from Notification
[ https://issues.apache.org/jira/browse/SYNCOPE-444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-444. -- Resolution: Fixed Remove selfAsRecipient from Notification Key: SYNCOPE-444 URL: https://issues.apache.org/jira/browse/SYNCOPE-444 Project: Syncope Issue Type: Improvement Components: common, console, core Affects Versions: 1.2.0 Reporter: fabio martelli Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.2.0 Notification event targets are not users only: selfAsRecipient have to be removed. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (SYNCOPE-446) Notification: let admins specify About for roles
[ https://issues.apache.org/jira/browse/SYNCOPE-446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro reassigned SYNCOPE-446: Assignee: Marco Di Sabatino Di Diodoro Notification: let admins specify About for roles -- Key: SYNCOPE-446 URL: https://issues.apache.org/jira/browse/SYNCOPE-446 Project: Syncope Issue Type: Improvement Components: common, console, core Affects Versions: 1.2.0 Reporter: fabio martelli Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.2.0 Currently this is only possible for users. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (SYNCOPE-446) Notification: let admins specify About for roles
[ https://issues.apache.org/jira/browse/SYNCOPE-446?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-446. -- Resolution: Fixed Notification: let admins specify About for roles -- Key: SYNCOPE-446 URL: https://issues.apache.org/jira/browse/SYNCOPE-446 Project: Syncope Issue Type: Improvement Components: common, console, core Affects Versions: 1.2.0 Reporter: fabio martelli Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.2.0 Currently this is only possible for users. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (SYNCOPE-495) List of role(s) assigned to user is deleted in edit user modal page if cancel button of role modal page is clicked
[ https://issues.apache.org/jira/browse/SYNCOPE-495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro reassigned SYNCOPE-495: Assignee: Marco Di Sabatino Di Diodoro List of role(s) assigned to user is deleted in edit user modal page if cancel button of role modal page is clicked -- Key: SYNCOPE-495 URL: https://issues.apache.org/jira/browse/SYNCOPE-495 Project: Syncope Issue Type: Bug Components: console Affects Versions: 1.2.0 Reporter: Andrea Patricelli Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.2.0 Suppose to be logged into console and to open in edit mode a generic user with roles assigned: 1) go under roles tab in edit user modal page 2) click on whatever role (assigned from lower list or not assigned from upper list), a role modal window is shown. 3) click on Cancel or x button to exit from modal page, list of roles assigned to user is incorrectly deleted. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (SYNCOPE-495) List of role(s) assigned to user is deleted in edit user modal page if cancel button of role modal page is clicked
[ https://issues.apache.org/jira/browse/SYNCOPE-495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-495. -- Resolution: Fixed List of role(s) assigned to user is deleted in edit user modal page if cancel button of role modal page is clicked -- Key: SYNCOPE-495 URL: https://issues.apache.org/jira/browse/SYNCOPE-495 Project: Syncope Issue Type: Bug Components: console Affects Versions: 1.2.0 Reporter: Andrea Patricelli Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.2.0 Suppose to be logged into console and to open in edit mode a generic user with roles assigned: 1) go under roles tab in edit user modal page 2) click on whatever role (assigned from lower list or not assigned from upper list), a role modal window is shown. 3) click on Cancel or x button to exit from modal page, list of roles assigned to user is incorrectly deleted. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (SYNCOPE-495) List of role(s) assigned to user is deleted in edit user modal page if cancel button of role modal page is clicked
[ https://issues.apache.org/jira/browse/SYNCOPE-495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-495. -- Resolution: Fixed List of role(s) assigned to user is deleted in edit user modal page if cancel button of role modal page is clicked -- Key: SYNCOPE-495 URL: https://issues.apache.org/jira/browse/SYNCOPE-495 Project: Syncope Issue Type: Bug Components: console Affects Versions: 1.2.0 Reporter: Andrea Patricelli Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.2.0 Suppose to be logged into console and to open in edit mode a generic user with roles assigned: 1) go under roles tab in edit user modal page 2) click on whatever role (assigned from lower list or not assigned from upper list), a role modal window is shown. 3) click on Cancel or x button to exit from modal page, list of roles assigned to user is incorrectly deleted. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (SYNCOPE-497) JEXL Frame positioning error
[ https://issues.apache.org/jira/browse/SYNCOPE-497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro reassigned SYNCOPE-497: Assignee: Marco Di Sabatino Di Diodoro JEXL Frame positioning error Key: SYNCOPE-497 URL: https://issues.apache.org/jira/browse/SYNCOPE-497 Project: Syncope Issue Type: Bug Components: console Reporter: Colm O hEigeartaigh Assignee: Marco Di Sabatino Di Diodoro Priority: Minor Fix For: 1.2.0 Attachments: jexl-error.png There is a problem with a JEXL frame positioning on trunk, where the help message does not appear properly on the screen (see attached png). Steps to reproduce: Tasks - Synchronization Task - Create User template Click on the help for Username. The result is the attached on both firefox and chrome. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (SYNCOPE-497) JEXL Frame positioning error
[ https://issues.apache.org/jira/browse/SYNCOPE-497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-497. -- Resolution: Fixed JEXL Frame positioning error Key: SYNCOPE-497 URL: https://issues.apache.org/jira/browse/SYNCOPE-497 Project: Syncope Issue Type: Bug Components: console Reporter: Colm O hEigeartaigh Assignee: Marco Di Sabatino Di Diodoro Priority: Minor Fix For: 1.2.0 Attachments: jexl-error.png There is a problem with a JEXL frame positioning on trunk, where the help message does not appear properly on the screen (see attached png). Steps to reproduce: Tasks - Synchronization Task - Create User template Click on the help for Username. The result is the attached on both firefox and chrome. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (SYNCOPE-500) Wrong (unwanted) derived attribute insertion addition in membership modal page
[ https://issues.apache.org/jira/browse/SYNCOPE-500?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro reassigned SYNCOPE-500: Assignee: Marco Di Sabatino Di Diodoro Wrong (unwanted) derived attribute insertion addition in membership modal page -- Key: SYNCOPE-500 URL: https://issues.apache.org/jira/browse/SYNCOPE-500 Project: Syncope Issue Type: Bug Components: console Affects Versions: 1.1.8, 1.2.0 Reporter: Andrea Patricelli Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.1.8, 1.2.0 1) Log into console as admin and create or edit user 2) in user modal page go under roles tab and add some membership that has a normal or virtual attribute in its template; for example use role child. 3) in membership modal page go under normal or virtual attributes tab and add an attribute (for example mvirtualdata); select text filed adjacent to attribute name by clicking on it and press enter button once (or several times), then go under derived attributes tab and you'll notice that have been added as many derived attributes as times you pressed enter button. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (SYNCOPE-506) Connector configuration tab in connector modal page does not accept new values
[ https://issues.apache.org/jira/browse/SYNCOPE-506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro reassigned SYNCOPE-506: Assignee: Marco Di Sabatino Di Diodoro Connector configuration tab in connector modal page does not accept new values -- Key: SYNCOPE-506 URL: https://issues.apache.org/jira/browse/SYNCOPE-506 Project: Syncope Issue Type: Bug Components: console Affects Versions: 1.2.0 Reporter: Andrea Patricelli Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.2.0 To reproduce the problem: 1) launch Syncope in embedded mode. 2) log into console and open resources page, then click on connector tab and edit a connector (ApacheDS is a good example). 3) Edit, for example listening, port for connector ApacheDS, edit other fields and save. 4) Open connector just updated and you will notice that values haven't changed and modifications haven't been submitted. Notes: some values are updated during submit, other values (as port number) not. More problematic fields are numeric ones (port number, Change Log Block Size), which are never updated. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (SYNCOPE-391) Make password management optional
[ https://issues.apache.org/jira/browse/SYNCOPE-391?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro reassigned SYNCOPE-391: Assignee: Marco Di Sabatino Di Diodoro Make password management optional - Key: SYNCOPE-391 URL: https://issues.apache.org/jira/browse/SYNCOPE-391 Project: Syncope Issue Type: Improvement Reporter: Francesco Chicchiriccò Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.2.0 Currently, SyncopeUser#password is annotated as @NotNull - this has several consequences to propagation / synchronization and even to admin console. However, it would be a nice addition to make the password storage and management optional - in complex IdM scenarios, in fact, it might even be a business requirement to NOT store passwords in Syncope internal storage. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (SYNCOPE-509) In Task page after change of number of rows (to display) is erroneously added a column to tasks table
[ https://issues.apache.org/jira/browse/SYNCOPE-509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro reassigned SYNCOPE-509: Assignee: Marco Di Sabatino Di Diodoro In Task page after change of number of rows (to display) is erroneously added a column to tasks table - Key: SYNCOPE-509 URL: https://issues.apache.org/jira/browse/SYNCOPE-509 Project: Syncope Issue Type: Bug Components: console Affects Versions: 1.1.8, 1.2.0 Reporter: Andrea Patricelli Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.1.8, 1.2.0 1) Log into console and go under Tasks page. 2) in one of displayed tabs change number of rows to display, you'll notice that a flaggable column is added each time you change value of rows to display, and (if enabled) wicket ajax debug reports an error. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (SYNCOPE-509) In Task page after change of number of rows (to display) is erroneously added a column to tasks table
[ https://issues.apache.org/jira/browse/SYNCOPE-509?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-509. -- Resolution: Fixed In Task page after change of number of rows (to display) is erroneously added a column to tasks table - Key: SYNCOPE-509 URL: https://issues.apache.org/jira/browse/SYNCOPE-509 Project: Syncope Issue Type: Bug Components: console Affects Versions: 1.1.8, 1.2.0 Reporter: Andrea Patricelli Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.1.8, 1.2.0 1) Log into console and go under Tasks page. 2) in one of displayed tabs change number of rows to display, you'll notice that a flaggable column is added each time you change value of rows to display, and (if enabled) wicket ajax debug reports an error. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SYNCOPE-391) Make password management optional
[ https://issues.apache.org/jira/browse/SYNCOPE-391?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14047711#comment-14047711 ] Marco Di Sabatino Di Diodoro commented on SYNCOPE-391: -- Propagation: the propagation of the password to the resource is determined by the configuration of the password policy, in particular if there exists at least a password policy that says to store the password, Syncope must store it inside the repository. Sync: if you don't need to store the password in the internal repository, Syncope should not create the generated password. Make password management optional - Key: SYNCOPE-391 URL: https://issues.apache.org/jira/browse/SYNCOPE-391 Project: Syncope Issue Type: Improvement Reporter: Francesco Chicchiriccò Assignee: Andrea Patricelli Fix For: 1.2.0 Currently, SyncopeUser#password is annotated as @NotNull - this has several consequences to propagation / synchronization and even to admin console. However, it would be a nice addition to make the password storage and management optional - in complex IdM scenarios, in fact, it might even be a business requirement to NOT store passwords in Syncope internal storage. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (SYNCOPE-527) Stacktrace on BulkAction result
[ https://issues.apache.org/jira/browse/SYNCOPE-527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro reassigned SYNCOPE-527: Assignee: Marco Di Sabatino Di Diodoro Stacktrace on BulkAction result --- Key: SYNCOPE-527 URL: https://issues.apache.org/jira/browse/SYNCOPE-527 Project: Syncope Issue Type: Bug Components: console Reporter: Francesco Chicchiriccò Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.2.0 Steps to reproduce: # create an user # select on the user list # click the bulk action icon on the lower left side # click the delete icon on the modal window -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (SYNCOPE-537) Upgrade to ConnId 1.4.0.0
[ https://issues.apache.org/jira/browse/SYNCOPE-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro reassigned SYNCOPE-537: Assignee: Marco Di Sabatino Di Diodoro Upgrade to ConnId 1.4.0.0 - Key: SYNCOPE-537 URL: https://issues.apache.org/jira/browse/SYNCOPE-537 Project: Syncope Issue Type: Task Components: build-tools, core Reporter: Francesco Chicchiriccò Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.3.0 Attachments: ConnId_1_4_0_0.initial.patch ConnId 1.4.0.0 has been released [1]. One of the most noticeable features is the full compatibility with OpenICF 1.4.0.0, which makes available to Syncope all OpenICF connectors [2]. [1] http://www.tirasa.net/news/connid-1.4.0.0-released.html [2] http://openicf.forgerock.org/connectors/index.html -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (SYNCOPE-537) Upgrade to ConnId 1.4.0.0
[ https://issues.apache.org/jira/browse/SYNCOPE-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-537. -- Resolution: Fixed Upgrade to ConnId 1.4.0.0 - Key: SYNCOPE-537 URL: https://issues.apache.org/jira/browse/SYNCOPE-537 Project: Syncope Issue Type: Task Components: build-tools, core Reporter: Francesco Chicchiriccò Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.2.0, 1.3.0 Attachments: ConnId_1_4_0_0.initial.patch ConnId 1.4.0.0 has been released [1]. One of the most noticeable features is the full compatibility with OpenICF 1.4.0.0, which makes available to Syncope all OpenICF connectors [2]. [1] http://www.tirasa.net/news/connid-1.4.0.0-released.html [2] http://openicf.forgerock.org/connectors/index.html -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (SYNCOPE-539) Edit user with resources causes Ajax failure
[
https://issues.apache.org/jira/browse/SYNCOPE-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Di Sabatino Di Diodoro reassigned SYNCOPE-539:
Assignee: Marco Di Sabatino Di Diodoro
Edit user with resources causes Ajax failure
Key: SYNCOPE-539
URL: https://issues.apache.org/jira/browse/SYNCOPE-539
Project: Syncope
Issue Type: Bug
Components: console
Affects Versions: 1.2.0
Reporter: Francesco Chicchiriccò
Assignee: Marco Di Sabatino Di Diodoro
Fix For: 1.2.0, 1.3.0
Steps to reproduce on the admin console:
# create an user with a resource assigned (say {{resource-testdb}} from test
data)
# edit the created user by changing one of attributes
# the Ajax debug will show an error
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Resolved] (SYNCOPE-543) Role's Inherit Attributes does not inherit from parent role for check box attribute
[ https://issues.apache.org/jira/browse/SYNCOPE-543?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-543. -- Resolution: Fixed Role's Inherit Attributes does not inherit from parent role for check box attribute - Key: SYNCOPE-543 URL: https://issues.apache.org/jira/browse/SYNCOPE-543 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.1.8, 1.2.0-M1, 1.3.0 Reporter: Stefan Auw Yang Assignee: Marco Di Sabatino Di Diodoro Priority: Minor Fix For: 1.1.9, 1.2.0-M1, 1.3.0 Even though inherit Attributes flag is checked, there is no way to set the child role's check box attribute (which defined with boolean type in schema) to inherit the value from parent. Is this considered as expected behavior? Is there actually any way to archive this? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (SYNCOPE-553) Internal Server Error when creating account policy
[
https://issues.apache.org/jira/browse/SYNCOPE-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Di Sabatino Di Diodoro reassigned SYNCOPE-553:
Assignee: Marco Di Sabatino Di Diodoro
Internal Server Error when creating account policy
--
Key: SYNCOPE-553
URL: https://issues.apache.org/jira/browse/SYNCOPE-553
Project: Syncope
Issue Type: Bug
Affects Versions: 1.2.0-M1
Reporter: Francesco Chicchiriccò
Assignee: Marco Di Sabatino Di Diodoro
Fix For: 1.2.0, 1.3.0
When creating an account policy from the admin console, an exception is
raised on the core:
{code}
java.lang.NullPointerException
at
org.apache.syncope.core.rest.data.PolicyDataBinder.getPolicy(PolicyDataBinder.java:173)
~[PolicyDataBinder.class:?]
at
org.apache.syncope.core.rest.controller.PolicyController.create(PolicyController.java:57)
~[PolicyController.class:?]
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (SYNCOPE-556) Error in the enum schema when trying to add new enumeration value/label
Marco Di Sabatino Di Diodoro created SYNCOPE-556: Summary: Error in the enum schema when trying to add new enumeration value/label Key: SYNCOPE-556 URL: https://issues.apache.org/jira/browse/SYNCOPE-556 Project: Syncope Issue Type: Bug Components: console Affects Versions: 1.2.0-M1 Reporter: Marco Di Sabatino Di Diodoro Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.2.0, 1.3.0 When trying to add a new enumeration in the enum schema, all previous values are cleared. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SYNCOPE-556) Error in the enum schema when trying to add new enumeration value/label
[ https://issues.apache.org/jira/browse/SYNCOPE-556?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-556. -- Resolution: Fixed Error in the enum schema when trying to add new enumeration value/label --- Key: SYNCOPE-556 URL: https://issues.apache.org/jira/browse/SYNCOPE-556 Project: Syncope Issue Type: Bug Components: console Affects Versions: 1.2.0-M1 Reporter: Marco Di Sabatino Di Diodoro Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.2.0, 1.3.0 When trying to add a new enumeration in the enum schema, all previous values are cleared. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (SYNCOPE-558) Ability to configure which user, role and membership attributes to display, and in which order
[ https://issues.apache.org/jira/browse/SYNCOPE-558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro reassigned SYNCOPE-558: Assignee: Marco Di Sabatino Di Diodoro Ability to configure which user, role and membership attributes to display, and in which order -- Key: SYNCOPE-558 URL: https://issues.apache.org/jira/browse/SYNCOPE-558 Project: Syncope Issue Type: New Feature Components: console Reporter: Francesco Chicchiriccò Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.2.1 Currently the admin console barely displays all defined user, role and membership attributes, in alphabetical order. This can be enhanced by providing a mean to configure which attributes, and in which order, should be displayed by admin console forms either for administration and self-management purpose. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SYNCOPE-562) Duplicated configuration parameters in the CATTR table
Marco Di Sabatino Di Diodoro created SYNCOPE-562: Summary: Duplicated configuration parameters in the CATTR table Key: SYNCOPE-562 URL: https://issues.apache.org/jira/browse/SYNCOPE-562 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.2.0 Reporter: Marco Di Sabatino Di Diodoro Fix For: 1.2.1, 1.3.0 When updating configuration parameters, in the CATTR table the entries are duplicated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SYNCOPE-565) Error on ResourceModalPage when override a SpinnerField in the ConnectorModalPage
Marco Di Sabatino Di Diodoro created SYNCOPE-565: Summary: Error on ResourceModalPage when override a SpinnerField in the ConnectorModalPage Key: SYNCOPE-565 URL: https://issues.apache.org/jira/browse/SYNCOPE-565 Project: Syncope Issue Type: Bug Components: console Affects Versions: 1.2.0 Reporter: Marco Di Sabatino Di Diodoro Fix For: 1.2.1, 1.3.0 Class cast exception on ResourceModalPage when override a SpinnerField in the ConnectorModalPage. java.lang.ClassCastException: Cannot cast java.lang.Double to int at java.lang.Class.cast(Class.java:3005) at org.apache.syncope.console.wicket.markup.html.form.SpinnerFieldPanel$2.getObject(SpinnerFieldPanel.java:109) at org.apache.syncope.console.wicket.markup.html.form.SpinnerFieldPanel$2.getObject(SpinnerFieldPanel.java:100) at org.apache.wicket.Component.getDefaultModelObject(Component.java:1590) at org.apache.wicket.Component.getDefaultModelObjectAsString(Component.java:1618) at org.apache.wicket.markup.html.form.FormComponent.getModelValue(FormComponent.java:1291) at org.apache.wicket.markup.html.form.FormComponent.getValue(FormComponent.java:878) at org.apache.wicket.markup.html.form.TextField.onComponentTag(TextField.java:108) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SYNCOPE-569) The user status is not propagated on the resources
Marco Di Sabatino Di Diodoro created SYNCOPE-569: Summary: The user status is not propagated on the resources Key: SYNCOPE-569 URL: https://issues.apache.org/jira/browse/SYNCOPE-569 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.2.0 Reporter: Marco Di Sabatino Di Diodoro Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.2.1, 1.3.0 It seems that during propagation on resources, the user status is not propagated. The problem seems to be the definition of the workflow. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SYNCOPE-569) The user status is not propagated on the resources
[ https://issues.apache.org/jira/browse/SYNCOPE-569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-569. -- Resolution: Fixed The user status is not propagated on the resources -- Key: SYNCOPE-569 URL: https://issues.apache.org/jira/browse/SYNCOPE-569 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.2.0 Reporter: Marco Di Sabatino Di Diodoro Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.2.1, 1.3.0 It seems that during propagation on resources, the user status is not propagated. The problem seems to be the definition of the workflow. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SYNCOPE-597) Error when serializating SyncToken with byte array type during sync task from Active Directory
Marco Di Sabatino Di Diodoro created SYNCOPE-597: Summary: Error when serializating SyncToken with byte array type during sync task from Active Directory Key: SYNCOPE-597 URL: https://issues.apache.org/jira/browse/SYNCOPE-597 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.2.0 Reporter: Marco Di Sabatino Di Diodoro Fix For: 1.2.1, 1.3.0 During the sync task from Active Directory, Syncope not stores properly the sync token. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (SYNCOPE-597) Error when serializating SyncToken with byte array type during sync task from Active Directory
[ https://issues.apache.org/jira/browse/SYNCOPE-597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro reassigned SYNCOPE-597: Assignee: Marco Di Sabatino Di Diodoro Error when serializating SyncToken with byte array type during sync task from Active Directory -- Key: SYNCOPE-597 URL: https://issues.apache.org/jira/browse/SYNCOPE-597 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.2.0 Reporter: Marco Di Sabatino Di Diodoro Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.2.1, 1.3.0 During the sync task from Active Directory, Syncope not stores properly the sync token. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (SYNCOPE-601) AD deleted object synchronization fails if a sync policy is specified on one or more attributes that can have no values on Syncope
[ https://issues.apache.org/jira/browse/SYNCOPE-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro reassigned SYNCOPE-601: Assignee: Marco Di Sabatino Di Diodoro AD deleted object synchronization fails if a sync policy is specified on one or more attributes that can have no values on Syncope -- Key: SYNCOPE-601 URL: https://issues.apache.org/jira/browse/SYNCOPE-601 Project: Syncope Issue Type: Bug Affects Versions: 1.1.8, 1.2.0 Reporter: fabio martelli Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.1.9, 1.2.1, 1.3.0 During AD synchronization (via ConnID AD - JNDI - connector bundle) returned connector objects about deleted objects don't have any profile attribute specified (see https://connid.atlassian.net/browse/AD-36). If a sync posicy is specified to perform a correlation among one or more internal profile attributes, the first user with no values about that attribute will match this correlation rule and maybe removed. The query has to be changed in order to avoid this behavior (for delteted object and creted-updated): 1. if one or more connector object attributes related to the correlation rule don't exist avoid the query execution ... no match 2. if all the connector object attributes related to the correlation rule exist then perform the query as is -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SYNCOPE-601) AD deleted object synchronization fails if a sync policy is specified on one or more attributes that can have no values on Syncope
[ https://issues.apache.org/jira/browse/SYNCOPE-601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-601. -- Resolution: Fixed AD deleted object synchronization fails if a sync policy is specified on one or more attributes that can have no values on Syncope -- Key: SYNCOPE-601 URL: https://issues.apache.org/jira/browse/SYNCOPE-601 Project: Syncope Issue Type: Bug Affects Versions: 1.1.8, 1.2.0 Reporter: fabio martelli Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.1.9, 1.2.1, 1.3.0 During AD synchronization (via ConnID AD - JNDI - connector bundle) returned connector objects about deleted objects don't have any profile attribute specified (see https://connid.atlassian.net/browse/AD-36). If a sync posicy is specified to perform a correlation among one or more internal profile attributes, the first user with no values about that attribute will match this correlation rule and maybe removed. The query has to be changed in order to avoid this behavior (for delteted object and creted-updated): 1. if one or more connector object attributes related to the correlation rule don't exist avoid the query execution ... no match 2. if all the connector object attributes related to the correlation rule exist then perform the query as is -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SYNCOPE-605) Impossible to update the connector capabilities
Marco Di Sabatino Di Diodoro created SYNCOPE-605: Summary: Impossible to update the connector capabilities Key: SYNCOPE-605 URL: https://issues.apache.org/jira/browse/SYNCOPE-605 Project: Syncope Issue Type: Bug Components: console, core Affects Versions: 1.2.1 Reporter: Marco Di Sabatino Di Diodoro Fix For: 1.2.1, 1.3.0 If you try to change (edit mode) the capabilities of the connector, Syncope does not save changes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (SYNCOPE-605) Impossible to update the connector capabilities
[ https://issues.apache.org/jira/browse/SYNCOPE-605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro reassigned SYNCOPE-605: Assignee: Marco Di Sabatino Di Diodoro Impossible to update the connector capabilities --- Key: SYNCOPE-605 URL: https://issues.apache.org/jira/browse/SYNCOPE-605 Project: Syncope Issue Type: Bug Components: console, core Affects Versions: 1.2.1 Reporter: Marco Di Sabatino Di Diodoro Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.2.1, 1.3.0 If you try to change (edit mode) the capabilities of the connector, Syncope does not save changes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SYNCOPE-605) Impossible to update the connector capabilities
[ https://issues.apache.org/jira/browse/SYNCOPE-605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-605. -- Resolution: Fixed Impossible to update the connector capabilities --- Key: SYNCOPE-605 URL: https://issues.apache.org/jira/browse/SYNCOPE-605 Project: Syncope Issue Type: Bug Components: console, core Affects Versions: 1.2.1 Reporter: Marco Di Sabatino Di Diodoro Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.2.1, 1.3.0 If you try to change (edit mode) the capabilities of the connector, Syncope does not save changes. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SYNCOPE-607) Error when adding a value to a multivalue configuration parameter of type long
Marco Di Sabatino Di Diodoro created SYNCOPE-607: Summary: Error when adding a value to a multivalue configuration parameter of type long Key: SYNCOPE-607 URL: https://issues.apache.org/jira/browse/SYNCOPE-607 Project: Syncope Issue Type: Bug Components: console Affects Versions: 1.2.1 Reporter: Marco Di Sabatino Di Diodoro Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.2.2, 1.3.0 Create new multivalue configuration schema of type Long. Try to add a value to the new schema from the console. Console return a class cast exception. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (SYNCOPE-608) Cannot configure audit for AuthenticationController
[
https://issues.apache.org/jira/browse/SYNCOPE-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Di Sabatino Di Diodoro reassigned SYNCOPE-608:
Assignee: Marco Di Sabatino Di Diodoro
Cannot configure audit for AuthenticationController
---
Key: SYNCOPE-608
URL: https://issues.apache.org/jira/browse/SYNCOPE-608
Project: Syncope
Issue Type: Bug
Components: console
Affects Versions: 1.2.0
Reporter: Francesco Chicchiriccò
Assignee: Marco Di Sabatino Di Diodoro
Fix For: 1.2.2, 1.3.0
The admin console does not allow to configure audit for Authentication
controller, required for auditing login success / failure.
This is possible via REST call, of course:
{code}
String name =
[REST]:[AuthenticationController]:[]:[login]:[SUCCESS];
LoggerTO loggerTO = new LoggerTO();
loggerTO.setName(name);
loggerTO.setLevel(LoggerLevel.DEBUG);
getService(LoggerService.class).update(LoggerType.AUDIT, name,
loggerTO);
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (SYNCOPE-608) Cannot configure audit for AuthenticationController
[
https://issues.apache.org/jira/browse/SYNCOPE-608?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Di Sabatino Di Diodoro resolved SYNCOPE-608.
--
Resolution: Fixed
Cannot configure audit for AuthenticationController
---
Key: SYNCOPE-608
URL: https://issues.apache.org/jira/browse/SYNCOPE-608
Project: Syncope
Issue Type: Bug
Components: console
Affects Versions: 1.2.0
Reporter: Francesco Chicchiriccò
Assignee: Marco Di Sabatino Di Diodoro
Fix For: 1.2.2, 1.3.0
The admin console does not allow to configure audit for Authentication
controller, required for auditing login success / failure.
This is possible via REST call, of course:
{code}
String name =
[REST]:[AuthenticationController]:[]:[login]:[SUCCESS];
LoggerTO loggerTO = new LoggerTO();
loggerTO.setName(name);
loggerTO.setLevel(LoggerLevel.DEBUG);
getService(LoggerService.class).update(LoggerType.AUDIT, name,
loggerTO);
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (SYNCOPE-607) Error when adding a value to a multivalue configuration parameter of type long
[ https://issues.apache.org/jira/browse/SYNCOPE-607?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-607. -- Resolution: Fixed Error when adding a value to a multivalue configuration parameter of type long -- Key: SYNCOPE-607 URL: https://issues.apache.org/jira/browse/SYNCOPE-607 Project: Syncope Issue Type: Bug Components: console Affects Versions: 1.2.1 Reporter: Marco Di Sabatino Di Diodoro Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.2.2, 1.3.0 Create new multivalue configuration schema of type Long. Try to add a value to the new schema from the console. Console return a class cast exception. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SYNCOPE-611) An approver display all approval tasks including those not assigned to him
Marco Di Sabatino Di Diodoro created SYNCOPE-611: Summary: An approver display all approval tasks including those not assigned to him Key: SYNCOPE-611 URL: https://issues.apache.org/jira/browse/SYNCOPE-611 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.2.1 Reporter: Marco Di Sabatino Di Diodoro Fix For: 1.2.2, 1.3.0 Currently an approvers display all approval tasks. If an approver tries to claim a task which is not a candidate, Syncope return an exception. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SYNCOPE-611) An approver displays all approval tasks including those not assigned to him
[ https://issues.apache.org/jira/browse/SYNCOPE-611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro updated SYNCOPE-611: - Summary: An approver displays all approval tasks including those not assigned to him (was: An approver display all approval tasks including those not assigned to him) An approver displays all approval tasks including those not assigned to him --- Key: SYNCOPE-611 URL: https://issues.apache.org/jira/browse/SYNCOPE-611 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.2.1 Reporter: Marco Di Sabatino Di Diodoro Fix For: 1.2.2, 1.3.0 Currently an approvers display all approval tasks. If an approver tries to claim a task which is not a candidate, Syncope return an exception. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SYNCOPE-611) An approver displays all approval tasks including those not assigned to him
[ https://issues.apache.org/jira/browse/SYNCOPE-611?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro updated SYNCOPE-611: - Description: Currently an approver display all approval tasks. If an approver tries to claim a task which is not a candidate, Syncope returns an exception. (was: Currently an approvers display all approval tasks. If an approver tries to claim a task which is not a candidate, Syncope return an exception.) An approver displays all approval tasks including those not assigned to him --- Key: SYNCOPE-611 URL: https://issues.apache.org/jira/browse/SYNCOPE-611 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.2.1 Reporter: Marco Di Sabatino Di Diodoro Fix For: 1.2.2, 1.3.0 Currently an approver display all approval tasks. If an approver tries to claim a task which is not a candidate, Syncope returns an exception. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SYNCOPE-613) delete overridable connector configuration property of type array String in resource edit panel
[ https://issues.apache.org/jira/browse/SYNCOPE-613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-613. -- Resolution: Fixed delete overridable connector configuration property of type array String in resource edit panel --- Key: SYNCOPE-613 URL: https://issues.apache.org/jira/browse/SYNCOPE-613 Project: Syncope Issue Type: Bug Components: console Affects Versions: 1.2.1 Reporter: Nicola Baiocco Assignee: Marco Di Sabatino Di Diodoro Priority: Minor Fix For: 1.2.2, 1.3.0 Steps to reproduce: 1) create AD connector with all configuration values overridable; 2) create AD resource that uses AD connector; 3) populate connector conf property of type array String (eg. memberships) with one or more values; 4) save; 5) remove all values from previous connector conf property; 6) save; not all values have been removed. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SYNCOPE-615) Updating properties and xml files of the installer module with the current version
Marco Di Sabatino Di Diodoro created SYNCOPE-615: Summary: Updating properties and xml files of the installer module with the current version Key: SYNCOPE-615 URL: https://issues.apache.org/jira/browse/SYNCOPE-615 Project: Syncope Issue Type: Bug Components: installer Affects Versions: 1.2.2 Reporter: Marco Di Sabatino Di Diodoro Priority: Critical Fix For: 1.2.2, 1.3.0 There are embedded xml and properties files that have not been updated to the new features and bug fixes of Apache Syncope. For example, in the OrmXML.java file the entity class=org.apache.syncope.core.persistence.beans.SecurityQuestion attributes id name=id generated-value generator=SEQ_SecurityQuestion strategy=TABLE/ table-generator name=SEQ_SecurityQuestion pk-column-value=SEQ_SecurityQuestion initial-value=100/ /id /attributes /entity is missing. Take a look at https://git-wip-us.apache.org/repos/asf?p=syncope.git;a=blob;f=core/src/main/resources/META-INF/orm.xml;h=3dad2b5a26fa9b12af39461a89a7d21cda11fdb4;hb=HEAD -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SYNCOPE-616) Improving the management of the xml and properties files inside the installer
Marco Di Sabatino Di Diodoro created SYNCOPE-616: Summary: Improving the management of the xml and properties files inside the installer Key: SYNCOPE-616 URL: https://issues.apache.org/jira/browse/SYNCOPE-616 Project: Syncope Issue Type: Improvement Components: installer Affects Versions: 1.2.2 Reporter: Marco Di Sabatino Di Diodoro Fix For: 1.2.2, 1.3.0 Currently the installer doesn't read the xml and properties files inside the core and console modules, but are embedded statically into java classes causing the following errors in syncope (SYNCOPE-615). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (SYNCOPE-615) Updating properties and xml files of the installer module with the current version
[ https://issues.apache.org/jira/browse/SYNCOPE-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro reassigned SYNCOPE-615: Assignee: Marco Di Sabatino Di Diodoro Updating properties and xml files of the installer module with the current version -- Key: SYNCOPE-615 URL: https://issues.apache.org/jira/browse/SYNCOPE-615 Project: Syncope Issue Type: Bug Components: installer Affects Versions: 1.2.2 Reporter: Marco Di Sabatino Di Diodoro Assignee: Marco Di Sabatino Di Diodoro Priority: Critical Fix For: 1.2.2, 1.3.0 There are embedded xml and properties files that have not been updated to the new features and bug fixes of Apache Syncope. For example, in the OrmXML.java file the entity class=org.apache.syncope.core.persistence.beans.SecurityQuestion attributes id name=id generated-value generator=SEQ_SecurityQuestion strategy=TABLE/ table-generator name=SEQ_SecurityQuestion pk-column-value=SEQ_SecurityQuestion initial-value=100/ /id /attributes /entity is missing. Take a look at https://git-wip-us.apache.org/repos/asf?p=syncope.git;a=blob;f=core/src/main/resources/META-INF/orm.xml;h=3dad2b5a26fa9b12af39461a89a7d21cda11fdb4;hb=HEAD -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SYNCOPE-615) Updating properties and xml files of the installer module with the current version
[ https://issues.apache.org/jira/browse/SYNCOPE-615?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-615. -- Resolution: Fixed Updating properties and xml files of the installer module with the current version -- Key: SYNCOPE-615 URL: https://issues.apache.org/jira/browse/SYNCOPE-615 Project: Syncope Issue Type: Bug Components: installer Affects Versions: 1.2.2 Reporter: Marco Di Sabatino Di Diodoro Assignee: Marco Di Sabatino Di Diodoro Priority: Critical Fix For: 1.2.2, 1.3.0 There are embedded xml and properties files that have not been updated to the new features and bug fixes of Apache Syncope. For example, in the OrmXML.java file the entity class=org.apache.syncope.core.persistence.beans.SecurityQuestion attributes id name=id generated-value generator=SEQ_SecurityQuestion strategy=TABLE/ table-generator name=SEQ_SecurityQuestion pk-column-value=SEQ_SecurityQuestion initial-value=100/ /id /attributes /entity is missing. Take a look at https://git-wip-us.apache.org/repos/asf?p=syncope.git;a=blob;f=core/src/main/resources/META-INF/orm.xml;h=3dad2b5a26fa9b12af39461a89a7d21cda11fdb4;hb=HEAD -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SYNCOPE-610) Installer doesn't update the console.properties with the container port
[ https://issues.apache.org/jira/browse/SYNCOPE-610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-610. -- Resolution: Fixed https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=5e013aa Installer doesn't update the console.properties with the container port --- Key: SYNCOPE-610 URL: https://issues.apache.org/jira/browse/SYNCOPE-610 Project: Syncope Issue Type: Bug Components: installer Affects Versions: 1.2.1 Reporter: Colm O hEigeartaigh Assignee: Marco Di Sabatino Di Diodoro Priority: Minor Fix For: 1.2.2, 1.3.0 When installing Syncope via the installer to Tomcat, if you change the port it isn't reflected in the resulting syncope-console/WEB-INF/classes/console.properties. Possibly the host needs to be changed as well as part of this. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SYNCOPE-616) Improving the management of the xml and properties files inside the installer
[ https://issues.apache.org/jira/browse/SYNCOPE-616?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-616. -- Resolution: Fixed Improving the management of the xml and properties files inside the installer - Key: SYNCOPE-616 URL: https://issues.apache.org/jira/browse/SYNCOPE-616 Project: Syncope Issue Type: Improvement Components: installer Affects Versions: 1.2.2 Reporter: Marco Di Sabatino Di Diodoro Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.2.2, 1.3.0 Currently the installer doesn't read the xml and properties files inside the core and console modules, but are embedded statically into java classes causing the following errors in syncope (SYNCOPE-615). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SYNCOPE-645) Provide validation error message when add a role attribute in a user mapping as accountId
[ https://issues.apache.org/jira/browse/SYNCOPE-645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-645. -- Resolution: Fixed Provide validation error message when add a role attribute in a user mapping as accountId - Key: SYNCOPE-645 URL: https://issues.apache.org/jira/browse/SYNCOPE-645 Project: Syncope Issue Type: Improvement Components: core Affects Versions: 1.1.8, 1.2.2 Reporter: Marco Di Sabatino Di Diodoro Assignee: Marco Di Sabatino Di Diodoro Priority: Critical Fix For: 1.1.9, 1.2.3, 2.0.0 Is not possibile to use a role attribute in a user mapping of an resource such as accountId. Provide validation error when add a role attribute in the user mapping as accountId. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SYNCOPE-625) Build fails with Java 6
[
https://issues.apache.org/jira/browse/SYNCOPE-625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Di Sabatino Di Diodoro resolved SYNCOPE-625.
--
Resolution: Fixed
Build fails with Java 6
---
Key: SYNCOPE-625
URL: https://issues.apache.org/jira/browse/SYNCOPE-625
Project: Syncope
Issue Type: Bug
Components: installer
Reporter: Francesco Chicchiriccò
Assignee: Marco Di Sabatino Di Diodoro
Priority: Critical
Fix For: 1.2.2, 1.3.0
[Latest
improvements|https://git-wip-us.apache.org/repos/asf?p=syncope.git;h=20bfa94]
on installer made use of package {{java.nio.file}}, not available with JDK
1.6.
As a consequence, the build process fails with Java 6.
{code}
14:58:38 [ERROR] COMPILATION ERROR :
14:58:38 [INFO] -
14:58:38 [ERROR] /home/jenkins/workspace/Apache Syncope
master/installer/src/main/java/org/apache/syncope/installer/utilities/FileSystemUtils.java:[33,21]
package java.nio.file does not exist
14:58:38 [ERROR] /home/jenkins/workspace/Apache Syncope
master/installer/src/main/java/org/apache/syncope/installer/utilities/FileSystemUtils.java:[34,21]
package java.nio.file does not exist
14:58:38 [ERROR] /home/jenkins/workspace/Apache Syncope
master/installer/src/main/java/org/apache/syncope/installer/utilities/FileSystemUtils.java:[35,21]
package java.nio.file does not exist
14:58:38 [ERROR] /home/jenkins/workspace/Apache Syncope
master/installer/src/main/java/org/apache/syncope/installer/utilities/FileSystemUtils.java:[36,21]
package java.nio.file does not exist
14:58:38 [ERROR] /home/jenkins/workspace/Apache Syncope
master/installer/src/main/java/org/apache/syncope/installer/utilities/FileSystemUtils.java:[64,19]
cannot find symbol
{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (SYNCOPE-648) Notification Configuration: missing some labels in events
[ https://issues.apache.org/jira/browse/SYNCOPE-648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro updated SYNCOPE-648: - Component/s: (was: console) core Notification Configuration: missing some labels in events - Key: SYNCOPE-648 URL: https://issues.apache.org/jira/browse/SYNCOPE-648 Project: Syncope Issue Type: Improvement Components: core Affects Versions: 1.2.2 Reporter: Nicola Baiocco Assignee: Marco Di Sabatino Di Diodoro Priority: Minor Fix For: 1.2.3, 2.0.0 Sync process include many operations for example “create”,”assign”,”link”,”unlink”, etc… but into notification configuration we find only “create”,”update”,”delete”,”none”. How to intercept a failure/success during “assing”, or during an operation different from [“create”,”update”,”delete”,”none”]? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SYNCOPE-648) Notification Configuration: missing some labels in events
[ https://issues.apache.org/jira/browse/SYNCOPE-648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-648. -- Resolution: Fixed Notification Configuration: missing some labels in events - Key: SYNCOPE-648 URL: https://issues.apache.org/jira/browse/SYNCOPE-648 Project: Syncope Issue Type: Improvement Components: core Affects Versions: 1.2.2 Reporter: Nicola Baiocco Assignee: Marco Di Sabatino Di Diodoro Priority: Minor Fix For: 1.2.3, 2.0.0 Sync process include many operations for example “create”,”assign”,”link”,”unlink”, etc… but into notification configuration we find only “create”,”update”,”delete”,”none”. How to intercept a failure/success during “assing”, or during an operation different from [“create”,”update”,”delete”,”none”]? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SYNCOPE-647) Problem during propagation of an updated membership on a resource
Marco Di Sabatino Di Diodoro created SYNCOPE-647: Summary: Problem during propagation of an updated membership on a resource Key: SYNCOPE-647 URL: https://issues.apache.org/jira/browse/SYNCOPE-647 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.2.2 Reporter: Marco Di Sabatino Di Diodoro Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.2.3, 2.0.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SYNCOPE-647) Problem during propagation of an updated membership on a resource
[ https://issues.apache.org/jira/browse/SYNCOPE-647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro updated SYNCOPE-647: - Description: Apache Syncope doesn't propagate on a resource if the only attributes that change are Membership. Problem during propagation of an updated membership on a resource -- Key: SYNCOPE-647 URL: https://issues.apache.org/jira/browse/SYNCOPE-647 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.2.2 Reporter: Marco Di Sabatino Di Diodoro Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.2.3, 2.0.0 Apache Syncope doesn't propagate on a resource if the only attributes that change are Membership. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SYNCOPE-658) Duplicate derived attribute after sync task when it is configured as accountid for the synched resource
[ https://issues.apache.org/jira/browse/SYNCOPE-658?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-658. -- Resolution: Fixed Duplicate derived attribute after sync task when it is configured as accountid for the synched resource --- Key: SYNCOPE-658 URL: https://issues.apache.org/jira/browse/SYNCOPE-658 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.2.3 Reporter: Marco Di Sabatino Di Diodoro Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.2.4, 2.0.0 The synchronization from a resource which has a derived attribute as accountId, produces a duplicate for this attribute in Syncope. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (SYNCOPE-658) Duplicate derived attribute after sync task when it is configured as accountid for the synched resource
[ https://issues.apache.org/jira/browse/SYNCOPE-658?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14492545#comment-14492545 ] Marco Di Sabatino Di Diodoro edited comment on SYNCOPE-658 at 4/13/15 4:01 PM: --- Tests failures on Syncope: https://connid.atlassian.net/browse/DB-11 was (Author: mdisabatino): Rehttps://connid.atlassian.net/browse/DB-11 Duplicate derived attribute after sync task when it is configured as accountid for the synched resource --- Key: SYNCOPE-658 URL: https://issues.apache.org/jira/browse/SYNCOPE-658 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.2.3 Reporter: Marco Di Sabatino Di Diodoro Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.2.4, 2.0.0 The synchronization from a resource which has a derived attribute as accountId, produces a duplicate for this attribute in Syncope. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SYNCOPE-669) Search filter in the notifications doesn't work properly
[ https://issues.apache.org/jira/browse/SYNCOPE-669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-669. -- Resolution: Fixed Search filter in the notifications doesn't work properly Key: SYNCOPE-669 URL: https://issues.apache.org/jira/browse/SYNCOPE-669 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.2.4 Reporter: Marco Di Sabatino Di Diodoro Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.2.5, 2.0.0 Configure a notification with a creation event and add a user filter. For example: [REST]:[UserController]:[]:[create]:[SUCCESS] with Username == xx Create from the console an user that should be excluded from the filter. Syncope creates a notification task. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SYNCOPE-672) Console doesn't display the right condition when configuring a search filter with a resource
[ https://issues.apache.org/jira/browse/SYNCOPE-672?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-672. -- Resolution: Fixed Console doesn't display the right condition when configuring a search filter with a resource Key: SYNCOPE-672 URL: https://issues.apache.org/jira/browse/SYNCOPE-672 Project: Syncope Issue Type: Bug Components: console Affects Versions: 1.2.4 Reporter: Marco Di Sabatino Di Diodoro Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.2.5, 2.0.0 SearchView doesn't display the correct condtion when configure a search filter that use a resource as comparator. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SYNCOPE-672) Console doesn't display the right condition when configuring a search filter with a resource
Marco Di Sabatino Di Diodoro created SYNCOPE-672: Summary: Console doesn't display the right condition when configuring a search filter with a resource Key: SYNCOPE-672 URL: https://issues.apache.org/jira/browse/SYNCOPE-672 Project: Syncope Issue Type: Bug Components: console Affects Versions: 1.2.4 Reporter: Marco Di Sabatino Di Diodoro Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.2.5, 2.0.0 SearchView doesn't display the correct condtion when configure a search filter that use a resource as comparator. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (SYNCOPE-669) Search filter in the notifications doesn't work properly
[ https://issues.apache.org/jira/browse/SYNCOPE-669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro reassigned SYNCOPE-669: Assignee: Marco Di Sabatino Di Diodoro Search filter in the notifications doesn't work properly Key: SYNCOPE-669 URL: https://issues.apache.org/jira/browse/SYNCOPE-669 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.2.4 Reporter: Marco Di Sabatino Di Diodoro Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.2.5, 2.0.0 Configure a notification with a creation event and add a user filter. For example: [REST]:[UserController]:[]:[create]:[SUCCESS] with Username == xx Create from the console an user that should be excluded from the filter. Syncope creates a notification task. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SYNCOPE-714) Add the possibility to override the capabilities of the connector
Marco Di Sabatino Di Diodoro created SYNCOPE-714: Summary: Add the possibility to override the capabilities of the connector Key: SYNCOPE-714 URL: https://issues.apache.org/jira/browse/SYNCOPE-714 Project: Syncope Issue Type: Improvement Components: console, core Affects Versions: 1.2.5 Reporter: Marco Di Sabatino Di Diodoro Priority: Minor Fix For: 2.0.0 Currently, in the resource configuration you can override only the connector instance properties. It would be useful to extend this behaviour to the connector capabilities. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SYNCOPE-712) Error while searching roles by parent
Marco Di Sabatino Di Diodoro created SYNCOPE-712:
Summary: Error while searching roles by parent
Key: SYNCOPE-712
URL: https://issues.apache.org/jira/browse/SYNCOPE-712
Project: Syncope
Issue Type: Bug
Components: core
Affects Versions: 1.2.5
Reporter: Marco Di Sabatino Di Diodoro
Assignee: Marco Di Sabatino Di Diodoro
Fix For: 1.2.6, 2.0.0
Search roles by parent return an openjpa exception.
org.apache.openjpa.persistence.PersistenceException: Column "PARENT_ID_NAME"
not found; SQL statement:
CREATE FORCE VIEW PUBLIC._152 AS
SELECT DISTINCT
SUBJECT_ID
FROM PUBLIC.ROLE_SEARCH
WHERE PARENT_ID_NAME = ?1 [42122-190] {SELECT u.subject_id FROM (SELECT
DISTINCT subject_id FROM role_search WHERE parent_id_name=?) u WHERE
u.subject_id NOT IN (SELECT id AS subject_id FROM SyncopeRole WHERE id <>1 AND
id <>2 AND id <>3 AND id <>4 AND id <>5 AND id <>6 AND id <>7 AND id <>8 AND id
<>9 AND id <>10 AND id <>11 AND id <>12 AND id <>13 AND id <>14 AND id <>100
AND id <>101 AND id <>102 AND id <>104 AND id <>106 AND id <>108 AND id <>109
AND id <>110 AND id <>111 AND id <>112 AND id <>113 AND id <>114 AND id <>115
AND id <>116 AND id <>117 AND id <>118 AND id <>119 AND id <>122 AND id <>123
AND id <>124 AND id <>126)} [code=42122, state=42S22]
at
org.apache.openjpa.persistence.QueryImpl.getResultList(QueryImpl.java:291)
~[openjpa-persistence-2.3.0.jar:2.3.0]
at
org.apache.syncope.core.persistence.dao.impl.SubjectSearchDAOImpl.doSearch(SubjectSearchDAOImpl.java:364)
~[classes/:?]
at
org.apache.syncope.core.persistence.dao.impl.SubjectSearchDAOImpl.search(SubjectSearchDAOImpl.java:155)
~[classes/:?]
at
org.apache.syncope.core.rest.controller.RoleController.search(RoleController.java:216)
~[classes/:?]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (SYNCOPE-712) Error while searching roles by parent
[
https://issues.apache.org/jira/browse/SYNCOPE-712?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Di Sabatino Di Diodoro updated SYNCOPE-712:
-
Fix Version/s: (was: 2.0.0)
> Error while searching roles by parent
> -
>
> Key: SYNCOPE-712
> URL: https://issues.apache.org/jira/browse/SYNCOPE-712
> Project: Syncope
> Issue Type: Bug
> Components: core
>Affects Versions: 1.2.5
>Reporter: Marco Di Sabatino Di Diodoro
>Assignee: Marco Di Sabatino Di Diodoro
> Fix For: 1.2.6
>
>
> Search roles by parent return an openjpa exception.
> org.apache.openjpa.persistence.PersistenceException: Column "PARENT_ID_NAME"
> not found; SQL statement:
> CREATE FORCE VIEW PUBLIC._152 AS
> SELECT DISTINCT
> SUBJECT_ID
> FROM PUBLIC.ROLE_SEARCH
> WHERE PARENT_ID_NAME = ?1 [42122-190] {SELECT u.subject_id FROM (SELECT
> DISTINCT subject_id FROM role_search WHERE parent_id_name=?) u WHERE
> u.subject_id NOT IN (SELECT id AS subject_id FROM SyncopeRole WHERE id <>1
> AND id <>2 AND id <>3 AND id <>4 AND id <>5 AND id <>6 AND id <>7 AND id <>8
> AND id <>9 AND id <>10 AND id <>11 AND id <>12 AND id <>13 AND id <>14 AND id
> <>100 AND id <>101 AND id <>102 AND id <>104 AND id <>106 AND id <>108 AND id
> <>109 AND id <>110 AND id <>111 AND id <>112 AND id <>113 AND id <>114 AND id
> <>115 AND id <>116 AND id <>117 AND id <>118 AND id <>119 AND id <>122 AND id
> <>123 AND id <>124 AND id <>126)} [code=42122, state=42S22]
> at
> org.apache.openjpa.persistence.QueryImpl.getResultList(QueryImpl.java:291)
> ~[openjpa-persistence-2.3.0.jar:2.3.0]
> at
> org.apache.syncope.core.persistence.dao.impl.SubjectSearchDAOImpl.doSearch(SubjectSearchDAOImpl.java:364)
> ~[classes/:?]
> at
> org.apache.syncope.core.persistence.dao.impl.SubjectSearchDAOImpl.search(SubjectSearchDAOImpl.java:155)
> ~[classes/:?]
> at
> org.apache.syncope.core.rest.controller.RoleController.search(RoleController.java:216)
> ~[classes/:?]
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (SYNCOPE-734) Useless and unpleasant flickering during datatable record selection
[ https://issues.apache.org/jira/browse/SYNCOPE-734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-734. -- Resolution: Fixed > Useless and unpleasant flickering during datatable record selection > --- > > Key: SYNCOPE-734 > URL: https://issues.apache.org/jira/browse/SYNCOPE-734 > Project: Syncope > Issue Type: Bug >Reporter: fabio martelli >Assignee: Marco Di Sabatino Di Diodoro > > Remove useless and unpleasant flickering during datatable record selection. > Maybe by removing empty updates about ON_CHANGE events and by using ajax link > for page browsing we can easily solve this problem. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (SYNCOPE-734) Useless and unpleasant flickering during datatable record selection
[ https://issues.apache.org/jira/browse/SYNCOPE-734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro reassigned SYNCOPE-734: Assignee: Marco Di Sabatino Di Diodoro > Useless and unpleasant flickering during datatable record selection > --- > > Key: SYNCOPE-734 > URL: https://issues.apache.org/jira/browse/SYNCOPE-734 > Project: Syncope > Issue Type: Bug >Reporter: fabio martelli >Assignee: Marco Di Sabatino Di Diodoro > > Remove useless and unpleasant flickering during datatable record selection. > Maybe by removing empty updates about ON_CHANGE events and by using ajax link > for page browsing we can easily solve this problem. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SYNCOPE-739) Virtual atributes are not updated after a sync task
Marco Di Sabatino Di Diodoro created SYNCOPE-739: Summary: Virtual atributes are not updated after a sync task Key: SYNCOPE-739 URL: https://issues.apache.org/jira/browse/SYNCOPE-739 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.2.6 Reporter: Marco Di Sabatino Di Diodoro Assignee: Marco Di Sabatino Di Diodoro Fix For: 1.2.7, 2.0.0 During sync task, virtual attributes of an existing user are not updated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SYNCOPE-739) Virtual attributes are not updated after a sync task
[ https://issues.apache.org/jira/browse/SYNCOPE-739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro updated SYNCOPE-739: - Summary: Virtual attributes are not updated after a sync task (was: Virtual atributes are not updated after a sync task) > Virtual attributes are not updated after a sync task > > > Key: SYNCOPE-739 > URL: https://issues.apache.org/jira/browse/SYNCOPE-739 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 1.2.6 >Reporter: Marco Di Sabatino Di Diodoro >Assignee: Marco Di Sabatino Di Diodoro > Fix For: 1.2.7, 2.0.0 > > > During sync task, virtual attributes of an existing user are not updated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SYNCOPE-739) Virtual attributes are not updated after a sync task
[ https://issues.apache.org/jira/browse/SYNCOPE-739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-739. -- Resolution: Fixed > Virtual attributes are not updated after a sync task > > > Key: SYNCOPE-739 > URL: https://issues.apache.org/jira/browse/SYNCOPE-739 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 1.2.6 >Reporter: Marco Di Sabatino Di Diodoro >Assignee: Marco Di Sabatino Di Diodoro > Fix For: 1.2.7, 2.0.0 > > > During sync task, virtual attributes of an existing user are not updated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SYNCOPE-737) UserWizardBuilder, the store internally password flag is not set properly
Marco Di Sabatino Di Diodoro created SYNCOPE-737: Summary: UserWizardBuilder, the store internally password flag is not set properly Key: SYNCOPE-737 URL: https://issues.apache.org/jira/browse/SYNCOPE-737 Project: Syncope Issue Type: Bug Components: console Affects Versions: 2.0.0 Reporter: Marco Di Sabatino Di Diodoro Fix For: 2.0.0 In the creation of a new user by the wizard, the storePassword field is not set properly. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (SYNCOPE-752) Re-enable console tests
[ https://issues.apache.org/jira/browse/SYNCOPE-752?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro reassigned SYNCOPE-752: Assignee: Marco Di Sabatino Di Diodoro > Re-enable console tests > --- > > Key: SYNCOPE-752 > URL: https://issues.apache.org/jira/browse/SYNCOPE-752 > Project: Syncope > Issue Type: Sub-task > Components: console >Reporter: Francesco Chicchiriccò >Assignee: Marco Di Sabatino Di Diodoro > Fix For: 2.0.0 > > > Admin console tests (selenium-based) are still set against the 1.2.X code, > need to be upgraded or replaced. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (SYNCOPE-733) Table sort does not work fine in case of multi paged result
[ https://issues.apache.org/jira/browse/SYNCOPE-733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro reassigned SYNCOPE-733: Assignee: Marco Di Sabatino Di Diodoro > Table sort does not work fine in case of multi paged result > --- > > Key: SYNCOPE-733 > URL: https://issues.apache.org/jira/browse/SYNCOPE-733 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.0.0 >Reporter: fabio martelli >Assignee: Marco Di Sabatino Di Diodoro > Fix For: 2.0.0 > > > By clicking on a column label in order to sort the table results, sort occurs > but a new component for result page browsing is added. At the end we will > have one pagination component for every click performed to sort table results. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SYNCOPE-733) Table sort does not work fine in case of multi paged result
[ https://issues.apache.org/jira/browse/SYNCOPE-733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-733. -- Resolution: Fixed > Table sort does not work fine in case of multi paged result > --- > > Key: SYNCOPE-733 > URL: https://issues.apache.org/jira/browse/SYNCOPE-733 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.0.0 >Reporter: fabio martelli >Assignee: Marco Di Sabatino Di Diodoro > Fix For: 2.0.0 > > > By clicking on a column label in order to sort the table results, sort occurs > but a new component for result page browsing is added. At the end we will > have one pagination component for every click performed to sort table results. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
