[jira] [Created] (SYNCOPE-390) Default Reportlets improvements
Andrea Patricelli created SYNCOPE-390: - Summary: Default Reportlets improvements Key: SYNCOPE-390 URL: https://issues.apache.org/jira/browse/SYNCOPE-390 Project: Syncope Issue Type: Improvement Components: core Affects Versions: 1.1.1 Reporter: Andrea Patricelli Fix For: 1.1.2, 1.2.0 Some improvements to default reportlets shipped with Syncope -- 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-390) Default Reportlets improvements
[ https://issues.apache.org/jira/browse/SYNCOPE-390?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli updated SYNCOPE-390: -- Attachment: SYNCOPE-390.patch > Default Reportlets improvements > --- > > Key: SYNCOPE-390 > URL: https://issues.apache.org/jira/browse/SYNCOPE-390 > Project: Syncope > Issue Type: Improvement > Components: core >Affects Versions: 1.1.1 >Reporter: Andrea Patricelli > Fix For: 1.1.2, 1.2.0 > > Attachments: SYNCOPE-390.patch > > > Some improvements to default reportlets shipped with Syncope -- 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-395) add a role reportlet to make report (in xml, html, pdf, rtf versions) about roles on Apache Syncope
Andrea Patricelli created SYNCOPE-395: - Summary: add a role reportlet to make report (in xml, html, pdf, rtf versions) about roles on Apache Syncope Key: SYNCOPE-395 URL: https://issues.apache.org/jira/browse/SYNCOPE-395 Project: Syncope Issue Type: Improvement Components: core Reporter: Andrea Patricelli Priority: Minor Fix For: 1.1.3 -- 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-395) Role Reportlet
[ https://issues.apache.org/jira/browse/SYNCOPE-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli updated SYNCOPE-395: -- Summary: Role Reportlet (was: add a role reportlet to make report (in xml, html, pdf, rtf versions) about roles on Apache Syncope) > Role Reportlet > -- > > Key: SYNCOPE-395 > URL: https://issues.apache.org/jira/browse/SYNCOPE-395 > Project: Syncope > Issue Type: Improvement > Components: core >Reporter: Andrea Patricelli >Priority: Minor > Fix For: 1.1.3 > > -- 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-395) Role Reportlet
[ https://issues.apache.org/jira/browse/SYNCOPE-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli updated SYNCOPE-395: -- Attachment: SYNCOPE-395.patch added RoleReportlet.java, RoleReportletConf.java classes and xsl file for conversion to html and pdf/rtf > Role Reportlet > -- > > Key: SYNCOPE-395 > URL: https://issues.apache.org/jira/browse/SYNCOPE-395 > Project: Syncope > Issue Type: Improvement > Components: core >Reporter: Andrea Patricelli >Priority: Minor > Fix For: 1.1.3 > > Attachments: SYNCOPE-395.patch > > -- 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-395) Role Reportlet
[ https://issues.apache.org/jira/browse/SYNCOPE-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli updated SYNCOPE-395: -- Attachment: (was: SYNCOPE-395.patch) > Role Reportlet > -- > > Key: SYNCOPE-395 > URL: https://issues.apache.org/jira/browse/SYNCOPE-395 > Project: Syncope > Issue Type: Improvement > Components: core >Reporter: Andrea Patricelli >Priority: Minor > Fix For: 1.1.3 > > -- 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-395) Role Reportlet
[ https://issues.apache.org/jira/browse/SYNCOPE-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli updated SYNCOPE-395: -- Attachment: SYNCOPE-395.patch changed header of files into correct version > Role Reportlet > -- > > Key: SYNCOPE-395 > URL: https://issues.apache.org/jira/browse/SYNCOPE-395 > Project: Syncope > Issue Type: Improvement > Components: core >Reporter: Andrea Patricelli >Priority: Minor > Fix For: 1.1.3 > > Attachments: SYNCOPE-395.patch > > -- 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-397) double propagation on update of user with virtual attributes on already associated resource while editing password on syncope and adding a new resource to user
Andrea Patricelli created SYNCOPE-397: - Summary: double propagation on update of user with virtual attributes on already associated resource while editing password on syncope and adding a new resource to user Key: SYNCOPE-397 URL: https://issues.apache.org/jira/browse/SYNCOPE-397 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.1.2 Reporter: Andrea Patricelli Fix For: 1.1.3, 1.2.0 steps (run Syncope with -Pdev profile): 1. modify resource-csv mapping external attribute mail with virtual attribute virtualdata 2. create a new user with all required (for csv) fields set to value (username, surname, mail, type, ecc), in particular add derived attributes csvdir and cn and virtual attribute virtualdata 3. add to user resource-csv as resource, save and open it in edit mode. 4. add new resource to user, ws-target-resource-2, edit virtual attribute virtualdata. 5. edit password and check the checkbox to change password also on Syncope (don't check all resouces, csv must not be checked), checkbox for ws-target-resource-2 is already set. Save user It will be noticed a double propagation of user on both resources due to method fillVirtual() in PropagationManager.java -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SYNCOPE-397) Double update propagation with virtual attributes on already associated resource when changing password and adding new resource
[ https://issues.apache.org/jira/browse/SYNCOPE-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli updated SYNCOPE-397: -- Description: steps (run Syncope with -Pdev profile): 1. modify resource-csv mapping external attribute mail with virtual attribute virtualdata 2. create a new user with all required (for csv) fields set to value (username, surname, mail, type, ecc), in particular add derived attributes csvuserid and cn and virtual attribute virtualdata 3. add to user resource-csv as resource, save and open it in edit mode. 4. add new resource to user, ws-target-resource-2, edit virtual attribute virtualdata. 5. edit password and check the checkbox to change password also on Syncope (don't check all resouces, csv must not be checked), checkbox for ws-target-resource-2 is already set. Save user It will be noticed a double propagation of user on both resources due to method fillVirtual() in PropagationManager.java was: steps (run Syncope with -Pdev profile): 1. modify resource-csv mapping external attribute mail with virtual attribute virtualdata 2. create a new user with all required (for csv) fields set to value (username, surname, mail, type, ecc), in particular add derived attributes csvdir and cn and virtual attribute virtualdata 3. add to user resource-csv as resource, save and open it in edit mode. 4. add new resource to user, ws-target-resource-2, edit virtual attribute virtualdata. 5. edit password and check the checkbox to change password also on Syncope (don't check all resouces, csv must not be checked), checkbox for ws-target-resource-2 is already set. Save user It will be noticed a double propagation of user on both resources due to method fillVirtual() in PropagationManager.java > Double update propagation with virtual attributes on already associated > resource when changing password and adding new resource > --- > > Key: SYNCOPE-397 > URL: https://issues.apache.org/jira/browse/SYNCOPE-397 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 1.1.2 >Reporter: Andrea Patricelli > Fix For: 1.1.3, 1.2.0 > > > steps (run Syncope with -Pdev profile): > 1. modify resource-csv mapping external attribute mail with virtual attribute > virtualdata > 2. create a new user with all required (for csv) fields set to value > (username, surname, mail, type, ecc), in > particular add derived attributes csvuserid and cn and virtual attribute > virtualdata > 3. add to user resource-csv as resource, save and open it in edit mode. > 4. add new resource to user, ws-target-resource-2, edit virtual attribute > virtualdata. > 5. edit password and check the checkbox to change password also on Syncope > (don't check all resouces, csv must not be checked), checkbox for > ws-target-resource-2 is already set. Save user > It will be noticed a double propagation of user on both resources due to > method fillVirtual() in PropagationManager.java -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SYNCOPE-397) Double update propagation with virtual attributes on already associated resource when changing password and adding new resource
[ https://issues.apache.org/jira/browse/SYNCOPE-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli updated SYNCOPE-397: -- Description: steps (run Syncope with -Pdev profile): 1. modify resource-csv mapping external attribute mail with virtual attribute virtualdata (assign BOTH purpose to the attribute, it may also work with SYNCHRONIZATION). 2. create a new user with all required (for csv) fields set to value (username, surname, mail, type, ecc), in particular add derived attributes csvuserid and cn and virtual attribute virtualdata 3. add to user resource-csv as resource, save and open it in edit mode. 4. add new resource to user, ws-target-resource-2, edit virtual attribute virtualdata. 5. edit password and check the checkbox to change password also on Syncope (don't check all resouces, csv must not be checked), checkbox for ws-target-resource-2 is already set. Save user It will be noticed a double propagation of user on both resources due to method fillVirtual() in PropagationManager.java was: steps (run Syncope with -Pdev profile): 1. modify resource-csv mapping external attribute mail with virtual attribute virtualdata 2. create a new user with all required (for csv) fields set to value (username, surname, mail, type, ecc), in particular add derived attributes csvuserid and cn and virtual attribute virtualdata 3. add to user resource-csv as resource, save and open it in edit mode. 4. add new resource to user, ws-target-resource-2, edit virtual attribute virtualdata. 5. edit password and check the checkbox to change password also on Syncope (don't check all resouces, csv must not be checked), checkbox for ws-target-resource-2 is already set. Save user It will be noticed a double propagation of user on both resources due to method fillVirtual() in PropagationManager.java > Double update propagation with virtual attributes on already associated > resource when changing password and adding new resource > --- > > Key: SYNCOPE-397 > URL: https://issues.apache.org/jira/browse/SYNCOPE-397 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 1.1.2 >Reporter: Andrea Patricelli > Fix For: 1.1.3, 1.2.0 > > > steps (run Syncope with -Pdev profile): > 1. modify resource-csv mapping external attribute mail with virtual attribute > virtualdata (assign BOTH > purpose to the attribute, it may also work with SYNCHRONIZATION). > 2. create a new user with all required (for csv) fields set to value > (username, surname, mail, type, ecc), in > particular add derived attributes csvuserid and cn and virtual attribute > virtualdata > 3. add to user resource-csv as resource, save and open it in edit mode. > 4. add new resource to user, ws-target-resource-2, edit virtual attribute > virtualdata. > 5. edit password and check the checkbox to change password also on Syncope > (don't check all resouces, csv must not be checked), checkbox for > ws-target-resource-2 is already set. Save user > It will be noticed a double propagation of user on both resources due to > method fillVirtual() in PropagationManager.java -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SYNCOPE-397) Double update propagation with virtual attributes on already associated resource when changing password and adding new resource
[ https://issues.apache.org/jira/browse/SYNCOPE-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli updated SYNCOPE-397: -- Attachment: SYNCOPE-397.patch reporting test case to reproduce issue behavior > Double update propagation with virtual attributes on already associated > resource when changing password and adding new resource > --- > > Key: SYNCOPE-397 > URL: https://issues.apache.org/jira/browse/SYNCOPE-397 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 1.1.2 >Reporter: Andrea Patricelli > Fix For: 1.1.3, 1.2.0 > > Attachments: SYNCOPE-397.patch > > > steps (run Syncope with -Pdev profile): > 1. modify resource-csv mapping external attribute mail with virtual attribute > virtualdata (assign BOTH > purpose to the attribute, it may also work with SYNCHRONIZATION). > 2. create a new user with all required (for csv) fields set to value > (username, surname, mail, type, ecc), in > particular add derived attributes csvuserid and cn and virtual attribute > virtualdata > 3. add to user resource-csv as resource, save and open it in edit mode. > 4. add new resource to user, ws-target-resource-2, edit virtual attribute > virtualdata. > 5. edit password and check the checkbox to change password also on Syncope > (don't check all resouces, csv must not be checked), checkbox for > ws-target-resource-2 is already set. Save user > It will be noticed a double propagation of user on both resources due to > method fillVirtual() in PropagationManager.java -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SYNCOPE-397) Double update propagation with virtual attributes on already associated resource when changing password and adding new resource
[ https://issues.apache.org/jira/browse/SYNCOPE-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli updated SYNCOPE-397: -- Attachment: (was: SYNCOPE-397.patch) > Double update propagation with virtual attributes on already associated > resource when changing password and adding new resource > --- > > Key: SYNCOPE-397 > URL: https://issues.apache.org/jira/browse/SYNCOPE-397 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 1.1.2 >Reporter: Andrea Patricelli > Fix For: 1.1.3, 1.2.0 > > > steps (run Syncope with -Pdev profile): > 1. modify resource-csv mapping external attribute mail with virtual attribute > virtualdata (assign BOTH > purpose to the attribute, it may also work with SYNCHRONIZATION). > 2. create a new user with all required (for csv) fields set to value > (username, surname, mail, type, ecc), in > particular add derived attributes csvuserid and cn and virtual attribute > virtualdata > 3. add to user resource-csv as resource, save and open it in edit mode. > 4. add new resource to user, ws-target-resource-2, edit virtual attribute > virtualdata. > 5. edit password and check the checkbox to change password also on Syncope > (don't check all resouces, csv must not be checked), checkbox for > ws-target-resource-2 is already set. Save user > It will be noticed a double propagation of user on both resources due to > method fillVirtual() in PropagationManager.java -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SYNCOPE-397) Double update propagation with virtual attributes on already associated resource when changing password and adding new resource
[ https://issues.apache.org/jira/browse/SYNCOPE-397?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli updated SYNCOPE-397: -- Attachment: SYNCOPE-397.patch patch containing test case plus bug-fix > Double update propagation with virtual attributes on already associated > resource when changing password and adding new resource > --- > > Key: SYNCOPE-397 > URL: https://issues.apache.org/jira/browse/SYNCOPE-397 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 1.1.2 >Reporter: Andrea Patricelli > Fix For: 1.1.3, 1.2.0 > > Attachments: SYNCOPE-397.patch > > > steps (run Syncope with -Pdev profile): > 1. modify resource-csv mapping external attribute mail with virtual attribute > virtualdata (assign BOTH > purpose to the attribute, it may also work with SYNCHRONIZATION). > 2. create a new user with all required (for csv) fields set to value > (username, surname, mail, type, ecc), in > particular add derived attributes csvuserid and cn and virtual attribute > virtualdata > 3. add to user resource-csv as resource, save and open it in edit mode. > 4. add new resource to user, ws-target-resource-2, edit virtual attribute > virtualdata. > 5. edit password and check the checkbox to change password also on Syncope > (don't check all resouces, csv must not be checked), checkbox for > ws-target-resource-2 is already set. Save user > It will be noticed a double propagation of user on both resources due to > method fillVirtual() in PropagationManager.java -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SYNCOPE-395) Role Reportlet
[ https://issues.apache.org/jira/browse/SYNCOPE-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli updated SYNCOPE-395: -- Attachment: (was: SYNCOPE-395.patch) > Role Reportlet > -- > > Key: SYNCOPE-395 > URL: https://issues.apache.org/jira/browse/SYNCOPE-395 > Project: Syncope > Issue Type: Improvement > Components: core >Reporter: Andrea Patricelli >Priority: Minor > Fix For: 1.1.3 > > -- 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-395) Role Reportlet
[ https://issues.apache.org/jira/browse/SYNCOPE-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli updated SYNCOPE-395: -- Attachment: SYNCOPE-395.patch new improved patch for role report > Role Reportlet > -- > > Key: SYNCOPE-395 > URL: https://issues.apache.org/jira/browse/SYNCOPE-395 > Project: Syncope > Issue Type: Improvement > Components: core >Reporter: Andrea Patricelli >Priority: Minor > Fix For: 1.1.3 > > Attachments: SYNCOPE-395.patch > > -- 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-395) Role Reportlet
[ https://issues.apache.org/jira/browse/SYNCOPE-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli updated SYNCOPE-395: -- Attachment: (was: SYNCOPE-395.patch) > Role Reportlet > -- > > Key: SYNCOPE-395 > URL: https://issues.apache.org/jira/browse/SYNCOPE-395 > Project: Syncope > Issue Type: Improvement > Components: core >Reporter: Andrea Patricelli >Priority: Minor > Fix For: 1.1.3 > > -- 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-395) Role Reportlet
[ https://issues.apache.org/jira/browse/SYNCOPE-395?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli updated SYNCOPE-395: -- Attachment: SYNCOPE-395.patch final patch with all headers corrected and upadted > Role Reportlet > -- > > Key: SYNCOPE-395 > URL: https://issues.apache.org/jira/browse/SYNCOPE-395 > Project: Syncope > Issue Type: Improvement > Components: core >Reporter: Andrea Patricelli >Priority: Minor > Fix For: 1.1.3 > > Attachments: SYNCOPE-395.patch > > -- 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-402) Inconsistent status of user edit form after exception returned by bad propagation on primary resource
Andrea Patricelli created SYNCOPE-402: - Summary: 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 Affects Versions: 1.1.3, 1.1.2 Reporter: Andrea Patricelli Fix For: 1.1.4 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] [Created] (SYNCOPE-403) Enrich PropagationStatusTO to report possible propagation exception message
Andrea Patricelli created SYNCOPE-403: - Summary: 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 Affects Versions: 1.1.3, 1.1.2 Reporter: Andrea Patricelli Fix For: 1.1.4 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] [Updated] (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 ] Andrea Patricelli updated SYNCOPE-403: -- Component/s: common > 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 >Affects Versions: 1.1.2, 1.1.3 >Reporter: Andrea Patricelli > Fix For: 1.1.4 > > > 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] [Updated] (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 ] Andrea Patricelli updated SYNCOPE-403: -- Component/s: core Fix Version/s: 1.2.0 Assignee: Andrea Patricelli > 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, core >Affects Versions: 1.1.2, 1.1.3 >Reporter: Andrea Patricelli >Assignee: Andrea Patricelli > Fix For: 1.1.4, 1.2.0 > > > 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] [Updated] (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 ] Andrea Patricelli updated SYNCOPE-402: -- Component/s: core Fix Version/s: 1.2.0 > 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 > 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] [Updated] (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 ] Andrea Patricelli updated SYNCOPE-403: -- Attachment: SYNCOPE-403.patch > 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, core >Affects Versions: 1.1.2, 1.1.3 >Reporter: Andrea Patricelli >Assignee: Andrea Patricelli > 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] [Updated] (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 ] Andrea Patricelli updated SYNCOPE-403: -- Attachment: (was: SYNCOPE-403.patch) > 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, core >Affects Versions: 1.1.2, 1.1.3 >Reporter: Andrea Patricelli >Assignee: Andrea Patricelli > Fix For: 1.1.4, 1.2.0 > > > 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] [Updated] (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 ] Andrea Patricelli updated SYNCOPE-403: -- Attachment: SYNCOPE-403.patch > 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, core >Affects Versions: 1.1.2, 1.1.3 >Reporter: Andrea Patricelli >Assignee: Andrea Patricelli > 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] [Updated] (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 ] Andrea Patricelli updated SYNCOPE-403: -- Attachment: SYNCOPE-403.patch > 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, core >Affects Versions: 1.1.2, 1.1.3 >Reporter: Andrea Patricelli >Assignee: Andrea Patricelli > 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] [Updated] (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 ] Andrea Patricelli updated SYNCOPE-403: -- Attachment: (was: SYNCOPE-403.patch) > 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, core >Affects Versions: 1.1.2, 1.1.3 >Reporter: Andrea Patricelli >Assignee: Andrea Patricelli > Fix For: 1.1.4, 1.2.0 > > > 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] [Updated] (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 ] Andrea Patricelli updated SYNCOPE-403: -- Component/s: console > 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] [Updated] (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 ] Andrea Patricelli updated SYNCOPE-403: -- Attachment: SYNCOPE-403.patch > 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, 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] [Updated] (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 ] Andrea Patricelli updated SYNCOPE-403: -- Attachment: (was: SYNCOPE-403.patch) > 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, 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] [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 ] Andrea Patricelli reassigned SYNCOPE-402: - Assignee: Andrea Patricelli (was: 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: Andrea Patricelli > 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] [Updated] (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 ] Andrea Patricelli updated SYNCOPE-402: -- Assignee: Marco Di Sabatino Di Diodoro (was: Andrea Patricelli) > 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] [Reopened] (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 ] Andrea Patricelli reopened SYNCOPE-403: --- FailureMessageModalPage.html missing tag > 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] [Updated] (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 ] Andrea Patricelli updated SYNCOPE-403: -- Attachment: MissingExtend.patch > 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: MissingExtend.patch, 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] [Created] (SYNCOPE-437) Wrong ID generation for new Notification instances
Andrea Patricelli created SYNCOPE-437: - Summary: Wrong ID generation for new Notification instances Key: SYNCOPE-437 URL: https://issues.apache.org/jira/browse/SYNCOPE-437 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.1.4 Reporter: Andrea Patricelli Assignee: Andrea Patricelli Fix For: 1.1.5, 1.2.0 When creating a new instance of Notification, IDs of created instances start from 1 and not from 100 as expected; this is due to the AUTO generation of IDs for Notification entity. This may lead to possible primary key violation errors. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (SYNCOPE-437) Wrong ID generation for new Notification instances
[ https://issues.apache.org/jira/browse/SYNCOPE-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli updated SYNCOPE-437: -- Description: When creating a new instance of Notification, IDs of created instances start from 1 and not from 100 as expected; this is due to the AUTO generation of IDs for Notification entity. This may lead to possible primary key violation errors; in particular if importing from content.xml notification instances as happens in "dev" profile. was: When creating a new instance of Notification, IDs of created instances start from 1 and not from 100 as expected; this is due to the AUTO generation of IDs for Notification entity. This may lead to possible primary key violation errors. > Wrong ID generation for new Notification instances > -- > > Key: SYNCOPE-437 > URL: https://issues.apache.org/jira/browse/SYNCOPE-437 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 1.1.4 >Reporter: Andrea Patricelli >Assignee: Andrea Patricelli > Fix For: 1.1.5, 1.2.0 > > > When creating a new instance of Notification, IDs of created instances start > from 1 and not from 100 as expected; this is due to the AUTO generation of > IDs for Notification entity. > This may lead to possible primary key violation errors; in particular if > importing from content.xml notification instances as happens in "dev" > profile. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (SYNCOPE-437) Wrong ID generation for new Notification instances
[ https://issues.apache.org/jira/browse/SYNCOPE-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli updated SYNCOPE-437: -- Attachment: SYNCOPE-437.patch > Wrong ID generation for new Notification instances > -- > > Key: SYNCOPE-437 > URL: https://issues.apache.org/jira/browse/SYNCOPE-437 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 1.1.4 >Reporter: Andrea Patricelli >Assignee: Andrea Patricelli > Fix For: 1.1.5, 1.2.0 > > Attachments: SYNCOPE-437.patch > > > When creating a new instance of Notification, IDs of created instances start > from 1 and not from 100 as expected; this is due to the AUTO generation of > IDs for Notification entity. > This may lead to possible primary key violation errors; in particular if > importing from content.xml notification instances as happens in "dev" > profile. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (SYNCOPE-437) Wrong ID generation for new Notification instances
[ https://issues.apache.org/jira/browse/SYNCOPE-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli updated SYNCOPE-437: -- Attachment: (was: SYNCOPE-437.patch) > Wrong ID generation for new Notification instances > -- > > Key: SYNCOPE-437 > URL: https://issues.apache.org/jira/browse/SYNCOPE-437 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 1.1.4 >Reporter: Andrea Patricelli >Assignee: Andrea Patricelli > Fix For: 1.1.5, 1.2.0 > > > When creating a new instance of Notification, IDs of created instances start > from 1 and not from 100 as expected; this is due to the AUTO generation of > IDs for Notification entity. > This may lead to possible primary key violation errors; in particular if > importing from content.xml notification instances as happens in "dev" > profile. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (SYNCOPE-437) Wrong ID generation for new Notification instances
[ https://issues.apache.org/jira/browse/SYNCOPE-437?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli updated SYNCOPE-437: -- Attachment: SYNCOPE-437.patch included modifications to orm.xml mysql and oracle > Wrong ID generation for new Notification instances > -- > > Key: SYNCOPE-437 > URL: https://issues.apache.org/jira/browse/SYNCOPE-437 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 1.1.4 >Reporter: Andrea Patricelli >Assignee: Andrea Patricelli > Fix For: 1.1.5, 1.2.0 > > Attachments: SYNCOPE-437.patch > > > When creating a new instance of Notification, IDs of created instances start > from 1 and not from 100 as expected; this is due to the AUTO generation of > IDs for Notification entity. > This may lead to possible primary key violation errors; in particular if > importing from content.xml notification instances as happens in "dev" > profile. -- This message was sent by Atlassian JIRA (v6.1#6144)
[jira] [Updated] (SYNCOPE-476) NPE opening Roles tab
[ https://issues.apache.org/jira/browse/SYNCOPE-476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli updated SYNCOPE-476: -- Attachment: SYNCOPE-476.patch > NPE opening Roles tab > - > > Key: SYNCOPE-476 > URL: https://issues.apache.org/jira/browse/SYNCOPE-476 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 1.1.5 >Reporter: Massimiliano Perrone >Priority: Critical > Fix For: 1.1.6, 1.2.0 > > Attachments: SYNCOPE-476.patch > > > 1) checkout branch 1_1_X > 2) cd 1_1_X; mvn clean install > 3) cd console; mvn -Pdebug > 4) login into console > 5) click on Roles tab > 6) java.lang.NullPointerException > at > org.apache.syncope.console.pages.panels.AbstractSearchResultPanel.(AbstractSearchResultPanel.java:170) > at > org.apache.syncope.console.pages.panels.RoleSearchResultPanel.(RoleSearchResultPanel.java:59) > at org.apache.syncope.console.pages.Roles.(Roles.java:97) -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Assigned] (SYNCOPE-476) NPE opening Roles tab
[ https://issues.apache.org/jira/browse/SYNCOPE-476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli reassigned SYNCOPE-476: - Assignee: Andrea Patricelli > NPE opening Roles tab > - > > Key: SYNCOPE-476 > URL: https://issues.apache.org/jira/browse/SYNCOPE-476 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 1.1.5 >Reporter: Massimiliano Perrone >Assignee: Andrea Patricelli >Priority: Critical > Fix For: 1.1.6, 1.2.0 > > Attachments: SYNCOPE-476.patch > > > 1) checkout branch 1_1_X > 2) cd 1_1_X; mvn clean install > 3) cd console; mvn -Pdebug > 4) login into console > 5) click on Roles tab > 6) java.lang.NullPointerException > at > org.apache.syncope.console.pages.panels.AbstractSearchResultPanel.(AbstractSearchResultPanel.java:170) > at > org.apache.syncope.console.pages.panels.RoleSearchResultPanel.(RoleSearchResultPanel.java:59) > at org.apache.syncope.console.pages.Roles.(Roles.java:97) -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (SYNCOPE-476) NPE opening Roles tab
[ https://issues.apache.org/jira/browse/SYNCOPE-476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli updated SYNCOPE-476: -- Attachment: (was: SYNCOPE-476.patch) > NPE opening Roles tab > - > > Key: SYNCOPE-476 > URL: https://issues.apache.org/jira/browse/SYNCOPE-476 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 1.1.5 >Reporter: Massimiliano Perrone >Assignee: Andrea Patricelli >Priority: Critical > Fix For: 1.1.6, 1.2.0 > > > 1) checkout branch 1_1_X > 2) cd 1_1_X; mvn clean install > 3) cd console; mvn -Pdebug > 4) login into console > 5) click on Roles tab > 6) java.lang.NullPointerException > at > org.apache.syncope.console.pages.panels.AbstractSearchResultPanel.(AbstractSearchResultPanel.java:170) > at > org.apache.syncope.console.pages.panels.RoleSearchResultPanel.(RoleSearchResultPanel.java:59) > at org.apache.syncope.console.pages.Roles.(Roles.java:97) -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (SYNCOPE-476) NPE opening Roles tab
[ https://issues.apache.org/jira/browse/SYNCOPE-476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli updated SYNCOPE-476: -- Attachment: SYNCOPE-476.patch > NPE opening Roles tab > - > > Key: SYNCOPE-476 > URL: https://issues.apache.org/jira/browse/SYNCOPE-476 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 1.1.5 >Reporter: Massimiliano Perrone >Assignee: Andrea Patricelli >Priority: Critical > Fix For: 1.1.6, 1.2.0 > > Attachments: SYNCOPE-476.patch > > > 1) checkout branch 1_1_X > 2) cd 1_1_X; mvn clean install > 3) cd console; mvn -Pdebug > 4) login into console > 5) click on Roles tab > 6) java.lang.NullPointerException > at > org.apache.syncope.console.pages.panels.AbstractSearchResultPanel.(AbstractSearchResultPanel.java:170) > at > org.apache.syncope.console.pages.panels.RoleSearchResultPanel.(RoleSearchResultPanel.java:59) > at org.apache.syncope.console.pages.Roles.(Roles.java:97) -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (SYNCOPE-477) Alert popup appears through page navigation after modal window closing
Andrea Patricelli created SYNCOPE-477: - Summary: Alert popup appears through page navigation after modal window closing Key: SYNCOPE-477 URL: https://issues.apache.org/jira/browse/SYNCOPE-477 Project: Syncope Issue Type: Bug Components: console Affects Versions: 1.1.5 Reporter: Andrea Patricelli Fix For: 1.1.6, 1.2.0 This behavior occurs when an edit modal window is opened and then closed. To reproduce the problem: 1) checkout branch 1_1_X 2) cd 1_1_X; mvn clean install 3) cd console; mvn -Pdebug 4) login into console 5) go under Configuration and edit (open edit modal window) a parameter 6) close edit modal window (with link or with ESC) 7) click on another page link, Users for example -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (SYNCOPE-480) Change feedback panel into a smart animated notification panel
Andrea Patricelli created SYNCOPE-480: - Summary: Change feedback panel into a smart animated notification panel Key: SYNCOPE-480 URL: https://issues.apache.org/jira/browse/SYNCOPE-480 Project: Syncope Issue Type: Improvement Components: console Reporter: Andrea Patricelli Priority: Minor Fix For: 1.2.0 Extend simple Wicket feedback panel with a new one provided with toggling animation and smart behavior (timeout based on message to show length). -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Created] (SYNCOPE-484) Reports and Content export fails over HTTPS connection
Andrea Patricelli created SYNCOPE-484: - Summary: Reports and Content export fails over HTTPS connection Key: SYNCOPE-484 URL: https://issues.apache.org/jira/browse/SYNCOPE-484 Project: Syncope Issue Type: Bug Components: client, console Affects Versions: 1.1.6 Reporter: Andrea Patricelli Fix For: 1.1.7 When Apache Syncope is configured to work in HTTPS, export (thus download) of documents as content.xml or reports (all available formats) fails returning HttpClientProtocol exception and message "the server failed to respond with a valid HTTP response". To reproduce the error: 1. Setup Apache Syncope to work over HTTPS connection (edit console configuration.properties). 2. Deploy and run on a web server (Apache Tomcat for example). 4. Log-in with credentials admin, password. 3. Try to export Content (Configuration > DB export). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (SYNCOPE-484) Reports and Content export fails over HTTPS connection
[ https://issues.apache.org/jira/browse/SYNCOPE-484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli updated SYNCOPE-484: -- Attachment: SYNCOPE-484.patch The problem is due to the fact that SpringServiceProxy always executes HTTP GET request with target host having protocol scheme set to default value (HTTP) and not to correct authorization scope scheme value (HTTPS in our case). > Reports and Content export fails over HTTPS connection > -- > > Key: SYNCOPE-484 > URL: https://issues.apache.org/jira/browse/SYNCOPE-484 > Project: Syncope > Issue Type: Bug > Components: client, console >Affects Versions: 1.1.6 >Reporter: Andrea Patricelli > Fix For: 1.1.7 > > Attachments: SYNCOPE-484.patch > > > When Apache Syncope is configured to work in HTTPS, export (thus download) of > documents as content.xml or reports (all available formats) fails returning > HttpClientProtocol exception and message "the server failed to respond with a > valid HTTP response". > To reproduce the error: > 1. Setup Apache Syncope to work over HTTPS connection (edit console > configuration.properties). > 2. Deploy and run on a web server (Apache Tomcat for example). > 4. Log-in with credentials admin, password. > 3. Try to export Content (Configuration > DB export). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (SYNCOPE-480) Change feedback panel into a smart animated notification panel
[ https://issues.apache.org/jira/browse/SYNCOPE-480?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli reassigned SYNCOPE-480: - Assignee: Andrea Patricelli > Change feedback panel into a smart animated notification panel > -- > > Key: SYNCOPE-480 > URL: https://issues.apache.org/jira/browse/SYNCOPE-480 > Project: Syncope > Issue Type: Improvement > Components: console >Reporter: Andrea Patricelli >Assignee: Andrea Patricelli >Priority: Minor > Fix For: 1.2.0 > > > Extend simple Wicket feedback panel with a new one provided with toggling > animation and smart behavior (timeout based on message to show length). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (SYNCOPE-489) Feedback panel not working in workflow xml editor popup
[ https://issues.apache.org/jira/browse/SYNCOPE-489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli reassigned SYNCOPE-489: - Assignee: Andrea Patricelli > Feedback panel not working in workflow xml editor popup > --- > > Key: SYNCOPE-489 > URL: https://issues.apache.org/jira/browse/SYNCOPE-489 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 1.2.0 >Reporter: Andrea Patricelli >Assignee: Andrea Patricelli >Priority: Minor > Fix For: 1.2.0 > > > 1. Access to console and open configuration tab > 2. open workflow sub-tab and then workflow XML editor (a popup window is > showed). > 3. edit (correctly or incorrectly, doesn't matter) XML workflow definition > and then click SAVE button. > No feedback panel, of success or failure, is showed neither in popup, nor in > main configuration page. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (SYNCOPE-489) Feedback panel not working in workflow xml editor popup
Andrea Patricelli created SYNCOPE-489: - Summary: Feedback panel not working in workflow xml editor popup Key: SYNCOPE-489 URL: https://issues.apache.org/jira/browse/SYNCOPE-489 Project: Syncope Issue Type: Bug Components: console Affects Versions: 1.2.0 Reporter: Andrea Patricelli Priority: Minor Fix For: 1.2.0 1. Access to console and open configuration tab 2. open workflow sub-tab and then workflow XML editor (a popup window is showed). 3. edit (correctly or incorrectly, doesn't matter) XML workflow definition and then click SAVE button. No feedback panel, of success or failure, is showed neither in popup, nor in main configuration page. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SYNCOPE-480) Change feedback panel into a smart animated notification panel
[ https://issues.apache.org/jira/browse/SYNCOPE-480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13991633#comment-13991633 ] Andrea Patricelli commented on SYNCOPE-480: --- Added smart notification panel, revision http://svn.apache.org/r1592778 > Change feedback panel into a smart animated notification panel > -- > > Key: SYNCOPE-480 > URL: https://issues.apache.org/jira/browse/SYNCOPE-480 > Project: Syncope > Issue Type: Improvement > Components: console >Reporter: Andrea Patricelli >Assignee: Andrea Patricelli >Priority: Minor > Fix For: 1.2.0 > > > Extend simple Wicket feedback panel with a new one provided with toggling > animation and smart behavior (timeout based on message to show length). -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (SYNCOPE-486) Update Selenium test configuration
[ https://issues.apache.org/jira/browse/SYNCOPE-486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli reassigned SYNCOPE-486: - Assignee: Andrea Patricelli > Update Selenium test configuration > -- > > Key: SYNCOPE-486 > URL: https://issues.apache.org/jira/browse/SYNCOPE-486 > Project: Syncope > Issue Type: Improvement > Components: console >Reporter: Francesco Chicchiriccò >Assignee: Andrea Patricelli > Labels: selenium, test > Fix For: 1.1.8, 1.2.0 > > > Currently Selenium is configured, for admin console, to run via > selenium-maven-plugin, updated to Selenium 2.30. > Unfortunately, this version is reported [1] to have a long-standing bug with > latest (>= 23.0) Firefox versions. > It seems that Selenium 2.40 solves such issue, but it requires a Maven > configuration change, according to [2] > [1] https://code.google.com/p/selenium/issues/detail?id=6112 > [2] http://docs.seleniumhq.org/download/maven.jsp -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (SYNCOPE-489) Feedback panel not working in workflow xml editor popup
[ https://issues.apache.org/jira/browse/SYNCOPE-489?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli closed SYNCOPE-489. - Resolution: Fixed > Feedback panel not working in workflow xml editor popup > --- > > Key: SYNCOPE-489 > URL: https://issues.apache.org/jira/browse/SYNCOPE-489 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 1.2.0 >Reporter: Andrea Patricelli >Assignee: Andrea Patricelli >Priority: Minor > Fix For: 1.2.0 > > > 1. Access to console and open configuration tab > 2. open workflow sub-tab and then workflow XML editor (a popup window is > shown). > 3. edit (correctly or incorrectly, doesn't matter) XML workflow definition > and then click SAVE button. > No feedback panel, of success or failure, is shown neither in popup, nor in > main configuration page. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (SYNCOPE-490) Problem returning to login page with manual url insertion after typing invalid username and/or password
Andrea Patricelli created SYNCOPE-490: - Summary: Problem returning to login page with manual url insertion after typing invalid username and/or password Key: SYNCOPE-490 URL: https://issues.apache.org/jira/browse/SYNCOPE-490 Project: Syncope Issue Type: Bug Components: console Affects Versions: 1.2.0 Reporter: Andrea Patricelli Assignee: Andrea Patricelli Priority: Minor Fix For: 1.2.0 1. Try to log into console with wrong (unexisting) username and/or password 2. After error notification panel is shown, reload manually the page by typing home page url (http://localhost:9080/syncope-console for example) in browser url section, you'll be redirected to Syncope error page. 3. Clicking "home" link in error window does not make redirection to blank login page, as expected, but we get stuck in the same error page. The only way to return to login page is to logout through logout button. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Closed] (SYNCOPE-490) Problem returning to login page with manual url insertion after typing invalid username and/or password
[ https://issues.apache.org/jira/browse/SYNCOPE-490?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli closed SYNCOPE-490. - Resolution: Fixed > Problem returning to login page with manual url insertion after typing > invalid username and/or password > --- > > Key: SYNCOPE-490 > URL: https://issues.apache.org/jira/browse/SYNCOPE-490 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 1.2.0 >Reporter: Andrea Patricelli >Assignee: Andrea Patricelli >Priority: Minor > Fix For: 1.2.0 > > > 1. Try to log into console with wrong (unexisting) username and/or password > 2. After error notification panel is shown, reload manually the page by > typing home page url (http://localhost:9080/syncope-console for example) in > browser url section, you'll be redirected to Syncope error page. > 3. Clicking "home" link in error window does not make redirection to blank > login page, as expected, but we get stuck in the same error page. > The only way to return to login page is to logout through logout button. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (SYNCOPE-486) Update Selenium test configuration
[ https://issues.apache.org/jira/browse/SYNCOPE-486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli resolved SYNCOPE-486. --- Resolution: Fixed Selenium tests doesn't work with selenium-maven-plugin anymore, but only with Failsafe Plugin and Selenium WebDriver Backend. Tests now run with Firefox >= 23 (tested with latest Firefox release 29.0). > Update Selenium test configuration > -- > > Key: SYNCOPE-486 > URL: https://issues.apache.org/jira/browse/SYNCOPE-486 > Project: Syncope > Issue Type: Improvement > Components: console >Reporter: Francesco Chicchiriccò >Assignee: Andrea Patricelli > Labels: selenium, test > Fix For: 1.1.8, 1.2.0 > > > Currently Selenium is configured, for admin console, to run via > selenium-maven-plugin, updated to Selenium 2.30. > Unfortunately, this version is reported [1] to have a long-standing bug with > latest (>= 23.0) Firefox versions. > It seems that Selenium 2.40 solves such issue, but it requires a Maven > configuration change, according to [2] > [1] https://code.google.com/p/selenium/issues/detail?id=6112 > [2] http://docs.seleniumhq.org/download/maven.jsp -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SYNCOPE-491) Use consistent icon set
[ https://issues.apache.org/jira/browse/SYNCOPE-491?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13998534#comment-13998534 ] Andrea Patricelli commented on SYNCOPE-491: --- +1 (non binding) > Use consistent icon set > --- > > Key: SYNCOPE-491 > URL: https://issues.apache.org/jira/browse/SYNCOPE-491 > Project: Syncope > Issue Type: Improvement > Components: console >Reporter: Massimiliano Perrone >Assignee: Massimiliano Perrone >Priority: Trivial > Fix For: 1.2.0 > > Attachments: five.png, four.png, one.png, seven.png, six.png, > three.png, two.png > > > Find an icon set to align the icons style. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (SYNCOPE-447) Create a single task for all events into a given notification
[ https://issues.apache.org/jira/browse/SYNCOPE-447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli reassigned SYNCOPE-447: - Assignee: Andrea Patricelli > Create a single task for all events into a given notification > - > > Key: SYNCOPE-447 > URL: https://issues.apache.org/jira/browse/SYNCOPE-447 > Project: Syncope > Issue Type: Improvement > Components: core >Affects Versions: 1.2.0 >Reporter: fabio martelli >Assignee: Andrea Patricelli > Fix For: 1.2.0 > > > Cumulative notification: create a single task for all events into a given > notification. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SYNCOPE-447) Create a single task for all events into a given notification
[ https://issues.apache.org/jira/browse/SYNCOPE-447?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14001883#comment-14001883 ] Andrea Patricelli commented on SYNCOPE-447: --- Mechanism of creating cumulative notifications is already available by a proper configuration of notification. A simple use case is user synchronization; a) if we want to have a notification task for each user creation/update coming from sync task we can configure notification task to generate notification on this event [SyncTask]:[user]:[resourceName]:[create]:[SUCCESS]. b) But if we do not want to have too many notifications, like point 1, we can configure notification to create a notification task only when synchronization job finishes, setting notification event to [TASK]:[SyncJob]:[]:[SyncJob]:[SUCCESS] instead of [SyncTask]:[user]:[resourceName]:[create]:[SUCCESS]. In case of a large number of users to synchronize b is preferable, and cumulative notification is sent. We can instead improve notification messages to show a better and more complete notification message generated from jobs like SyncJob or PushJob and also provide new mail and text templates useful for use case exposed above. > Create a single task for all events into a given notification > - > > Key: SYNCOPE-447 > URL: https://issues.apache.org/jira/browse/SYNCOPE-447 > Project: Syncope > Issue Type: Improvement > Components: core >Affects Versions: 1.2.0 >Reporter: fabio martelli >Assignee: Andrea Patricelli > Fix For: 1.2.0 > > > Cumulative notification: create a single task for all events into a given > notification. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (SYNCOPE-447) Provide the ability to have a single (cumulative) notification for task execution
[ https://issues.apache.org/jira/browse/SYNCOPE-447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli updated SYNCOPE-447: -- Description: A simple use case is user synchronization; a) if we want to have a notification task for each user creation/update coming from sync task we can configure notification task to generate notification on this event [SyncTask]:[user]:[resourceName]:[create]:[SUCCESS]. b) But if we do not want to have too many notifications, like point 1, we can configure notification to create a notification task only when synchronization job finishes, setting notification event to [TASK]:[SyncJob]:[]:[SyncJob]:[SUCCESS] instead of [SyncTask]:[user]:[resourceName]:[create]:[SUCCESS]. In case of a large number of users to synchronize b is preferable, and cumulative notification is sent. Improve notification messages to show a better and more complete notification message generated from jobs like SyncJob or PushJob and also provide new mail and text templates useful for use case exposed above. was:Cumulative notification: create a single task for all events into a given notification. Summary: Provide the ability to have a single (cumulative) notification for task execution (was: Create a single task for all events into a given notification) > Provide the ability to have a single (cumulative) notification for task > execution > - > > Key: SYNCOPE-447 > URL: https://issues.apache.org/jira/browse/SYNCOPE-447 > Project: Syncope > Issue Type: Improvement > Components: core >Affects Versions: 1.2.0 >Reporter: fabio martelli >Assignee: Andrea Patricelli > Fix For: 1.2.0 > > > A simple use case is user synchronization; > a) if we want to have a notification task for each user creation/update > coming from sync task we can configure notification task to generate > notification on this event > [SyncTask]:[user]:[resourceName]:[create]:[SUCCESS]. > b) But if we do not want to have too many notifications, like point 1, we can > configure notification to create a notification task only when > synchronization job finishes, setting notification event to > [TASK]:[SyncJob]:[]:[SyncJob]:[SUCCESS] instead of > [SyncTask]:[user]:[resourceName]:[create]:[SUCCESS]. > In case of a large number of users to synchronize b is preferable, and > cumulative notification is sent. > Improve notification messages to show a better and more complete notification > message generated from jobs like SyncJob or PushJob and also provide new mail > and text templates useful for use case exposed above. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Issue Comment Deleted] (SYNCOPE-447) Provide the ability to have a single (cumulative) notification for task execution
[ https://issues.apache.org/jira/browse/SYNCOPE-447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli updated SYNCOPE-447: -- Comment: was deleted (was: Mechanism of creating cumulative notifications is already available by a proper configuration of notification. A simple use case is user synchronization; a) if we want to have a notification task for each user creation/update coming from sync task we can configure notification task to generate notification on this event [SyncTask]:[user]:[resourceName]:[create]:[SUCCESS]. b) But if we do not want to have too many notifications, like point 1, we can configure notification to create a notification task only when synchronization job finishes, setting notification event to [TASK]:[SyncJob]:[]:[SyncJob]:[SUCCESS] instead of [SyncTask]:[user]:[resourceName]:[create]:[SUCCESS]. In case of a large number of users to synchronize b is preferable, and cumulative notification is sent. We can instead improve notification messages to show a better and more complete notification message generated from jobs like SyncJob or PushJob and also provide new mail and text templates useful for use case exposed above. ) > Provide the ability to have a single (cumulative) notification for task > execution > - > > Key: SYNCOPE-447 > URL: https://issues.apache.org/jira/browse/SYNCOPE-447 > Project: Syncope > Issue Type: Improvement > Components: core >Affects Versions: 1.2.0 >Reporter: fabio martelli >Assignee: Andrea Patricelli > Fix For: 1.2.0 > > > A simple use case is user synchronization; > a) if we want to have a notification task for each user creation/update > coming from sync task we can configure notification task to generate > notification on this event > [SyncTask]:[user]:[resourceName]:[create]:[SUCCESS]. > b) But if we do not want to have too many notifications, like point 1, we can > configure notification to create a notification task only when > synchronization job finishes, setting notification event to > [TASK]:[SyncJob]:[]:[SyncJob]:[SUCCESS] instead of > [SyncTask]:[user]:[resourceName]:[create]:[SUCCESS]. > In case of a large number of users to synchronize b is preferable, and > cumulative notification is sent. > Improve notification messages to show a better and more complete notification > message generated from jobs like SyncJob or PushJob and also provide new mail > and text templates useful for use case exposed above. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (SYNCOPE-447) Provide the ability to have a single (cumulative) notification for task execution
[ https://issues.apache.org/jira/browse/SYNCOPE-447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli resolved SYNCOPE-447. --- Resolution: Fixed > Provide the ability to have a single (cumulative) notification for task > execution > - > > Key: SYNCOPE-447 > URL: https://issues.apache.org/jira/browse/SYNCOPE-447 > Project: Syncope > Issue Type: Improvement > Components: core >Affects Versions: 1.2.0 >Reporter: fabio martelli >Assignee: Andrea Patricelli > Fix For: 1.2.0 > > > A simple use case is user synchronization; > a) if we want to have a notification task for each user creation/update > coming from sync task we can configure notification task to generate > notification on this event > [SyncTask]:[user]:[resourceName]:[create]:[SUCCESS]. > b) But if we do not want to have too many notifications, like point 1, we can > configure notification to create a notification task only when > synchronization job finishes, setting notification event to > [TASK]:[SyncJob]:[]:[SyncJob]:[SUCCESS] instead of > [SyncTask]:[user]:[resourceName]:[create]:[SUCCESS]. > In case of a large number of users to synchronize b is preferable, and > cumulative notification is sent. > Improve notification messages to show a better and more complete notification > message generated from jobs like SyncJob or PushJob and also provide new mail > and text templates useful for use case exposed above. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (SYNCOPE-492) Provide possibility to activate/deactivate notifications
Andrea Patricelli created SYNCOPE-492: - Summary: Provide possibility to activate/deactivate notifications Key: SYNCOPE-492 URL: https://issues.apache.org/jira/browse/SYNCOPE-492 Project: Syncope Issue Type: Improvement Components: console, core Affects Versions: 1.2.0 Reporter: Andrea Patricelli Assignee: Andrea Patricelli Fix For: 1.2.0 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (SYNCOPE-492) Provide possibility to activate/deactivate notifications
[ https://issues.apache.org/jira/browse/SYNCOPE-492?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli resolved SYNCOPE-492. --- Resolution: Fixed > Provide possibility to activate/deactivate notifications > > > Key: SYNCOPE-492 > URL: https://issues.apache.org/jira/browse/SYNCOPE-492 > Project: Syncope > Issue Type: Improvement > Components: console, core >Affects Versions: 1.2.0 >Reporter: Andrea Patricelli >Assignee: Andrea Patricelli > Fix For: 1.2.0 > > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (SYNCOPE-493) Provide new user and role mapping purpose "NONE"
Andrea Patricelli created SYNCOPE-493: - Summary: Provide new user and role mapping purpose "NONE" Key: SYNCOPE-493 URL: https://issues.apache.org/jira/browse/SYNCOPE-493 Project: Syncope Issue Type: Improvement Components: console, core Affects Versions: 1.1.8, 1.2.0 Reporter: Andrea Patricelli Assignee: Andrea Patricelli Fix For: 1.1.8, 1.2.0 Provide new mapping purpose called "NONE" to ignore the mapping with such purpose; this avoids deletion of (temporarily) unuseful or not required user/role mappings. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (SYNCOPE-493) Provide new user and role mapping purpose "NONE"
[ https://issues.apache.org/jira/browse/SYNCOPE-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli updated SYNCOPE-493: -- Component/s: (was: core) common > Provide new user and role mapping purpose "NONE" > > > Key: SYNCOPE-493 > URL: https://issues.apache.org/jira/browse/SYNCOPE-493 > Project: Syncope > Issue Type: Improvement > Components: common, console >Affects Versions: 1.1.8, 1.2.0 >Reporter: Andrea Patricelli >Assignee: Andrea Patricelli > Fix For: 1.1.8, 1.2.0 > > > Provide new mapping purpose called "NONE" to ignore the mapping with such > purpose; this avoids deletion of (temporarily) unuseful or not required > user/role mappings. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (SYNCOPE-493) Provide new user and role mapping purpose "NONE"
[ https://issues.apache.org/jira/browse/SYNCOPE-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli updated SYNCOPE-493: -- Affects Version/s: (was: 1.1.8) > Provide new user and role mapping purpose "NONE" > > > Key: SYNCOPE-493 > URL: https://issues.apache.org/jira/browse/SYNCOPE-493 > Project: Syncope > Issue Type: Improvement > Components: common, console, core >Affects Versions: 1.2.0 >Reporter: Andrea Patricelli >Assignee: Andrea Patricelli > Fix For: 1.1.8, 1.2.0 > > > Provide new mapping purpose called "NONE" to ignore the mapping with such > purpose; this avoids deletion of (temporarily) unuseful or not required > user/role mappings. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (SYNCOPE-493) Provide new user and role mapping purpose "NONE"
[ https://issues.apache.org/jira/browse/SYNCOPE-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli updated SYNCOPE-493: -- Component/s: core > Provide new user and role mapping purpose "NONE" > > > Key: SYNCOPE-493 > URL: https://issues.apache.org/jira/browse/SYNCOPE-493 > Project: Syncope > Issue Type: Improvement > Components: common, console, core >Affects Versions: 1.1.8, 1.2.0 >Reporter: Andrea Patricelli >Assignee: Andrea Patricelli > Fix For: 1.1.8, 1.2.0 > > > Provide new mapping purpose called "NONE" to ignore the mapping with such > purpose; this avoids deletion of (temporarily) unuseful or not required > user/role mappings. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (SYNCOPE-493) Provide new user and role mapping purpose "NONE"
[ https://issues.apache.org/jira/browse/SYNCOPE-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli updated SYNCOPE-493: -- Fix Version/s: (was: 1.1.8) > Provide new user and role mapping purpose "NONE" > > > Key: SYNCOPE-493 > URL: https://issues.apache.org/jira/browse/SYNCOPE-493 > Project: Syncope > Issue Type: Improvement > Components: common, console, core >Affects Versions: 1.2.0 >Reporter: Andrea Patricelli >Assignee: Andrea Patricelli > Fix For: 1.2.0 > > > Provide new mapping purpose called "NONE" to ignore the mapping with such > purpose; this avoids deletion of (temporarily) unuseful or not required > user/role mappings. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (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
Andrea Patricelli created SYNCOPE-495: - Summary: 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 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-493) Provide new user and role mapping purpose "NONE"
[ https://issues.apache.org/jira/browse/SYNCOPE-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli resolved SYNCOPE-493. --- Resolution: Fixed > Provide new user and role mapping purpose "NONE" > > > Key: SYNCOPE-493 > URL: https://issues.apache.org/jira/browse/SYNCOPE-493 > Project: Syncope > Issue Type: Improvement > Components: common, console, core >Affects Versions: 1.2.0 >Reporter: Andrea Patricelli >Assignee: Andrea Patricelli > Fix For: 1.2.0 > > > Provide new mapping purpose called "NONE" to ignore the mapping with such > purpose; this avoids deletion of (temporarily) unuseful or not required > user/role mappings. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (SYNCOPE-467) Update notification docs with latest improvements
[ https://issues.apache.org/jira/browse/SYNCOPE-467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli reassigned SYNCOPE-467: - Assignee: Andrea Patricelli > Update notification docs with latest improvements > - > > Key: SYNCOPE-467 > URL: https://issues.apache.org/jira/browse/SYNCOPE-467 > Project: Syncope > Issue Type: Task > Components: documentation >Reporter: Francesco Chicchiriccò >Assignee: Andrea Patricelli > Fix For: 1.2.0 > > > As for SYNCOPE-463, reflect all improvements in the notification area to the > correspondent wiki pages. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (SYNCOPE-467) Update notification docs with latest improvements
[ https://issues.apache.org/jira/browse/SYNCOPE-467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli resolved SYNCOPE-467. --- Resolution: Fixed > Update notification docs with latest improvements > - > > Key: SYNCOPE-467 > URL: https://issues.apache.org/jira/browse/SYNCOPE-467 > Project: Syncope > Issue Type: Task > Components: documentation >Reporter: Francesco Chicchiriccò >Assignee: Andrea Patricelli > Fix For: 1.2.0 > > > As for SYNCOPE-463, reflect all improvements in the notification area to the > correspondent wiki pages. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (SYNCOPE-458) Change membership virtual attribute management
[ https://issues.apache.org/jira/browse/SYNCOPE-458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli reassigned SYNCOPE-458: - Assignee: Andrea Patricelli > Change membership virtual attribute management > -- > > Key: SYNCOPE-458 > URL: https://issues.apache.org/jira/browse/SYNCOPE-458 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 1.1.5 >Reporter: fabio martelli >Assignee: Andrea Patricelli > Fix For: 1.2.0 > > > Consider that memberships are not directly interested by a propagation. > Membership virtual attribute have to be considered like user virtual > attribute: > 1. retrieve membership virtual attribute values as done for user attributes > 2. manage membership virtual attributes during propagation (create/update) > 3. manage membership virtual attributes during membership remove -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Reopened] (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 ] Andrea Patricelli reopened SYNCOPE-495: --- 1) Open console 2) Open in edit mode an user with roles already assigned (as rossini) 3) click on role tab and open (from role tree) a role. 4) click cancel button and you will see that list of already assigned roles below disappears. > 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] [Updated] (SYNCOPE-499) Deletion of Role used as parent role in role template generate exception editing role template
[ https://issues.apache.org/jira/browse/SYNCOPE-499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli updated SYNCOPE-499: -- Affects Version/s: 1.2.0 > Deletion of Role used as parent role in role template generate exception > editing role template > -- > > Key: SYNCOPE-499 > URL: https://issues.apache.org/jira/browse/SYNCOPE-499 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 1.1.7, 1.2.0 > Environment: Apache Syncope 1.1.7 standalone distribution on Windows > 7 64bit and Oracle Java7 SE >Reporter: Denis Signoretto > > Steps to reproduce: > 1) Create a role > 2) Create a Synchronization Task and assign the previously created role as > parent role in the role template > 3) Delete previously created role > 4) Try edit role template > 5) Exception > Grave: Servlet.service() for servlet [syncope-core-rest] in context with path > [/syncope] threw exception [Request processing failed; nested exception is > org.apache.syncope.core.persistence.dao.NotFoundException: Role 152] with > root cause > org.apache.syncope.core.persistence.dao.NotFoundException: Role 152 > at > org.apache.syncope.core.rest.data.RoleDataBinder.getRoleFromId(RoleDataBinder.java:73) > at > org.apache.syncope.core.rest.data.RoleDataBinder$$FastClassBySpringCGLIB$$75f19568.invoke() > at > org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204) > at > org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:700) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (SYNCOPE-500) Wrong (unwanted) derived attribute insertion addition in membership modal page
Andrea Patricelli created SYNCOPE-500: - Summary: 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 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] [Created] (SYNCOPE-501) Virtual attribute propagation not working when updating only virtual attributes
Andrea Patricelli created SYNCOPE-501: - Summary: Virtual attribute propagation not working when updating only virtual attributes Key: SYNCOPE-501 URL: https://issues.apache.org/jira/browse/SYNCOPE-501 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.1.8, 1.2.0 Reporter: Andrea Patricelli Fix For: 1.1.8, 1.2.0 During User update, if updating ONLY mapped virtual attributes, are they really propagated? It seems that core doesn't track these changes and virtual attribute modifications (in this case) aren't propagated. If, instead, we update also other normal attribute(s), mapped with resource, virtual attributes changes are really propagated. Aren't modification made by solution of issue [1] enough to satisfy this requirement? [1] https://issues.apache.org/jira/browse/SYNCOPE-459 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (SYNCOPE-458) Change membership virtual attribute management
[ https://issues.apache.org/jira/browse/SYNCOPE-458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli resolved SYNCOPE-458. --- Resolution: Fixed > Change membership virtual attribute management > -- > > Key: SYNCOPE-458 > URL: https://issues.apache.org/jira/browse/SYNCOPE-458 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 1.1.5 >Reporter: fabio martelli >Assignee: Andrea Patricelli > Fix For: 1.2.0 > > > Consider that memberships are not directly interested by a propagation. > Membership virtual attribute have to be considered like user virtual > attribute: > 1. retrieve membership virtual attribute values as done for user attributes > 2. manage membership virtual attributes during propagation (create/update) > 3. manage membership virtual attributes during membership remove -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (SYNCOPE-501) Virtual attribute propagation not working when updating only virtual attributes
[ https://issues.apache.org/jira/browse/SYNCOPE-501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli reassigned SYNCOPE-501: - Assignee: Andrea Patricelli > Virtual attribute propagation not working when updating only virtual > attributes > --- > > Key: SYNCOPE-501 > URL: https://issues.apache.org/jira/browse/SYNCOPE-501 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 1.1.8, 1.2.0 >Reporter: Andrea Patricelli >Assignee: Andrea Patricelli > Fix For: 1.1.8, 1.2.0 > > > During User update, if updating ONLY mapped virtual attributes, are they > really propagated? > It seems that core doesn't track these changes and virtual attribute > modifications (in this case) aren't propagated. > If, instead, we update also other normal attribute(s), mapped with resource, > virtual attributes changes are really propagated. > Aren't modification made by solution of issue [1] enough to satisfy this > requirement? > [1] https://issues.apache.org/jira/browse/SYNCOPE-459 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SYNCOPE-501) Virtual attribute propagation not working when updating only virtual attributes
[ https://issues.apache.org/jira/browse/SYNCOPE-501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14026282#comment-14026282 ] Andrea Patricelli commented on SYNCOPE-501: --- It would be useful and not negligible to check this situation also for membership virtual attributes. > Virtual attribute propagation not working when updating only virtual > attributes > --- > > Key: SYNCOPE-501 > URL: https://issues.apache.org/jira/browse/SYNCOPE-501 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 1.1.8, 1.2.0 >Reporter: Andrea Patricelli >Assignee: Andrea Patricelli > Fix For: 1.1.8, 1.2.0 > > > During User update, if updating ONLY mapped virtual attributes, are they > really propagated? > It seems that core doesn't track these changes and virtual attribute > modifications (in this case) aren't propagated. > If, instead, we update also other normal attribute(s), mapped with resource, > virtual attributes changes are really propagated. > Aren't modification made by solution of issue [1] enough to satisfy this > requirement? > [1] https://issues.apache.org/jira/browse/SYNCOPE-459 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SYNCOPE-501) Virtual attribute propagation not working when updating only virtual attributes
[ https://issues.apache.org/jira/browse/SYNCOPE-501?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14027885#comment-14027885 ] Andrea Patricelli commented on SYNCOPE-501: --- A deep exploration of the code showed that changes made by SYNCOPE-459 are not enough, in fact if only virtual attributes are updated, code doesn't create propagation tasks necessary to propagation of virtual attributes, in other situations like update of username/password or update of normal attributes (mapped with the resource) , these tasks are created. So a patch is necessary to solve the problem. > Virtual attribute propagation not working when updating only virtual > attributes > --- > > Key: SYNCOPE-501 > URL: https://issues.apache.org/jira/browse/SYNCOPE-501 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 1.1.8, 1.2.0 >Reporter: Andrea Patricelli >Assignee: Andrea Patricelli > Fix For: 1.1.8, 1.2.0 > > > During User update, if updating ONLY mapped virtual attributes, are they > really propagated? > It seems that core doesn't track these changes and virtual attribute > modifications (in this case) aren't propagated. > If, instead, we update also other normal attribute(s), mapped with resource, > virtual attributes changes are really propagated. > Aren't modification made by solution of issue [1] enough to satisfy this > requirement? > [1] https://issues.apache.org/jira/browse/SYNCOPE-459 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (SYNCOPE-506) Connector configuration tab in connector modal page not accepting new values
Andrea Patricelli created SYNCOPE-506: - Summary: Connector configuration tab in connector modal page not accepting 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 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] [Updated] (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 ] Andrea Patricelli updated SYNCOPE-506: -- Summary: Connector configuration tab in connector modal page does not accept new values (was: Connector configuration tab in connector modal page not accepting new values) > 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 > 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] [Resolved] (SYNCOPE-501) Virtual attribute propagation not working when updating only virtual attributes
[ https://issues.apache.org/jira/browse/SYNCOPE-501?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli resolved SYNCOPE-501. --- Resolution: Fixed > Virtual attribute propagation not working when updating only virtual > attributes > --- > > Key: SYNCOPE-501 > URL: https://issues.apache.org/jira/browse/SYNCOPE-501 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 1.1.8, 1.2.0 >Reporter: Andrea Patricelli >Assignee: Andrea Patricelli > Fix For: 1.1.8, 1.2.0 > > > During User update, if updating ONLY mapped virtual attributes, are they > really propagated? > It seems that core doesn't track these changes and virtual attribute > modifications (in this case) aren't propagated. > If, instead, we update also other normal attribute(s), mapped with resource, > virtual attributes changes are really propagated. > Aren't modification made by solution of issue [1] enough to satisfy this > requirement? > [1] https://issues.apache.org/jira/browse/SYNCOPE-459 -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Assigned] (SYNCOPE-473) Provide configuration interface for push tasks
[ https://issues.apache.org/jira/browse/SYNCOPE-473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli reassigned SYNCOPE-473: - Assignee: Andrea Patricelli (was: fabio martelli) > Provide configuration interface for push tasks > -- > > Key: SYNCOPE-473 > URL: https://issues.apache.org/jira/browse/SYNCOPE-473 > Project: Syncope > Issue Type: Sub-task > Components: console >Affects Versions: 1.2.0 >Reporter: fabio martelli >Assignee: Andrea Patricelli > Fix For: 1.2.0 > > > Provide configuration interface for push tasks like done for sync and sched > tasks -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (SYNCOPE-509) In Task page after change of number of rows (to display) is erroneously added a column to tasks table
Andrea Patricelli created SYNCOPE-509: - Summary: 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 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] [Created] (SYNCOPE-510) Class cast exception in AbstractSearchPanel
Andrea Patricelli created SYNCOPE-510: - Summary: Class cast exception in AbstractSearchPanel Key: SYNCOPE-510 URL: https://issues.apache.org/jira/browse/SYNCOPE-510 Project: Syncope Issue Type: Bug Components: console Affects Versions: 1.2.0 Reporter: Andrea Patricelli Assignee: Andrea Patricelli Fix For: 1.2.0 1) Log into console 2) Go to Roles page and then move to search tab 3) search for roles with (or without) resources by selecting resource from search filter choice 4) click search button and you'll notice an Apache Wicket error page with message of ClassCastException in AbstractSearchFilter. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (SYNCOPE-510) Class cast exception in AbstractSearchPanel
[ https://issues.apache.org/jira/browse/SYNCOPE-510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli resolved SYNCOPE-510. --- Resolution: Fixed > Class cast exception in AbstractSearchPanel > --- > > Key: SYNCOPE-510 > URL: https://issues.apache.org/jira/browse/SYNCOPE-510 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 1.2.0 >Reporter: Andrea Patricelli >Assignee: Andrea Patricelli > Fix For: 1.2.0 > > > 1) Log into console > 2) Go to Roles page and then move to search tab > 3) search for roles with (or without) resources by selecting resource from > search filter choice > 4) click search button and you'll notice an Apache Wicket error page with > message of ClassCastException in AbstractSearchFilter. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (SYNCOPE-473) Provide configuration interface for push tasks
[ https://issues.apache.org/jira/browse/SYNCOPE-473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli resolved SYNCOPE-473. --- Resolution: Fixed When push action classes will be implemented AbstractSyncTaskModalPage needs only one localized adjustement as commented in code. > Provide configuration interface for push tasks > -- > > Key: SYNCOPE-473 > URL: https://issues.apache.org/jira/browse/SYNCOPE-473 > Project: Syncope > Issue Type: Sub-task > Components: console >Affects Versions: 1.2.0 >Reporter: fabio martelli >Assignee: Andrea Patricelli > Fix For: 1.2.0 > > > Provide configuration interface for push tasks like done for sync and sched > tasks -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Comment Edited] (SYNCOPE-473) Provide configuration interface for push tasks
[ https://issues.apache.org/jira/browse/SYNCOPE-473?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14038745#comment-14038745 ] Andrea Patricelli edited comment on SYNCOPE-473 at 6/20/14 12:41 PM: - When push action classes will be implemented AbstractSyncTaskModalPage needs only one localized adjustment as commented in code. was (Author: andrea.patricelli): When push action classes will be implemented AbstractSyncTaskModalPage needs only one localized adjustement as commented in code. > Provide configuration interface for push tasks > -- > > Key: SYNCOPE-473 > URL: https://issues.apache.org/jira/browse/SYNCOPE-473 > Project: Syncope > Issue Type: Sub-task > Components: console >Affects Versions: 1.2.0 >Reporter: fabio martelli >Assignee: Andrea Patricelli > Fix For: 1.2.0 > > > Provide configuration interface for push tasks like done for sync and sched > tasks -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (SYNCOPE-512) If there are no roles in edit user modal page is possible to create membership between root (fake) role and user
Andrea Patricelli created SYNCOPE-512: - Summary: If there are no roles in edit user modal page is possible to create membership between root (fake) role and user Key: SYNCOPE-512 URL: https://issues.apache.org/jira/browse/SYNCOPE-512 Project: Syncope Issue Type: Bug Components: console Affects Versions: 1.1.8, 1.2.0 Reporter: Andrea Patricelli Assignee: Andrea Patricelli Fix For: 1.1.8, 1.2.0 1) start Syncope in embedded mode and delete all roles or deploy syncope project with empty (default) content.xml 2) log into console and create an user. 3) go under roles tab in user modal page and click on empty role (the only displayed), a membership modal window is shown. 4) click on save button and you'll notice a NullPointerException. This is due to the fact that, if there are no roles, in edit user modal page is possible to create membership between root (fake) role and user and this is incorrect because root role is not useful for creating a membership. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (SYNCOPE-512) If there are no roles in edit user modal page is possible to create membership between root (fake) role and user
[ https://issues.apache.org/jira/browse/SYNCOPE-512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli updated SYNCOPE-512: -- Description: 1) start Syncope in embedded mode and delete all roles or deploy syncope project with empty (default) content.xml 2) log into console and create an user. 3) go under roles tab in user modal page and click on empty role (the only displayed), a membership modal window is shown. 4) click on save button and you'll notice a NullPointerException. This is due to the fact that, if there are no roles, in edit user modal page is possible to create membership between root (fake) role (the one with id 0) and user and this is incorrect because root role is not useful for creating a membership. was: 1) start Syncope in embedded mode and delete all roles or deploy syncope project with empty (default) content.xml 2) log into console and create an user. 3) go under roles tab in user modal page and click on empty role (the only displayed), a membership modal window is shown. 4) click on save button and you'll notice a NullPointerException. This is due to the fact that, if there are no roles, in edit user modal page is possible to create membership between root (fake) role and user and this is incorrect because root role is not useful for creating a membership. > If there are no roles in edit user modal page is possible to create > membership between root (fake) role and user > > > Key: SYNCOPE-512 > URL: https://issues.apache.org/jira/browse/SYNCOPE-512 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 1.1.8, 1.2.0 >Reporter: Andrea Patricelli >Assignee: Andrea Patricelli > Fix For: 1.1.8, 1.2.0 > > > 1) start Syncope in embedded mode and delete all roles or deploy syncope > project with empty (default) content.xml > 2) log into console and create an user. > 3) go under roles tab in user modal page and click on empty role (the only > displayed), a membership modal window is shown. > 4) click on save button and you'll notice a NullPointerException. > This is due to the fact that, if there are no roles, in edit user modal page > is possible to create membership between root (fake) role (the one with id 0) > and user and this is incorrect because root role is not useful for creating > a membership. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SYNCOPE-512) If there are no roles in edit user modal page is possible to create membership between root (fake) role and user
[ https://issues.apache.org/jira/browse/SYNCOPE-512?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14038839#comment-14038839 ] Andrea Patricelli commented on SYNCOPE-512: --- Fixed on branch with commit [1] [1] http://svn.apache.org/r1604174 > If there are no roles in edit user modal page is possible to create > membership between root (fake) role and user > > > Key: SYNCOPE-512 > URL: https://issues.apache.org/jira/browse/SYNCOPE-512 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 1.1.8, 1.2.0 >Reporter: Andrea Patricelli >Assignee: Andrea Patricelli > Fix For: 1.1.8, 1.2.0 > > > 1) start Syncope in embedded mode and delete all roles or deploy syncope > project with empty (default) content.xml > 2) log into console and create an user. > 3) go under roles tab in user modal page and click on empty role (the only > displayed), a membership modal window is shown. > 4) click on save button and you'll notice a NullPointerException. > This is due to the fact that, if there are no roles, in edit user modal page > is possible to create membership between root (fake) role (the one with id 0) > and user and this is incorrect because root role is not useful for creating > a membership. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (SYNCOPE-512) If there are no roles in edit user modal page is possible to create membership between root (fake) role and user
[ https://issues.apache.org/jira/browse/SYNCOPE-512?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli resolved SYNCOPE-512. --- Resolution: Fixed > If there are no roles in edit user modal page is possible to create > membership between root (fake) role and user > > > Key: SYNCOPE-512 > URL: https://issues.apache.org/jira/browse/SYNCOPE-512 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 1.1.8, 1.2.0 >Reporter: Andrea Patricelli >Assignee: Andrea Patricelli > Fix For: 1.1.8, 1.2.0 > > > 1) start Syncope in embedded mode and delete all roles or deploy syncope > project with empty (default) content.xml > 2) log into console and create an user. > 3) go under roles tab in user modal page and click on empty role (the only > displayed), a membership modal window is shown. > 4) click on save button and you'll notice a NullPointerException. > This is due to the fact that, if there are no roles, in edit user modal page > is possible to create membership between root (fake) role (the one with id 0) > and user and this is incorrect because root role is not useful for creating > a membership. -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Created] (SYNCOPE-516) Binary Schema UI enhancements
Andrea Patricelli created SYNCOPE-516: - Summary: Binary Schema UI enhancements Key: SYNCOPE-516 URL: https://issues.apache.org/jira/browse/SYNCOPE-516 Project: Syncope Issue Type: Improvement Components: console Affects Versions: 1.2.0 Reporter: Andrea Patricelli Assignee: Andrea Patricelli Fix For: 1.2.0 Binary schema enhancements: 1) Change text field to auto-complete text field to allow user to write whatever MIME type, but he has also the support of a complete and updated list of suggestions. 2) Display total byte count of the attribute in User UI. 3) Provide a pluggable binary viewer mechanism (as discussed in [1]) [1] http://syncope-user.1051894.n5.nabble.com/Certificates-in-Syncope-td5706704.html -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SYNCOPE-516) Binary Schema UI enhancements
[ https://issues.apache.org/jira/browse/SYNCOPE-516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14042159#comment-14042159 ] Andrea Patricelli commented on SYNCOPE-516: --- You are right, reading file size in edit mode would probably be inefficient. But since there are two arrows (upload/download) next to the attribute, we could, first of all, think to disable download link if attribute is not populated and so different opacity of download arrow can show us if there's some uploaded file or not (or even arrow could not be shown at all), WDYT? > Binary Schema UI enhancements > - > > Key: SYNCOPE-516 > URL: https://issues.apache.org/jira/browse/SYNCOPE-516 > Project: Syncope > Issue Type: Improvement > Components: console >Affects Versions: 1.2.0 >Reporter: Andrea Patricelli >Assignee: Andrea Patricelli > Fix For: 1.2.0 > > > Binary schema enhancements: > 1) Change text field to auto-complete text field to allow user to write > whatever MIME type, but he has also the support of a complete and updated > list of suggestions. > 2) Display total byte count of the attribute in User UI. > 3) Provide a pluggable binary viewer mechanism (as discussed in [1]) > [1] > http://syncope-user.1051894.n5.nabble.com/Certificates-in-Syncope-td5706704.html > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (SYNCOPE-516) Binary Schema UI enhancements
[ https://issues.apache.org/jira/browse/SYNCOPE-516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli updated SYNCOPE-516: -- Description: Binary schema enhancements: 1) Change text field to auto-complete text field to allow user to write whatever MIME type, but he has also the support of a complete and updated list of suggestions. 2) Display whether attribute has value or not, working on download arrow opacity. 3) Provide a pluggable binary viewer mechanism (as discussed in [1]) [1] http://syncope-user.1051894.n5.nabble.com/Certificates-in-Syncope-td5706704.html was: Binary schema enhancements: 1) Change text field to auto-complete text field to allow user to write whatever MIME type, but he has also the support of a complete and updated list of suggestions. 2) Display total byte count of the attribute in User UI. 3) Provide a pluggable binary viewer mechanism (as discussed in [1]) [1] http://syncope-user.1051894.n5.nabble.com/Certificates-in-Syncope-td5706704.html > Binary Schema UI enhancements > - > > Key: SYNCOPE-516 > URL: https://issues.apache.org/jira/browse/SYNCOPE-516 > Project: Syncope > Issue Type: Improvement > Components: console >Affects Versions: 1.2.0 >Reporter: Andrea Patricelli >Assignee: Andrea Patricelli > Fix For: 1.2.0 > > > Binary schema enhancements: > 1) Change text field to auto-complete text field to allow user to write > whatever MIME type, but he has also the support of a complete and updated > list of suggestions. > 2) Display whether attribute has value or not, working on download arrow > opacity. > 3) Provide a pluggable binary viewer mechanism (as discussed in [1]) > [1] > http://syncope-user.1051894.n5.nabble.com/Certificates-in-Syncope-td5706704.html > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SYNCOPE-516) Binary Schema UI enhancements
[ https://issues.apache.org/jira/browse/SYNCOPE-516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14042214#comment-14042214 ] Andrea Patricelli commented on SYNCOPE-516: --- Good, I'll update the issue. > Binary Schema UI enhancements > - > > Key: SYNCOPE-516 > URL: https://issues.apache.org/jira/browse/SYNCOPE-516 > Project: Syncope > Issue Type: Improvement > Components: console >Affects Versions: 1.2.0 >Reporter: Andrea Patricelli >Assignee: Andrea Patricelli > Fix For: 1.2.0 > > > Binary schema enhancements: > 1) Change text field to auto-complete text field to allow user to write > whatever MIME type, but he has also the support of a complete and updated > list of suggestions. > 2) Display whether attribute has value or not, working on download arrow > opacity. > 3) Provide a pluggable binary viewer mechanism (as discussed in [1]) > [1] > http://syncope-user.1051894.n5.nabble.com/Certificates-in-Syncope-td5706704.html > -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Resolved] (SYNCOPE-516) Binary Schema UI enhancements
[ https://issues.apache.org/jira/browse/SYNCOPE-516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli resolved SYNCOPE-516. --- Resolution: Fixed > Binary Schema UI enhancements > - > > Key: SYNCOPE-516 > URL: https://issues.apache.org/jira/browse/SYNCOPE-516 > Project: Syncope > Issue Type: Improvement > Components: console >Affects Versions: 1.2.0 >Reporter: Andrea Patricelli >Assignee: Andrea Patricelli > Fix For: 1.2.0 > > > Binary schema enhancements: > 1) Change text field to auto-complete text field to allow user to write > whatever MIME type, but he has also the support of a complete and updated > list of suggestions. > 2) Display whether attribute has value or not, working on download arrow > opacity. > 3) Provide a pluggable binary viewer mechanism (as discussed in [1]) > [1] > http://syncope-user.1051894.n5.nabble.com/Certificates-in-Syncope-td5706704.html > -- This message was sent by Atlassian JIRA (v6.2#6252)
