[jira] [Created] (SYNCOPE-1811) Missing Bypass MFA properties
Marco Di Sabatino Di Diodoro created SYNCOPE-1811: - Summary: Missing Bypass MFA properties Key: SYNCOPE-1811 URL: https://issues.apache.org/jira/browse/SYNCOPE-1811 Project: Syncope Issue Type: Improvement Components: wa Affects Versions: 3.0.6 Reporter: Marco Di Sabatino Di Diodoro Assignee: Marco Di Sabatino Di Diodoro Fix For: 3.0.7, 4.0.0 The authentication policy doesn't allow setting the parameters to bypass mfa module. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (SYNCOPE-1756) Add an id_token_hint parameter to the logout provider url for OIDC
Marco Di Sabatino Di Diodoro created SYNCOPE-1756: - Summary: Add an id_token_hint parameter to the logout provider url for OIDC Key: SYNCOPE-1756 URL: https://issues.apache.org/jira/browse/SYNCOPE-1756 Project: Syncope Issue Type: Bug Components: extensions Affects Versions: 2.1.13 Reporter: Marco Di Sabatino Di Diodoro Fix For: 2.1.14 Some OIDC providers also require the id_token_hint parameter in the logout url -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (SYNCOPE-1733) Support OAUTH20 authentication module in WA
[ https://issues.apache.org/jira/browse/SYNCOPE-1733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-1733. --- Resolution: Fixed > Support OAUTH20 authentication module in WA > --- > > Key: SYNCOPE-1733 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1733 > Project: Syncope > Issue Type: Improvement > Components: wa >Affects Versions: 3.0.2 >Reporter: Marco Di Sabatino Di Diodoro >Assignee: Marco Di Sabatino Di Diodoro >Priority: Major > Fix For: 3.0.3, 4.0.0 > > > Add the ability to create an OAuth 20 authentication module in WA -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (SYNCOPE-1733) Support OAUTH20 authentication module in WA
Marco Di Sabatino Di Diodoro created SYNCOPE-1733: - Summary: Support OAUTH20 authentication module in WA Key: SYNCOPE-1733 URL: https://issues.apache.org/jira/browse/SYNCOPE-1733 Project: Syncope Issue Type: Improvement Components: wa Affects Versions: 3.0.2 Reporter: Marco Di Sabatino Di Diodoro Assignee: Marco Di Sabatino Di Diodoro Fix For: 3.0.3 Add the ability to create an OAuth 20 authentication module in WA -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (SYNCOPE-1633) Give the possibility to add a custom message to the confirm dialog
Marco Di Sabatino Di Diodoro created SYNCOPE-1633: - Summary: Give the possibility to add a custom message to the confirm dialog Key: SYNCOPE-1633 URL: https://issues.apache.org/jira/browse/SYNCOPE-1633 Project: Syncope Issue Type: Improvement Components: console Affects Versions: 2.1.9 Reporter: Marco Di Sabatino Di Diodoro Assignee: Marco Di Sabatino Di Diodoro Fix For: 2.1.10, 3.0.0 In some cases it is not possible to specify the message to appear in the confirm dialog. In order to display a custom message the entire component must be overridden. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (SYNCOPE-1619) SearchPanel should display the input field based on the type of the selected property
[ https://issues.apache.org/jira/browse/SYNCOPE-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-1619. --- Resolution: Fixed > SearchPanel should display the input field based on the type of the selected > property > - > > Key: SYNCOPE-1619 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1619 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.1.8 >Reporter: Marco Di Sabatino Di Diodoro >Assignee: Marco Di Sabatino Di Diodoro >Priority: Minor > Fix For: 2.1.9, 3.0.0 > > > In the search panel, display the input field based on the type of the > selected property. > If the user selects an attribute of type date, the console will need to show > a date time picker. It will do the same thing for the other types as well. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (SYNCOPE-1619) SearchPanel should display the input field based on the type of the selected property
[ https://issues.apache.org/jira/browse/SYNCOPE-1619?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro updated SYNCOPE-1619: -- Summary: SearchPanel should display the input field based on the type of the selected property (was: SearchPanel display the input field based on the type of the selected property) > SearchPanel should display the input field based on the type of the selected > property > - > > Key: SYNCOPE-1619 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1619 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.1.8 >Reporter: Marco Di Sabatino Di Diodoro >Assignee: Marco Di Sabatino Di Diodoro >Priority: Minor > Fix For: 2.1.9, 3.0.0 > > > In the search panel, display the input field based on the type of the > selected property. > If the user selects an attribute of type date, the console will need to show > a date time picker. It will do the same thing for the other types as well. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (SYNCOPE-1619) SearchPanel display the input field based on the type of the selected property
Marco Di Sabatino Di Diodoro created SYNCOPE-1619: - Summary: SearchPanel display the input field based on the type of the selected property Key: SYNCOPE-1619 URL: https://issues.apache.org/jira/browse/SYNCOPE-1619 Project: Syncope Issue Type: Bug Components: console Affects Versions: 2.1.8 Reporter: Marco Di Sabatino Di Diodoro Assignee: Marco Di Sabatino Di Diodoro Fix For: 2.1.9, 3.0.0 In the search panel, display the input field based on the type of the selected property. If the user selects an attribute of type date, the console will need to show a date time picker. It will do the same thing for the other types as well. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (SYNCOPE-1606) Syncope returns an exception when doing two sequential operations for the same user from the toggle panel
[ https://issues.apache.org/jira/browse/SYNCOPE-1606?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-1606. --- Resolution: Fixed > Syncope returns an exception when doing two sequential operations for the > same user from the toggle panel > - > > Key: SYNCOPE-1606 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1606 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.1.8 >Reporter: Marco Di Sabatino Di Diodoro >Assignee: Marco Di Sabatino Di Diodoro >Priority: Minor > Fix For: 2.1.9, 3.0.0 > > > If we try to change the password for a user and then set the must change > password flag without reloading the toogle panel, Syncope returns an Etag > exception. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (SYNCOPE-1606) Syncope returns an exception when doing two sequential operations for the same user from the toggle panel
Marco Di Sabatino Di Diodoro created SYNCOPE-1606: - Summary: Syncope returns an exception when doing two sequential operations for the same user from the toggle panel Key: SYNCOPE-1606 URL: https://issues.apache.org/jira/browse/SYNCOPE-1606 Project: Syncope Issue Type: Bug Components: console Affects Versions: 2.1.8 Reporter: Marco Di Sabatino Di Diodoro Assignee: Marco Di Sabatino Di Diodoro Fix For: 2.1.9, 3.0.0 If we try to change the password for a user and then set the must change password flag without reloading the toogle panel, Syncope returns an Etag exception. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (SYNCOPE-1605) Syncope doesn't generate a propagation task if the update involves only the ConnectorObjectLink
[ https://issues.apache.org/jira/browse/SYNCOPE-1605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro updated SYNCOPE-1605: -- Summary: Syncope doesn't generate a propagation task if the update involves only the ConnectorObjectLink (was: Syncope doesnit generate a propagation task if the update involves only the ConnectorObjectLink) > Syncope doesn't generate a propagation task if the update involves only the > ConnectorObjectLink > --- > > Key: SYNCOPE-1605 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1605 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 2.1.7, 3.0.0 >Reporter: Marco Di Sabatino Di Diodoro >Assignee: Marco Di Sabatino Di Diodoro >Priority: Major > Fix For: 2.1.8, 3.0.0 > > > When updating an entity, syncope doesn't create a propagation task if the > modified attribute is not present in the mapping but only in the > connectorObjectLink -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (SYNCOPE-1605) Syncope doesnit generate a propagation task if the update involves only the ConnectorObjectLink
Marco Di Sabatino Di Diodoro created SYNCOPE-1605: - Summary: Syncope doesnit generate a propagation task if the update involves only the ConnectorObjectLink Key: SYNCOPE-1605 URL: https://issues.apache.org/jira/browse/SYNCOPE-1605 Project: Syncope Issue Type: Bug Components: core Affects Versions: 2.1.7, 3.0.0 Reporter: Marco Di Sabatino Di Diodoro Assignee: Marco Di Sabatino Di Diodoro Fix For: 2.1.8, 3.0.0 When updating an entity, syncope doesn't create a propagation task if the modified attribute is not present in the mapping but only in the connectorObjectLink -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (SYNCOPE-1604) AjaxDateTimePicker doesn't handle some 1900 dates the right way
Marco Di Sabatino Di Diodoro created SYNCOPE-1604: - Summary: AjaxDateTimePicker doesn't handle some 1900 dates the right way Key: SYNCOPE-1604 URL: https://issues.apache.org/jira/browse/SYNCOPE-1604 Project: Syncope Issue Type: Bug Components: console Affects Versions: 2.1.7 Reporter: Marco Di Sabatino Di Diodoro Fix For: 2.1.8, 3.0.0 Some dates from 1900 are not handled correctly by the picker. If you set the year to 20/11/1918 the picker transforms it into 20/11/2018. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (SYNCOPE-1575) Provide the ability to specify on which resources the user's status should be propagated
Marco Di Sabatino Di Diodoro created SYNCOPE-1575: - Summary: Provide the ability to specify on which resources the user's status should be propagated Key: SYNCOPE-1575 URL: https://issues.apache.org/jira/browse/SYNCOPE-1575 Project: Syncope Issue Type: Improvement Components: core Affects Versions: 2.1.6, 2.0.15 Reporter: Marco Di Sabatino Di Diodoro Fix For: 2.0.16, 3.0.0, 2.1.6 If only the state changes during a pull from a resource, Syncope doesn't propagate the change. It's necessary to improve the management of this use case by allowing to specify through the worklow tasks on which resources the state must be propagated. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (SYNCOPE-1548) Allow the possibility to customize the Groups wizard step
[ https://issues.apache.org/jira/browse/SYNCOPE-1548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-1548. --- Resolution: Fixed > Allow the possibility to customize the Groups wizard step > - > > Key: SYNCOPE-1548 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1548 > Project: Syncope > Issue Type: Improvement > Components: console >Affects Versions: 2.1.5 >Reporter: Marco Di Sabatino Di Diodoro >Assignee: Marco Di Sabatino Di Diodoro >Priority: Minor > Fix For: 2.1.6, 3.0.0 > > > Allow to customize the behavior of the components within this wizard step. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (SYNCOPE-1548) Allow the possibility to customize the Groups wizard step
Marco Di Sabatino Di Diodoro created SYNCOPE-1548: - Summary: Allow the possibility to customize the Groups wizard step Key: SYNCOPE-1548 URL: https://issues.apache.org/jira/browse/SYNCOPE-1548 Project: Syncope Issue Type: Improvement Components: console Affects Versions: 2.1.5 Reporter: Marco Di Sabatino Di Diodoro Assignee: Marco Di Sabatino Di Diodoro Fix For: 2.1.6, 3.0.0 Allow to customize the behavior of the components within this wizard step. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (SYNCOPE-1547) Allow the possibility to customize the roles to be displayed
[ https://issues.apache.org/jira/browse/SYNCOPE-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro updated SYNCOPE-1547: -- Fix Version/s: 3.0.0 2.1.6 > Allow the possibility to customize the roles to be displayed > > > Key: SYNCOPE-1547 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1547 > Project: Syncope > Issue Type: Improvement > Components: console >Affects Versions: 2.1.5 >Reporter: Marco Di Sabatino Di Diodoro >Assignee: Marco Di Sabatino Di Diodoro >Priority: Major > Fix For: 2.1.6, 3.0.0 > > > Make it possible to override the method to retrieve the roles to be displayed > on the wizard -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (SYNCOPE-1547) Allow the possibility to customize the roles to be displayed
[ https://issues.apache.org/jira/browse/SYNCOPE-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro updated SYNCOPE-1547: -- Component/s: console > Allow the possibility to customize the roles to be displayed > > > Key: SYNCOPE-1547 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1547 > Project: Syncope > Issue Type: Improvement > Components: console >Affects Versions: 2.1.5 >Reporter: Marco Di Sabatino Di Diodoro >Assignee: Marco Di Sabatino Di Diodoro >Priority: Major > > Make it possible to override the method to retrieve the roles to be displayed > on the wizard -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (SYNCOPE-1547) Allow the possibility to customize the roles to be displayed
[ https://issues.apache.org/jira/browse/SYNCOPE-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro updated SYNCOPE-1547: -- Affects Version/s: 2.1.5 > Allow the possibility to customize the roles to be displayed > > > Key: SYNCOPE-1547 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1547 > Project: Syncope > Issue Type: Improvement >Affects Versions: 2.1.5 >Reporter: Marco Di Sabatino Di Diodoro >Assignee: Marco Di Sabatino Di Diodoro >Priority: Major > > Make it possible to override the method to retrieve the roles to be displayed > on the wizard -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (SYNCOPE-1547) Allow the possibility to customize the roles to be displayed
Marco Di Sabatino Di Diodoro created SYNCOPE-1547: - Summary: Allow the possibility to customize the roles to be displayed Key: SYNCOPE-1547 URL: https://issues.apache.org/jira/browse/SYNCOPE-1547 Project: Syncope Issue Type: Improvement Reporter: Marco Di Sabatino Di Diodoro Assignee: Marco Di Sabatino Di Diodoro Make it possible to override the method to retrieve the roles to be displayed on the wizard -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (SYNCOPE-1538) Admin Console: users / groups management slow to access with high number of realms
[ https://issues.apache.org/jira/browse/SYNCOPE-1538?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17031101#comment-17031101 ] Marco Di Sabatino Di Diodoro commented on SYNCOPE-1538: --- The RoleWizardBuilder has a palette that still needs to be adapted. > Admin Console: users / groups management slow to access with high number of > realms > -- > > Key: SYNCOPE-1538 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1538 > Project: Syncope > Issue Type: Bug > Components: console, core >Affects Versions: 2.1.5 >Reporter: Francesco Chicchiriccò >Assignee: Marco Di Sabatino Di Diodoro >Priority: Major > Fix For: 2.1.6, 3.0.0 > > > When the number of available realms is high, using the Admin Console for > users or groups management becomes slow to access. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (SYNCOPE-1538) Admin Console: users / groups management slow to access with high number of realms
[ https://issues.apache.org/jira/browse/SYNCOPE-1538?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro reassigned SYNCOPE-1538: - Assignee: Marco Di Sabatino Di Diodoro > Admin Console: users / groups management slow to access with high number of > realms > -- > > Key: SYNCOPE-1538 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1538 > Project: Syncope > Issue Type: Bug > Components: console, core >Affects Versions: 2.1.5 >Reporter: Francesco Chicchiriccò >Assignee: Marco Di Sabatino Di Diodoro >Priority: Major > Fix For: 2.1.6, 3.0.0 > > > When the number of available realms is high, using the Admin Console for > users or groups management becomes slow to access. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (SYNCOPE-1522) Realm behaviors for Delegated Administration
[ https://issues.apache.org/jira/browse/SYNCOPE-1522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-1522. --- Resolution: Fixed > Realm behaviors for Delegated Administration > > > Key: SYNCOPE-1522 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1522 > Project: Syncope > Issue Type: Improvement > Components: console >Reporter: Francesco Chicchiriccò >Assignee: Marco Di Sabatino Di Diodoro >Priority: Major > Fix For: 2.1.6, 3.0.0 > > > A couple of improvements to apply for Delegated Administration scenarios, > dealing with Realms: > # show only the Realms the logged user can administer > # when clicking on the Realms left menu item, bring to the first Realm for > which administration rights are owned by the logged user -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (SYNCOPE-1521) Allow filtering for Role assignment
[ https://issues.apache.org/jira/browse/SYNCOPE-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-1521. --- Resolution: Fixed > Allow filtering for Role assignment > --- > > Key: SYNCOPE-1521 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1521 > Project: Syncope > Issue Type: Improvement > Components: console >Reporter: Francesco Chicchiriccò >Assignee: Marco Di Sabatino Di Diodoro >Priority: Major > Fix For: 2.1.6, 3.0.0 > > > During user edit there could be scenarios where the number of available Roles > is high and the current palette might not be handy: it could be the case to > use the same strategy already in place for Groups (first 30 elements shown, > with dedicated search field). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (SYNCOPE-1522) Realm behaviors for Delegated Administration
[ https://issues.apache.org/jira/browse/SYNCOPE-1522?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro reassigned SYNCOPE-1522: - Assignee: Marco Di Sabatino Di Diodoro > Realm behaviors for Delegated Administration > > > Key: SYNCOPE-1522 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1522 > Project: Syncope > Issue Type: Improvement > Components: console >Reporter: Francesco Chicchiriccò >Assignee: Marco Di Sabatino Di Diodoro >Priority: Major > Fix For: 2.1.6, 3.0.0 > > > A couple of improvements to apply for Delegated Administration scenarios, > dealing with Realms: > # show only the Realms the logged user can administer > # when clicking on the Realms left menu item, bring to the first Realm for > which administration rights are owned by the logged user -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Assigned] (SYNCOPE-1521) Allow filtering for Role assignment
[ https://issues.apache.org/jira/browse/SYNCOPE-1521?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro reassigned SYNCOPE-1521: - Assignee: Marco Di Sabatino Di Diodoro > Allow filtering for Role assignment > --- > > Key: SYNCOPE-1521 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1521 > Project: Syncope > Issue Type: Improvement > Components: console >Reporter: Francesco Chicchiriccò >Assignee: Marco Di Sabatino Di Diodoro >Priority: Major > Fix For: 2.1.6, 3.0.0 > > > During user edit there could be scenarios where the number of available Roles > is high and the current palette might not be handy: it could be the case to > use the same strategy already in place for Groups (first 30 elements shown, > with dedicated search field). -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (SYNCOPE-1504) Error setting uidOnCreate attribute during a pull task with multiple provisions
Marco Di Sabatino Di Diodoro created SYNCOPE-1504: - Summary: Error setting uidOnCreate attribute during a pull task with multiple provisions Key: SYNCOPE-1504 URL: https://issues.apache.org/jira/browse/SYNCOPE-1504 Project: Syncope Issue Type: Bug Components: core Affects Versions: 2.1.5 Reporter: Marco Di Sabatino Di Diodoro Assignee: Marco Di Sabatino Di Diodoro Fix For: 2.1.6, 3.0.0 If a uidOnCreate has been set and multiple provisions have been configured for the same resource, during a pull task Syncope raises an exception. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Resolved] (SYNCOPE-1481) Invalid values when saving a membership attribute of type date
[ https://issues.apache.org/jira/browse/SYNCOPE-1481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-1481. --- Resolution: Fixed > Invalid values when saving a membership attribute of type date > -- > > Key: SYNCOPE-1481 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1481 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.0.13, 2.1.4 >Reporter: Marco Di Sabatino Di Diodoro >Assignee: Marco Di Sabatino Di Diodoro >Priority: Major > Fix For: 2.0.14, 2.1.5, 3.0.0 > > > 1) Create a new schema of type date with date format -MM-dd > 2) Put the schema inside a AnyTypeClass > 3) Assign the AnyTypeClass to the group using a TypeExtension > 4) Create/Update an user and fill a value inside the new schema > Syncope returns this exception: > java.util.concurrent.ExecutionException: > org.apache.syncope.common.lib.SyncopeClientException: InvalidValues > [ParseException: Unparseable date: "Mon Aug 19 00:00:00 UTC 2019"] -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Assigned] (SYNCOPE-1481) Invalid values when saving a membership attribute of type date
[ https://issues.apache.org/jira/browse/SYNCOPE-1481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro reassigned SYNCOPE-1481: - Assignee: Marco Di Sabatino Di Diodoro (was: Andrea Patricelli) > Invalid values when saving a membership attribute of type date > -- > > Key: SYNCOPE-1481 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1481 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.0.13, 2.1.4 >Reporter: Marco Di Sabatino Di Diodoro >Assignee: Marco Di Sabatino Di Diodoro >Priority: Major > Fix For: 2.0.14, 2.1.5, 3.0.0 > > > 1) Create a new schema of type date with date format -MM-dd > 2) Put the schema inside a AnyTypeClass > 3) Assign the AnyTypeClass to the group using a TypeExtension > 4) Create/Update an user and fill a value inside the new schema > Syncope returns this exception: > java.util.concurrent.ExecutionException: > org.apache.syncope.common.lib.SyncopeClientException: InvalidValues > [ParseException: Unparseable date: "Mon Aug 19 00:00:00 UTC 2019"] -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Updated] (SYNCOPE-1481) Invalid values when saving a membership attribute of type date
[ https://issues.apache.org/jira/browse/SYNCOPE-1481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro updated SYNCOPE-1481: -- Component/s: console > Invalid values when saving a membership attribute of type date > -- > > Key: SYNCOPE-1481 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1481 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.0.13, 2.1.4 >Reporter: Marco Di Sabatino Di Diodoro >Priority: Major > Fix For: 2.0.14, 2.1.5 > > > 1) Create a new schema of type date with date format -MM-dd > 2) Put the schema inside a AnyTypeClass > 3) Assign the AnyTypeClass to the group using a TypeExtension > 4) Create/Update an user and fill a value inside the new schema > Syncope returns this exception: > java.util.concurrent.ExecutionException: > org.apache.syncope.common.lib.SyncopeClientException: InvalidValues > [ParseException: Unparseable date: "Mon Aug 19 00:00:00 UTC 2019"] -- This message was sent by Atlassian JIRA (v7.6.14#76016)
[jira] [Resolved] (SYNCOPE-1473) Provide a PropagationActions to maintain a conservative membership policy management
[ https://issues.apache.org/jira/browse/SYNCOPE-1473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-1473. --- Resolution: Fixed > Provide a PropagationActions to maintain a conservative membership policy > management > > > Key: SYNCOPE-1473 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1473 > Project: Syncope > Issue Type: Improvement > Components: core >Affects Versions: 2.0.13, 2.1.4 >Reporter: Marco Di Sabatino Di Diodoro >Assignee: Marco Di Sabatino Di Diodoro >Priority: Major > Fix For: 2.0.14, 2.1.5, 3.0.0 > > > If a user has a group assigned on LDAP or AD, but the group is not managed by > Syncope, during the modification of the user, Syncope removes the assignment. > Give the possibility to provide a conservative management and assignment of > groups to user on the resource when the group is not managed from Syncope. > The groups already assigned to an user on LDAP or AD will not be removed if > the group is not managed from Syncope. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SYNCOPE-1473) Provide a PropagationActions to maintain a conservative membership policy management
[ https://issues.apache.org/jira/browse/SYNCOPE-1473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro reassigned SYNCOPE-1473: - Assignee: Marco Di Sabatino Di Diodoro > Provide a PropagationActions to maintain a conservative membership policy > management > > > Key: SYNCOPE-1473 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1473 > Project: Syncope > Issue Type: Improvement > Components: core >Affects Versions: 2.0.13, 2.1.4 >Reporter: Marco Di Sabatino Di Diodoro >Assignee: Marco Di Sabatino Di Diodoro >Priority: Major > Fix For: 2.0.14, 2.1.5, 3.0.0 > > > If a user has a group assigned on LDAP or AD, but the group is not managed by > Syncope, during the modification of the user, Syncope removes the assignment. > Give the possibility to provide a conservative management and assignment of > groups to user on the resource when the group is not managed from Syncope. > The groups already assigned to an user on LDAP or AD will not be removed if > the group is not managed from Syncope. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SYNCOPE-1473) Provide a PropagationActions to maintain a conservative membership policy management
Marco Di Sabatino Di Diodoro created SYNCOPE-1473: - Summary: Provide a PropagationActions to maintain a conservative membership policy management Key: SYNCOPE-1473 URL: https://issues.apache.org/jira/browse/SYNCOPE-1473 Project: Syncope Issue Type: Improvement Components: core Affects Versions: 2.1.4, 2.0.13 Reporter: Marco Di Sabatino Di Diodoro Fix For: 2.0.14, 2.1.5, 3.0.0 If a user has a group assigned on LDAP or AD, but the group is not managed by Syncope, during the modification of the user, Syncope removes the assignment. Give the possibility to provide a conservative management and assignment of groups to user on the resource when the group is not managed from Syncope. The groups already assigned to an user on LDAP or AD will not be removed if the group is not managed from Syncope. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SYNCOPE-1467) RDN not allowed when an attribute of the group present also in the DN is changed
[
https://issues.apache.org/jira/browse/SYNCOPE-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Di Sabatino Di Diodoro resolved SYNCOPE-1467.
---
Resolution: Fixed
> RDN not allowed when an attribute of the group present also in the DN is
> changed
>
>
> Key: SYNCOPE-1467
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1467
> Project: Syncope
> Issue Type: Bug
> Components: core
>Affects Versions: 2.0.13, 2.1.4
>Reporter: Marco Di Sabatino Di Diodoro
>Assignee: Marco Di Sabatino Di Diodoro
>Priority: Major
> Fix For: 2.0.14, 2.1.5, 3.0.0
>
>
> During rename of a group with LDAP resource assigned, Syncope returns an
> exception
> {code}
> javax.naming.directory.SchemaViolationException: [LDAP: error code 67 -
> NOT_ALLOWED_ON_RDN: failed for MessageType : MODIFY_REQUEST
> Message ID : 66
> Modify Request
> Object : 'cn=testLDAPGroup,ou=groups,o=isp'
> Modification[0]
> Operation : replace
> Modification
> owner: (null)Modification[1]
> Operation : replace
> Modification
> description: (null)Modification[2]
> Operation : replace
> Modification
> cn:
> testLDAPGroup2org.apache.directory.api.ldap.model.message.ModifyRequestImpl@9aac12bb:
> ERR_62 Entry cn=testLDAPGroup,ou=groups,o=isp does not have the cn
> attributeType, which is part of the RDN";]; remaining name
> 'cn=testLDAPGroup,ou=groups,o=isp'
> Cause: [LDAP: error code 67 - NOT_ALLOWED_ON_RDN: failed for MessageType :
> MODIFY_REQUEST
> {code}
> To replicate the issue with test data:
> # pull from resource-ldap
> # assign the group {{testLDAPGroup}} to {{resource-ldap}}
> # rename {{testLDAPGroup}} to {{testLDAPGroup2}}
> # propagation error
> With a {{ldapmodify}} it's possible to rename the group
> {code}
> dn: cn=aGroupForPropagation,ou=Groups,o=isp
> changetype: moddn
> newrdn: cn=aGroupForPropagation1
> deleteoldrdn: 1
> newsuperior: ou=Groups,o=isp
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Reopened] (SYNCOPE-1467) RDN not allowed when an attribute of the group present also in the DN is changed
[
https://issues.apache.org/jira/browse/SYNCOPE-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Di Sabatino Di Diodoro reopened SYNCOPE-1467:
---
> RDN not allowed when an attribute of the group present also in the DN is
> changed
>
>
> Key: SYNCOPE-1467
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1467
> Project: Syncope
> Issue Type: Bug
> Components: core
>Affects Versions: 2.0.13, 2.1.4
>Reporter: Marco Di Sabatino Di Diodoro
>Assignee: Marco Di Sabatino Di Diodoro
>Priority: Major
> Fix For: 2.0.14, 2.1.5, 3.0.0
>
>
> During rename of a group with LDAP resource assigned, Syncope returns an
> exception
> {code}
> javax.naming.directory.SchemaViolationException: [LDAP: error code 67 -
> NOT_ALLOWED_ON_RDN: failed for MessageType : MODIFY_REQUEST
> Message ID : 66
> Modify Request
> Object : 'cn=testLDAPGroup,ou=groups,o=isp'
> Modification[0]
> Operation : replace
> Modification
> owner: (null)Modification[1]
> Operation : replace
> Modification
> description: (null)Modification[2]
> Operation : replace
> Modification
> cn:
> testLDAPGroup2org.apache.directory.api.ldap.model.message.ModifyRequestImpl@9aac12bb:
> ERR_62 Entry cn=testLDAPGroup,ou=groups,o=isp does not have the cn
> attributeType, which is part of the RDN";]; remaining name
> 'cn=testLDAPGroup,ou=groups,o=isp'
> Cause: [LDAP: error code 67 - NOT_ALLOWED_ON_RDN: failed for MessageType :
> MODIFY_REQUEST
> {code}
> To replicate the issue with test data:
> # pull from resource-ldap
> # assign the group {{testLDAPGroup}} to {{resource-ldap}}
> # rename {{testLDAPGroup}} to {{testLDAPGroup2}}
> # propagation error
> With a {{ldapmodify}} it's possible to rename the group
> {code}
> dn: cn=aGroupForPropagation,ou=Groups,o=isp
> changetype: moddn
> newrdn: cn=aGroupForPropagation1
> deleteoldrdn: 1
> newsuperior: ou=Groups,o=isp
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Resolved] (SYNCOPE-1467) RDN not allowed when an attribute of the group present also in the DN is changed
[
https://issues.apache.org/jira/browse/SYNCOPE-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Di Sabatino Di Diodoro resolved SYNCOPE-1467.
---
Resolution: Fixed
> RDN not allowed when an attribute of the group present also in the DN is
> changed
>
>
> Key: SYNCOPE-1467
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1467
> Project: Syncope
> Issue Type: Bug
> Components: core
>Affects Versions: 2.0.13, 2.1.4
>Reporter: Marco Di Sabatino Di Diodoro
>Assignee: Marco Di Sabatino Di Diodoro
>Priority: Major
> Fix For: 2.0.14, 2.1.5, 3.0.0
>
>
> During rename of a group with LDAP resource assigned, Syncope returns an
> exception
> {code}
> javax.naming.directory.SchemaViolationException: [LDAP: error code 67 -
> NOT_ALLOWED_ON_RDN: failed for MessageType : MODIFY_REQUEST
> Message ID : 66
> Modify Request
> Object : 'cn=testLDAPGroup,ou=groups,o=isp'
> Modification[0]
> Operation : replace
> Modification
> owner: (null)Modification[1]
> Operation : replace
> Modification
> description: (null)Modification[2]
> Operation : replace
> Modification
> cn:
> testLDAPGroup2org.apache.directory.api.ldap.model.message.ModifyRequestImpl@9aac12bb:
> ERR_62 Entry cn=testLDAPGroup,ou=groups,o=isp does not have the cn
> attributeType, which is part of the RDN";]; remaining name
> 'cn=testLDAPGroup,ou=groups,o=isp'
> Cause: [LDAP: error code 67 - NOT_ALLOWED_ON_RDN: failed for MessageType :
> MODIFY_REQUEST
> {code}
> To replicate the issue with test data:
> # pull from resource-ldap
> # assign the group {{testLDAPGroup}} to {{resource-ldap}}
> # rename {{testLDAPGroup}} to {{testLDAPGroup2}}
> # propagation error
> With a {{ldapmodify}} it's possible to rename the group
> {code}
> dn: cn=aGroupForPropagation,ou=Groups,o=isp
> changetype: moddn
> newrdn: cn=aGroupForPropagation1
> deleteoldrdn: 1
> newsuperior: ou=Groups,o=isp
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (SYNCOPE-1467) RDN not allowed when an attribute of the group present also in the DN is changed
[
https://issues.apache.org/jira/browse/SYNCOPE-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Di Sabatino Di Diodoro reassigned SYNCOPE-1467:
-
Assignee: Marco Di Sabatino Di Diodoro
> RDN not allowed when an attribute of the group present also in the DN is
> changed
>
>
> Key: SYNCOPE-1467
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1467
> Project: Syncope
> Issue Type: Bug
> Components: core
>Affects Versions: 2.0.13, 2.1.4
>Reporter: Marco Di Sabatino Di Diodoro
>Assignee: Marco Di Sabatino Di Diodoro
>Priority: Major
> Fix For: 2.0.14, 2.1.5, 3.0.0
>
>
> During rename of a group with LDAP resource assigned, Syncope returns an
> exception
> {code}
> javax.naming.directory.SchemaViolationException: [LDAP: error code 67 -
> NOT_ALLOWED_ON_RDN: failed for MessageType : MODIFY_REQUEST
> Message ID : 66
> Modify Request
> Object : 'cn=testLDAPGroup,ou=groups,o=isp'
> Modification[0]
> Operation : replace
> Modification
> owner: (null)Modification[1]
> Operation : replace
> Modification
> description: (null)Modification[2]
> Operation : replace
> Modification
> cn:
> testLDAPGroup2org.apache.directory.api.ldap.model.message.ModifyRequestImpl@9aac12bb:
> ERR_62 Entry cn=testLDAPGroup,ou=groups,o=isp does not have the cn
> attributeType, which is part of the RDN";]; remaining name
> 'cn=testLDAPGroup,ou=groups,o=isp'
> Cause: [LDAP: error code 67 - NOT_ALLOWED_ON_RDN: failed for MessageType :
> MODIFY_REQUEST
> {code}
> To replicate the issue with test data:
> # pull from resource-ldap
> # assign the group {{testLDAPGroup}} to {{resource-ldap}}
> # rename {{testLDAPGroup}} to {{testLDAPGroup2}}
> # propagation error
> With a {{ldapmodify}} it's possible to rename the group
> {code}
> dn: cn=aGroupForPropagation,ou=Groups,o=isp
> changetype: moddn
> newrdn: cn=aGroupForPropagation1
> deleteoldrdn: 1
> newsuperior: ou=Groups,o=isp
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SYNCOPE-1467) RDN not allowed when an attribute of the group present also in the DN is changed
[
https://issues.apache.org/jira/browse/SYNCOPE-1467?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16833625#comment-16833625
]
Marco Di Sabatino Di Diodoro commented on SYNCOPE-1467:
---
The issue will be resolved on the ldap connector
https://connid.atlassian.net/projects/LDAP/issues/LDAP-28
> RDN not allowed when an attribute of the group present also in the DN is
> changed
>
>
> Key: SYNCOPE-1467
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1467
> Project: Syncope
> Issue Type: Bug
> Components: core
>Affects Versions: 2.0.13, 2.1.4
>Reporter: Marco Di Sabatino Di Diodoro
>Priority: Major
> Fix For: 2.0.14, 2.1.5, 3.0.0
>
>
> During rename of a group with LDAP resource assigned, Syncope returns an
> exception
> {code}
> javax.naming.directory.SchemaViolationException: [LDAP: error code 67 -
> NOT_ALLOWED_ON_RDN: failed for MessageType : MODIFY_REQUEST
> Message ID : 66
> Modify Request
> Object : 'cn=testLDAPGroup,ou=groups,o=isp'
> Modification[0]
> Operation : replace
> Modification
> owner: (null)Modification[1]
> Operation : replace
> Modification
> description: (null)Modification[2]
> Operation : replace
> Modification
> cn:
> testLDAPGroup2org.apache.directory.api.ldap.model.message.ModifyRequestImpl@9aac12bb:
> ERR_62 Entry cn=testLDAPGroup,ou=groups,o=isp does not have the cn
> attributeType, which is part of the RDN";]; remaining name
> 'cn=testLDAPGroup,ou=groups,o=isp'
> Cause: [LDAP: error code 67 - NOT_ALLOWED_ON_RDN: failed for MessageType :
> MODIFY_REQUEST
> {code}
> To replicate the issue with test data:
> # pull from resource-ldap
> # assign the group {{testLDAPGroup}} to {{resource-ldap}}
> # rename {{testLDAPGroup}} to {{testLDAPGroup2}}
> # propagation error
> With a {{ldapmodify}} it's possible to rename the group
> {code}
> dn: cn=aGroupForPropagation,ou=Groups,o=isp
> changetype: moddn
> newrdn: cn=aGroupForPropagation1
> deleteoldrdn: 1
> newsuperior: ou=Groups,o=isp
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (SYNCOPE-1467) RDN not allowed when an attribute of the group present also in the DN is changed
Marco Di Sabatino Di Diodoro created SYNCOPE-1467: - Summary: RDN not allowed when an attribute of the group present also in the DN is changed Key: SYNCOPE-1467 URL: https://issues.apache.org/jira/browse/SYNCOPE-1467 Project: Syncope Issue Type: Bug Components: core Affects Versions: 2.1.4, 2.0.13 Reporter: Marco Di Sabatino Di Diodoro Fix For: 2.0.14, 2.1.5 During update of an attribute of a group, for example cn, Syncope returns an exception javax.naming.directory.SchemaViolationException: [LDAP: error code 67 - NOT_ALLOWED_ON_RDN: failed for MessageType : MODIFY_REQUEST Message ID : 41 Modify Request Object : 'cn=aGroupForPropagation2,ou=groups,o=isp' Modification[0] Operation : replace Modification owner: (null) Modification[1] Operation : replace Modification description: r12 Modification[2] Operation : replace Modification cn: aGroupForPropagation3org.apache.directory.api.ldap.model.message.ModifyRequestImpl@51d29a89: ERR_62 Entry cn=aGroupForPropagation2,ou=groups,o=isp does not have the cn attributeType, which is part of the RDN";]; remaining name 'cn=aGroupForPropagation2,ou=groups,o=isp' Cause: [LDAP: error code 67 - NOT_ALLOWED_ON_RDN: failed for MessageType : MODIFY_REQUEST To replicate the issue: # pull from resource-ldap 2. assign the grupp testLDAPGroup to resource-ldap 3. rename di testLDAPGroup in testLDAPGroup2 4. propagation error With a ldapmodify it's possible to rename the group dn: cn=aGroupForPropagation,ou=Groups,o=isp changetype: moddn newrdn: cn=aGroupForPropagation1 deleteoldrdn: 1 newsuperior: ou=Groups,o=isp -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SYNCOPE-1365) Erorr during retrieve candidate groups for approval process
[ https://issues.apache.org/jira/browse/SYNCOPE-1365?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-1365. --- Resolution: Fixed > Erorr during retrieve candidate groups for approval process > --- > > Key: SYNCOPE-1365 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1365 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 2.1.1 >Reporter: Marco Di Sabatino Di Diodoro >Priority: Major > Fix For: 2.1.2, 3.0.0 > > > NullPointer exception during approval process -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SYNCOPE-1365) Erorr during retrieve candidate groups for approval process
Marco Di Sabatino Di Diodoro created SYNCOPE-1365: - Summary: Erorr during retrieve candidate groups for approval process Key: SYNCOPE-1365 URL: https://issues.apache.org/jira/browse/SYNCOPE-1365 Project: Syncope Issue Type: Bug Components: core Affects Versions: 2.1.1 Reporter: Marco Di Sabatino Di Diodoro Fix For: 2.1.2, 3.0.0 NullPointer exception during approval process -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SYNCOPE-1352) Group wizard doesn't update the plain attributes
[ https://issues.apache.org/jira/browse/SYNCOPE-1352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-1352. --- Resolution: Fixed > Group wizard doesn't update the plain attributes > > > Key: SYNCOPE-1352 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1352 > Project: Syncope > Issue Type: Improvement > Components: console >Affects Versions: 2.0.9, 2.1.0 >Reporter: Marco Di Sabatino Di Diodoro >Assignee: Marco Di Sabatino Di Diodoro >Priority: Major > Fix For: 2.0.10, 2.1.1 > > > The update of a group from the console builds a patch without plain attributes -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SYNCOPE-1352) Group wizard doesn't update the plain attributes
[ https://issues.apache.org/jira/browse/SYNCOPE-1352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro reassigned SYNCOPE-1352: - Assignee: Marco Di Sabatino Di Diodoro > Group wizard doesn't update the plain attributes > > > Key: SYNCOPE-1352 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1352 > Project: Syncope > Issue Type: Improvement > Components: console >Affects Versions: 2.0.9, 2.1.0 >Reporter: Marco Di Sabatino Di Diodoro >Assignee: Marco Di Sabatino Di Diodoro >Priority: Major > Fix For: 2.0.10, 2.1.1 > > > The update of a group from the console builds a patch without plain attributes -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SYNCOPE-1352) Group wizard doesn't update the plain attributes
Marco Di Sabatino Di Diodoro created SYNCOPE-1352: - Summary: Group wizard doesn't update the plain attributes Key: SYNCOPE-1352 URL: https://issues.apache.org/jira/browse/SYNCOPE-1352 Project: Syncope Issue Type: Improvement Components: console Affects Versions: 2.1.0, 2.0.9 Reporter: Marco Di Sabatino Di Diodoro Fix For: 2.0.10, 2.1.1 The update of a group from the console builds a patch without plain attributes -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SYNCOPE-1336) Add pagination for approvals forms
Marco Di Sabatino Di Diodoro created SYNCOPE-1336: - Summary: Add pagination for approvals forms Key: SYNCOPE-1336 URL: https://issues.apache.org/jira/browse/SYNCOPE-1336 Project: Syncope Issue Type: Improvement Components: core Affects Versions: 2.1.0, 2.0.9 Reporter: Marco Di Sabatino Di Diodoro Fix For: 2.0.10, 2.1.1 If there are many approval tasks, the console takes a long time to load all the forms. It's necessary to add pagination in the query. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SYNCOPE-1326) Wizard generates unnecessary attrPatch when the field is empty
[ https://issues.apache.org/jira/browse/SYNCOPE-1326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-1326. --- Resolution: Fixed > Wizard generates unnecessary attrPatch when the field is empty > -- > > Key: SYNCOPE-1326 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1326 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.0.8, 2.1.0 >Reporter: Marco Di Sabatino Di Diodoro >Assignee: Marco Di Sabatino Di Diodoro >Priority: Major > Fix For: 2.0.9, 2.1.0 > > > In particular, if the attribute value is empty and its value has not changed, > Syncope always generates an attrPatch for that field. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SYNCOPE-1326) Wizard generates unnecessary attrPatch when the field is empty
[ https://issues.apache.org/jira/browse/SYNCOPE-1326?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro reassigned SYNCOPE-1326: - Assignee: Marco Di Sabatino Di Diodoro > Wizard generates unnecessary attrPatch when the field is empty > -- > > Key: SYNCOPE-1326 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1326 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.0.8, 2.1.0 >Reporter: Marco Di Sabatino Di Diodoro >Assignee: Marco Di Sabatino Di Diodoro >Priority: Major > Fix For: 2.0.9, 2.1.0 > > > In particular, if the attribute value is empty and its value has not changed, > Syncope always generates an attrPatch for that field. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SYNCOPE-1326) Wizard generates unnecessary attrPatch when the field is empty
Marco Di Sabatino Di Diodoro created SYNCOPE-1326: - Summary: Wizard generates unnecessary attrPatch when the field is empty Key: SYNCOPE-1326 URL: https://issues.apache.org/jira/browse/SYNCOPE-1326 Project: Syncope Issue Type: Bug Components: console Affects Versions: 2.0.8, 2.1.0 Reporter: Marco Di Sabatino Di Diodoro Fix For: 2.0.9, 2.1.0 In particular, if the attribute value is empty and its value has not changed, Syncope always generates an attrPatch for that field. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SYNCOPE-681) i18n labels for schema names
[ https://issues.apache.org/jira/browse/SYNCOPE-681?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro reassigned SYNCOPE-681: Assignee: Marco Di Sabatino Di Diodoro (was: Francesco Chicchiriccò) > i18n labels for schema names > > > Key: SYNCOPE-681 > URL: https://issues.apache.org/jira/browse/SYNCOPE-681 > Project: Syncope > Issue Type: Improvement >Reporter: Francesco Chicchiriccò >Assignee: Marco Di Sabatino Di Diodoro >Priority: Major > Fix For: 2.1.0 > > > Schema names can be "ugly" text, but there should be a REST service providing > optional i18n labels. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SYNCOPE-1318) Future task rejected from ScheduledThreadPoolExecutor
Marco Di Sabatino Di Diodoro created SYNCOPE-1318: - Summary: Future task rejected from ScheduledThreadPoolExecutor Key: SYNCOPE-1318 URL: https://issues.apache.org/jira/browse/SYNCOPE-1318 Project: Syncope Issue Type: Bug Components: console Affects Versions: 2.0.8 Reporter: Marco Di Sabatino Di Diodoro Fix For: 2.0.9, 2.1.0 After several operations on the console, the connection pool to the core ends and doesn't allows to perform other operations ERROR org.apache.syncope.client.console.wizards.AjaxWizard - Wizard error on finish java.util.concurrent.RejectedExecutionException: Task java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask@561b0d9e rejected from java.util.concurrent.ScheduledThreadPoolExecutor@73c6df51[Terminated, pool size = 0, active threads = 0, queued tasks = 0, completed tasks = 1] at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2063) ~[?:1.8.0_151] at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:830) ~[?:1.8.0_151] at java.util.concurrent.ScheduledThreadPoolExecutor.delayedExecute(ScheduledThreadPoolExecutor.java:326) ~[?:1.8.0_151] at java.util.concurrent.ScheduledThreadPoolExecutor.schedule(ScheduledThreadPoolExecutor.java:549) ~[?:1.8.0_151] at java.util.concurrent.ScheduledThreadPoolExecutor.submit(ScheduledThreadPoolExecutor.java:648) ~[?:1.8.0_151] at org.apache.syncope.client.console.SyncopeConsoleSession.execute(SyncopeConsoleSession.java:128) ~[classes/:2.0.8] at org.apache.syncope.client.console.wizards.AjaxWizard.onApply(AjaxWizard.java:383) ~[syncope-client-console-2.0.8.jar:2.0.8] at org.apache.syncope.client.console.wizards.AjaxWizard.onFinish(AjaxWizard.java:198) ~[syncope-client-console-2.0.8.jar:2.0.8] at org.apache.wicket.extensions.wizard.AbstractWizardModel.fireWizardFinished(AbstractWizardModel.java:182) ~[wicket-extensions-7.10.0.jar:7.10.0] at org.apache.wicket.extensions.wizard.AbstractWizardModel.finish(AbstractWizardModel.java:88) ~[wicket-extensions-7.10.0.jar:7.10.0] at org.apache.wicket.extensions.wizard.FinishButton.onClick(FinishButton.java:68) ~[wicket-extensions-7.10.0.jar:7.10.0] at org.apache.wicket.extensions.wizard.WizardButton.onSubmit(WizardButton.java:88) ~[wicket-extensions-7.10.0.jar:7.10.0] at org.apache.syncope.client.console.wizards.AjaxWizardMgtButtonBar$1.onSubmit(AjaxWizardMgtButtonBar.java:80) ~[syncope-client-console-2.0.8.jar:2.0.8] at org.apache.wicket.ajax.form.AjaxFormSubmitBehavior$AjaxFormSubmitter.onSubmit(AjaxFormSubmitBehavior.java:218) ~[wicket-core-7.10.0.jar:7.10.0] at org.apache.wicket.markup.html.form.Form.delegateSubmit(Form.java:1311) ~[wicket-core-7.10.0.jar:7.10.0] at org.apache.wicket.markup.html.form.Form.process(Form.java:977) ~[wicket-core-7.10.0.jar:7.10.0] at org.apache.wicket.markup.html.form.Form.onFormSubmitted(Form.java:798) ~[wicket-core-7.10.0.jar:7.10.0] at org.apache.wicket.ajax.form.AjaxFormSubmitBehavior.onEvent(AjaxFormSubmitBehavior.java:174) ~[wicket-core-7.10.0.jar:7.10.0] at org.apache.wicket.ajax.AjaxEventBehavior.respond(AjaxEventBehavior.java:155) ~[wicket-core-7.10.0.jar:7.10.0] at org.apache.wicket.ajax.AbstractDefaultAjaxBehavior.onRequest(AbstractDefaultAjaxBehavior.java:601) ~[wicket-core-7.10.0.jar:7.10.0] at sun.reflect.GeneratedMethodAccessor343.invoke(Unknown Source) ~[?:?] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) ~[?:1.8.0_151] at java.lang.reflect.Method.invoke(Method.java:498) ~[?:1.8.0_151] at org.apache.wicket.RequestListenerInterface.internalInvoke(RequestListenerInterface.java:258) ~[wicket-core-7.10.0.jar:7.10.0] at org.apache.wicket.RequestListenerInterface.invoke(RequestListenerInterface.java:241) ~[wicket-core-7.10.0.jar:7.10.0] at org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandler.invokeListener(ListenerInterfaceRequestHandler.java:248) ~[wicket-core-7.10.0.jar:7.10.0] at org.apache.wicket.core.request.handler.ListenerInterfaceRequestHandler.respond(ListenerInterfaceRequestHandler.java:234) ~[wicket-core-7.10.0.jar:7.10.0] at org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:895) ~[wicket-core-7.10.0.jar:7.10.0] at org.apache.wicket.request.RequestHandlerStack.execute(RequestHandlerStack.java:64) ~[wicket-request-7.10.0.jar:7.10.0] at org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:265) ~[wicket-core-7.10.0.jar:7.10.0] at
[jira] [Resolved] (SYNCOPE-1294) Plainschema panel doesn't display the assigned validator class
[ https://issues.apache.org/jira/browse/SYNCOPE-1294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-1294. --- Resolution: Fixed > Plainschema panel doesn't display the assigned validator class > -- > > Key: SYNCOPE-1294 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1294 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.0.8, 2.1.0 >Reporter: Marco Di Sabatino Di Diodoro >Assignee: Marco Di Sabatino Di Diodoro >Priority: Major > Fix For: 2.0.9, 2.1.0 > > > If a plain schema has assigned a validator class, the console always shows a > null value -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SYNCOPE-1294) Plainschema panel doesn't display the assigned validator class
Marco Di Sabatino Di Diodoro created SYNCOPE-1294: - Summary: Plainschema panel doesn't display the assigned validator class Key: SYNCOPE-1294 URL: https://issues.apache.org/jira/browse/SYNCOPE-1294 Project: Syncope Issue Type: Bug Components: console Affects Versions: 2.0.8, 2.1.0 Reporter: Marco Di Sabatino Di Diodoro Assignee: Marco Di Sabatino Di Diodoro Fix For: 2.0.9 If a plain schema has assigned a validator class, the console always shows a null value -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SYNCOPE-1275) Add the possibiliy to delete a job
[ https://issues.apache.org/jira/browse/SYNCOPE-1275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-1275. --- Resolution: Fixed > Add the possibiliy to delete a job > -- > > Key: SYNCOPE-1275 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1275 > Project: Syncope > Issue Type: Bug > Components: console, core >Affects Versions: 2.0.7 >Reporter: Marco Di Sabatino Di Diodoro >Assignee: Marco Di Sabatino Di Diodoro >Priority: Major > Fix For: 2.0.8, 2.1.0 > > > Currently it is only possible to force execution or try to stop it. The goal > is to add the ability to delete a job. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SYNCOPE-1275) Add the possibiliy to delete a job
[ https://issues.apache.org/jira/browse/SYNCOPE-1275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro reassigned SYNCOPE-1275: - Assignee: Marco Di Sabatino Di Diodoro > Add the possibiliy to delete a job > -- > > Key: SYNCOPE-1275 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1275 > Project: Syncope > Issue Type: Bug > Components: console, core >Affects Versions: 2.0.7 >Reporter: Marco Di Sabatino Di Diodoro >Assignee: Marco Di Sabatino Di Diodoro >Priority: Major > Fix For: 2.0.8, 2.1.0 > > > Currently it is only possible to force execution or try to stop it. The goal > is to add the ability to delete a job. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SYNCOPE-1275) Add the possibiliy to delete a job
Marco Di Sabatino Di Diodoro created SYNCOPE-1275: - Summary: Add the possibiliy to delete a job Key: SYNCOPE-1275 URL: https://issues.apache.org/jira/browse/SYNCOPE-1275 Project: Syncope Issue Type: Bug Components: console, core Affects Versions: 2.0.7 Reporter: Marco Di Sabatino Di Diodoro Fix For: 2.0.8, 2.1.0 Currently it is only possible to force execution or try to stop it. The goal is to add the ability to delete a job. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SYNCOPE-1272) Export of the report always returns the result of the last execution
[ https://issues.apache.org/jira/browse/SYNCOPE-1272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-1272. --- Resolution: Fixed > Export of the report always returns the result of the last execution > > > Key: SYNCOPE-1272 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1272 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.0.7 >Reporter: Marco Di Sabatino Di Diodoro >Assignee: Marco Di Sabatino Di Diodoro >Priority: Major > Fix For: 2.0.8, 2.1.0 > > > If you try to download the result of the same report for various executions, > the console always returns the result of the last execution -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SYNCOPE-1272) Export of the report always returns the result of the last execution
[ https://issues.apache.org/jira/browse/SYNCOPE-1272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro reassigned SYNCOPE-1272: - Assignee: Marco Di Sabatino Di Diodoro > Export of the report always returns the result of the last execution > > > Key: SYNCOPE-1272 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1272 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.0.7 >Reporter: Marco Di Sabatino Di Diodoro >Assignee: Marco Di Sabatino Di Diodoro >Priority: Major > Fix For: 2.0.8, 2.1.0 > > > If you try to download the result of the same report for various executions, > the console always returns the result of the last execution -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SYNCOPE-1272) Export of the report always returns the result of the last execution
Marco Di Sabatino Di Diodoro created SYNCOPE-1272: - Summary: Export of the report always returns the result of the last execution Key: SYNCOPE-1272 URL: https://issues.apache.org/jira/browse/SYNCOPE-1272 Project: Syncope Issue Type: Bug Components: console Affects Versions: 2.0.7 Reporter: Marco Di Sabatino Di Diodoro Fix For: 2.0.8, 2.1.0 If you try to download the result of the same report for various executions, the console always returns the result of the last execution -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SYNCOPE-1271) Search using boolean attributes from the console returns a wrong result
Marco Di Sabatino Di Diodoro created SYNCOPE-1271: - Summary: Search using boolean attributes from the console returns a wrong result Key: SYNCOPE-1271 URL: https://issues.apache.org/jira/browse/SYNCOPE-1271 Project: Syncope Issue Type: Bug Components: console Affects Versions: 2.0.7 Reporter: Marco Di Sabatino Di Diodoro Fix For: 2.0.8, 2.1.0 The search from the console using a boolean attribute returns always an empty result. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SYNCOPE-1251) UserTO variable is not updated during Update Activiti Task
[ https://issues.apache.org/jira/browse/SYNCOPE-1251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro reassigned SYNCOPE-1251: - Assignee: Marco Di Sabatino Di Diodoro > UserTO variable is not updated during Update Activiti Task > -- > > Key: SYNCOPE-1251 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1251 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 2.0.6 >Reporter: Marco Di Sabatino Di Diodoro >Assignee: Marco Di Sabatino Di Diodoro > Fix For: 2.0.7, 2.1.0 > > > During the update process, the variable userTO is not updated in the > workflow. > In the approval phase, if you make a change to the user, the userTO doesn't > match the current one. This causes a wrong user patch. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (SYNCOPE-1251) UserTO variable is not updated during Update Activiti Task
[ https://issues.apache.org/jira/browse/SYNCOPE-1251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-1251. --- Resolution: Fixed > UserTO variable is not updated during Update Activiti Task > -- > > Key: SYNCOPE-1251 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1251 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 2.0.6 >Reporter: Marco Di Sabatino Di Diodoro >Assignee: Marco Di Sabatino Di Diodoro > Fix For: 2.0.7, 2.1.0 > > > During the update process, the variable userTO is not updated in the > workflow. > In the approval phase, if you make a change to the user, the userTO doesn't > match the current one. This causes a wrong user patch. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SYNCOPE-1251) UserTO variable is not updated during Update Activiti Task
Marco Di Sabatino Di Diodoro created SYNCOPE-1251: - Summary: UserTO variable is not updated during Update Activiti Task Key: SYNCOPE-1251 URL: https://issues.apache.org/jira/browse/SYNCOPE-1251 Project: Syncope Issue Type: Bug Components: core Affects Versions: 2.0.6 Reporter: Marco Di Sabatino Di Diodoro Fix For: 2.0.7, 2.1.0 During the update process, the variable userTO is not updated in the workflow. In the approval phase, if you make a change to the user, the userTO doesn't match the current one. This causes a wrong user patch. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (SYNCOPE-1248) Password policy history error when the user is updated before being approved
[ https://issues.apache.org/jira/browse/SYNCOPE-1248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-1248. --- Resolution: Fixed Assignee: Marco Di Sabatino Di Diodoro > Password policy history error when the user is updated before being approved > > > Key: SYNCOPE-1248 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1248 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.0.6 >Reporter: Marco Di Sabatino Di Diodoro >Assignee: Marco Di Sabatino Di Diodoro > Fix For: 2.0.7, 2.1.0 > > > Error: InvalidUser [InvalidPassword: Password value was used in the past: not > allowed] > when the user is updated before being approved. > To reproduce the error: > 1) Create a password policy with history for a realm X > 2) Create a new user inside realm X > 3) Set a membership from enduser > 4) With your admin, claim and edit the user. > 5) Save > 7) Try to approve the user -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SYNCOPE-1248) Password policy history error when the user is updated before being approved
Marco Di Sabatino Di Diodoro created SYNCOPE-1248: - Summary: Password policy history error when the user is updated before being approved Key: SYNCOPE-1248 URL: https://issues.apache.org/jira/browse/SYNCOPE-1248 Project: Syncope Issue Type: Bug Components: console Affects Versions: 2.0.6 Reporter: Marco Di Sabatino Di Diodoro Fix For: 2.0.7, 2.1.0 Error: InvalidUser [InvalidPassword: Password value was used in the past: not allowed] when the user is updated before being approved. To reproduce the error: 1) Create a password policy with history for a realm X 2) Create a new user inside realm X 3) Set a membership from enduser 4) With your admin, claim and edit the user. 5) Save 7) Try to approve the user -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SYNCOPE-1240) Topology panel doesn't refresh after a connector has been created
Marco Di Sabatino Di Diodoro created SYNCOPE-1240: - Summary: Topology panel doesn't refresh after a connector has been created Key: SYNCOPE-1240 URL: https://issues.apache.org/jira/browse/SYNCOPE-1240 Project: Syncope Issue Type: Bug Components: console Affects Versions: 2.0.6 Reporter: Marco Di Sabatino Di Diodoro Fix For: 2.0.7, 2.1.0 The topology panel doesn't refresh after a connector or resource has been added. The problem is related to the issue https://issues.apache.org/jira/browse/SYNCOPE-1238 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SYNCOPE-1236) Pagination error for executed tasks
Marco Di Sabatino Di Diodoro created SYNCOPE-1236: - Summary: Pagination error for executed tasks Key: SYNCOPE-1236 URL: https://issues.apache.org/jira/browse/SYNCOPE-1236 Project: Syncope Issue Type: Bug Components: console Affects Versions: 2.0.6 Reporter: Marco Di Sabatino Di Diodoro Fix For: 2.0.7, 2.1.0 During visualization of the executed task, the total number is not calculated correctly. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SYNCOPE-1193) Add the option to update a user via REST by using the username as key
[ https://issues.apache.org/jira/browse/SYNCOPE-1193?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro updated SYNCOPE-1193: -- Summary: Add the option to update a user via REST by using the username as key (was: Add the option to edit a user via REST by using the username as key) > Add the option to update a user via REST by using the username as key > - > > Key: SYNCOPE-1193 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1193 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 2.0.4 >Reporter: Marco Di Sabatino Di Diodoro > Fix For: 2.0.5, 2.1.0 > > > During an update via REST, you must use key to upgrade the user. This happens > because during the search of the last etag, the core uses > userDAO.findLastChange(key). If you set the username it returns a > NotFoundException. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SYNCOPE-1193) Add the option to edit a user via REST by using the username as key
Marco Di Sabatino Di Diodoro created SYNCOPE-1193: - Summary: Add the option to edit a user via REST by using the username as key Key: SYNCOPE-1193 URL: https://issues.apache.org/jira/browse/SYNCOPE-1193 Project: Syncope Issue Type: Bug Components: core Affects Versions: 2.0.4 Reporter: Marco Di Sabatino Di Diodoro Fix For: 2.0.5, 2.1.0 During an update via REST, you must use key to upgrade the user. This happens because during the search of the last etag, the core uses userDAO.findLastChange(key). If you set the username it returns a NotFoundException. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SYNCOPE-1166) No propagation task is created for resources where the password is not propagated
[ https://issues.apache.org/jira/browse/SYNCOPE-1166?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro updated SYNCOPE-1166: -- Attachment: SYNCOPE-1166-test.patch I implemented the test for this issue. > No propagation task is created for resources where the password is not > propagated > - > > Key: SYNCOPE-1166 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1166 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 2.0.4 >Reporter: Marco Di Sabatino Di Diodoro >Assignee: Marco Di Sabatino Di Diodoro > Fix For: 2.0.5, 2.1.0 > > Attachments: SYNCOPE-1166-test.patch > > > During a propagation, if one of the resources assigned to the user doesn't > need to propagate the password but other fields, Syncope doesn't generate the > task for that resource. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SYNCOPE-1169) Operation not supported error when trying to run a bulk action for users
Marco Di Sabatino Di Diodoro created SYNCOPE-1169: - Summary: Operation not supported error when trying to run a bulk action for users Key: SYNCOPE-1169 URL: https://issues.apache.org/jira/browse/SYNCOPE-1169 Project: Syncope Issue Type: Bug Components: console Affects Versions: 2.0.4 Reporter: Marco Di Sabatino Di Diodoro Fix For: 2.0.5, 2.1.0 When trying to run a bulk action for user/groups/any, Syncope returns an operation not supported message. The problem is caused client/console/src/main/java/org/apache/syncope/client/console/bulk/BulkContent.java at line number 154. ERROR org.apache.syncope.client.console.bulk.BulkContent - Bulk action failure java.lang.NoSuchMethodException: org.apache.syncope.client.console.rest.UserRestClient.bulkAction(org.apache.syncope.common.lib.to.BulkAction) at java.lang.Class.getMethod(Class.java:1786) ~[?:1.8.0_131] at org.apache.syncope.client.console.bulk.BulkContent$2.onClick(BulkContent.java:155) ~[syncope-client-console-2.0.5-SNAPSHOT.jar:2.0.5-SNAPSHOT] at org.apache.syncope.client.console.wicket.markup.html.form.ActionPanel$3.onClick(ActionPanel.java:122) ~[syncope-client-console-2.0.5-SNAPSHOT.jar:2.0.5-SNAPSHOT] -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SYNCOPE-1166) No propagation task is created for resources where the password is not propagated
Marco Di Sabatino Di Diodoro created SYNCOPE-1166: - Summary: No propagation task is created for resources where the password is not propagated Key: SYNCOPE-1166 URL: https://issues.apache.org/jira/browse/SYNCOPE-1166 Project: Syncope Issue Type: Bug Components: core Affects Versions: 2.0.4 Reporter: Marco Di Sabatino Di Diodoro Assignee: Marco Di Sabatino Di Diodoro Fix For: 2.0.5, 2.1.0 During a propagation, if one of the resources assigned to the user doesn't need to propagate the password but other fields, Syncope doesn't generate the task for that resource. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (SYNCOPE-1095) Provide preview for JSON and XML binary field
[ https://issues.apache.org/jira/browse/SYNCOPE-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-1095. --- Resolution: Fixed > Provide preview for JSON and XML binary field > - > > Key: SYNCOPE-1095 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1095 > Project: Syncope > Issue Type: New Feature > Components: console >Affects Versions: 2.0.3 >Reporter: Marco Di Sabatino Di Diodoro >Assignee: Marco Di Sabatino Di Diodoro > Fix For: 2.0.4, 2.1.0 > > > Provide a preview for JSON and XML binary field. The preview can be extended > with other types [1] > [1] https://codemirror.net/mode/ -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Reopened] (SYNCOPE-1095) Provide preview for JSON and XML binary field
[ https://issues.apache.org/jira/browse/SYNCOPE-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro reopened SYNCOPE-1095: --- Field preview in a multivalued schema is not displayed correctly > Provide preview for JSON and XML binary field > - > > Key: SYNCOPE-1095 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1095 > Project: Syncope > Issue Type: New Feature > Components: console >Affects Versions: 2.0.3 >Reporter: Marco Di Sabatino Di Diodoro >Assignee: Marco Di Sabatino Di Diodoro > Fix For: 2.0.4, 2.1.0 > > > Provide a preview for JSON and XML binary field. The preview can be extended > with other types [1] > [1] https://codemirror.net/mode/ -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (SYNCOPE-1095) Provide preview for JSON and XML binary field
[ https://issues.apache.org/jira/browse/SYNCOPE-1095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-1095. --- Resolution: Fixed > Provide preview for JSON and XML binary field > - > > Key: SYNCOPE-1095 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1095 > Project: Syncope > Issue Type: New Feature > Components: console >Affects Versions: 2.0.3 >Reporter: Marco Di Sabatino Di Diodoro >Assignee: Marco Di Sabatino Di Diodoro > Fix For: 2.0.4, 2.1.0 > > > Provide a preview for JSON and XML binary field. The preview can be extended > with other types [1] > [1] https://codemirror.net/mode/ -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (SYNCOPE-1095) Provide preview for JSON and XML binary field
Marco Di Sabatino Di Diodoro created SYNCOPE-1095: - Summary: Provide preview for JSON and XML binary field Key: SYNCOPE-1095 URL: https://issues.apache.org/jira/browse/SYNCOPE-1095 Project: Syncope Issue Type: New Feature Components: console Affects Versions: 2.0.3 Reporter: Marco Di Sabatino Di Diodoro Assignee: Marco Di Sabatino Di Diodoro Fix For: 2.0.4, 2.1.0 Provide a preview for JSON and XML binary field. The preview can be extended with other types [1] [1] https://codemirror.net/mode/ -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (SYNCOPE-1083) ConnInstance location is not normalized
[ https://issues.apache.org/jira/browse/SYNCOPE-1083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-1083. --- Resolution: Fixed > ConnInstance location is not normalized > --- > > Key: SYNCOPE-1083 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1083 > Project: Syncope > Issue Type: Improvement > Components: core >Affects Versions: 1.2.10, 2.0.3 >Reporter: Andrea Patricelli >Assignee: Marco Di Sabatino Di Diodoro > Fix For: 1.2.11, 2.0.4, 2.1.0 > > > Currently only location of connid bundles is normalized to URL, ConnInstance > is not. This could lead to misalignments between bundles location and > conninstance location. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Assigned] (SYNCOPE-1083) ConnInstance location is not normalized
[ https://issues.apache.org/jira/browse/SYNCOPE-1083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro reassigned SYNCOPE-1083: - Assignee: Marco Di Sabatino Di Diodoro > ConnInstance location is not normalized > --- > > Key: SYNCOPE-1083 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1083 > Project: Syncope > Issue Type: Improvement > Components: core >Affects Versions: 1.2.10, 2.0.3 >Reporter: Andrea Patricelli >Assignee: Marco Di Sabatino Di Diodoro > Fix For: 1.2.11, 2.0.4, 2.1.0 > > > Currently only location of connid bundles is normalized to URL, ConnInstance > is not. This could lead to misalignments between bundles location and > conninstance location. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (SYNCOPE-1075) User lastChangeDate attribute is not displayed correctly
[ https://issues.apache.org/jira/browse/SYNCOPE-1075?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-1075. --- Resolution: Fixed > User lastChangeDate attribute is not displayed correctly > > > Key: SYNCOPE-1075 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1075 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.0.3 >Reporter: Marco Di Sabatino Di Diodoro >Assignee: Marco Di Sabatino Di Diodoro >Priority: Minor > Fix For: 2.0.4, 2.1.0 > > > On the user's edit modal page the lastChangeDate attribute is not displayed > correctly -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (SYNCOPE-1076) The console doesn't allow to download the report in various formats
Marco Di Sabatino Di Diodoro created SYNCOPE-1076: - Summary: The console doesn't allow to download the report in various formats Key: SYNCOPE-1076 URL: https://issues.apache.org/jira/browse/SYNCOPE-1076 Project: Syncope Issue Type: Bug Components: console Affects Versions: 2.0.3 Reporter: Marco Di Sabatino Di Diodoro Fix For: 2.0.4, 2.1.0 The console doesn't allow to download the report in various formats. The type of report selected remains persistent even on other donwload links. In the SNAPSHOT version, missing the link for downloading xml format. The download link for xml format is not present. A workaround to download the various formats is to reclick on the report tab and download the desired format. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (SYNCOPE-1075) User lastChangeDate attribute is not displayed correctly
Marco Di Sabatino Di Diodoro created SYNCOPE-1075: - Summary: User lastChangeDate attribute is not displayed correctly Key: SYNCOPE-1075 URL: https://issues.apache.org/jira/browse/SYNCOPE-1075 Project: Syncope Issue Type: Bug Components: console Affects Versions: 2.0.3 Reporter: Marco Di Sabatino Di Diodoro Assignee: Marco Di Sabatino Di Diodoro Priority: Minor Fix For: 2.0.4, 2.1.0 On the user's edit modal page the lastChangeDate attribute is not displayed correctly -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (SYNCOPE-1071) The executed notification tasks are not displaying on the console
[ https://issues.apache.org/jira/browse/SYNCOPE-1071?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-1071. --- Resolution: Fixed > The executed notification tasks are not displaying on the console > - > > Key: SYNCOPE-1071 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1071 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.0.3 >Reporter: Marco Di Sabatino Di Diodoro >Assignee: Marco Di Sabatino Di Diodoro > Fix For: 2.0.4, 2.1.0 > > > The executed notification tasks under the Notification/NotificationTasks are > not visible. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (SYNCOPE-1071) The executed notification tasks are not displaying on the console
Marco Di Sabatino Di Diodoro created SYNCOPE-1071: - Summary: The executed notification tasks are not displaying on the console Key: SYNCOPE-1071 URL: https://issues.apache.org/jira/browse/SYNCOPE-1071 Project: Syncope Issue Type: Bug Components: console Affects Versions: 2.0.3 Reporter: Marco Di Sabatino Di Diodoro Assignee: Marco Di Sabatino Di Diodoro Fix For: 2.0.4, 2.1.0 The executed notification tasks under the Notification/NotificationTasks are not visible. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SYNCOPE-1057) During pull task Syncope doesn't maintains the assigned type extensions
[ https://issues.apache.org/jira/browse/SYNCOPE-1057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro updated SYNCOPE-1057: -- Fix Version/s: 2.1.0 > During pull task Syncope doesn't maintains the assigned type extensions > > > Key: SYNCOPE-1057 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1057 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 2.0.3 >Reporter: Marco Di Sabatino Di Diodoro > Fix For: 2.0.3, 2.1.0 > > > During a pull task, if the object need to update, Syncope removes the > assigned type extension. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SYNCOPE-1057) During pull task Syncope doesn't maintains the assigned type extensions
[ https://issues.apache.org/jira/browse/SYNCOPE-1057?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro updated SYNCOPE-1057: -- Affects Version/s: (was: 2.1.0) > During pull task Syncope doesn't maintains the assigned type extensions > > > Key: SYNCOPE-1057 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1057 > Project: Syncope > Issue Type: Bug > Components: core >Affects Versions: 2.0.3 >Reporter: Marco Di Sabatino Di Diodoro > Fix For: 2.0.3, 2.1.0 > > > During a pull task, if the object need to update, Syncope removes the > assigned type extension. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (SYNCOPE-1057) During pull task Syncope doesn't maintains the assigned type extensions
Marco Di Sabatino Di Diodoro created SYNCOPE-1057: - Summary: During pull task Syncope doesn't maintains the assigned type extensions Key: SYNCOPE-1057 URL: https://issues.apache.org/jira/browse/SYNCOPE-1057 Project: Syncope Issue Type: Bug Components: core Affects Versions: 2.0.3, 2.1.0 Reporter: Marco Di Sabatino Di Diodoro Fix For: 2.0.3 During a pull task, if the object need to update, Syncope removes the assigned type extension. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (SYNCOPE-991) Improve user password management / resource management
[
https://issues.apache.org/jira/browse/SYNCOPE-991?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Di Sabatino Di Diodoro updated SYNCOPE-991:
-
Attachment: SYNCOPE-991.patch
> Improve user password management / resource management
> --
>
> Key: SYNCOPE-991
> URL: https://issues.apache.org/jira/browse/SYNCOPE-991
> Project: Syncope
> Issue Type: Improvement
> Components: console
>Reporter: Francesco Chicchiriccò
>Assignee: fabio martelli
> Fix For: 2.0.3, 2.1.0
>
> Attachments: password_resources.png, SYNCOPE-991.patch, user_row.png
>
>
> Resource management (for users, groups and any objects) is accessible via a
> dedicated icon (the second one from left side, see attached screenshot
> {{user_row.png}}).
> From there, several bulk actions (link / unlink, assign / unassign, provision
> / deprovision) are available, and status is also shown. However, the view
> feature (reporting the actual remote object on the external resource) is
> missing and should be added.
> About user password management:
> * when new user is created, password can be optionally provided (a sliding
> pane is available for this purpose)
> * when user is edited, new password can be optionally provided, but a pane
> with currently assigned resources (with remote view) is also available; for
> each resource a checkbox is present to indicate that password value must be
> sent there, in case of password update (see attached screenshot
> {{password_resources.png}})
> It would be better to
> # remove the resources pane at all (provided that the remote view will be
> anyway available from elsewhere)
> # keep user password update but insert a warning message that password value
> will be sent to all associated resources (including the internal storage)
> # add a further modal window, accessible as other features as in
> {{user_row.png}} for managing password update on internal storage and / or
> one or more resources
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (SYNCOPE-1042) Removal of all executed pull tasks via bulk action returns a missing resource exception
Marco Di Sabatino Di Diodoro created SYNCOPE-1042: - Summary: Removal of all executed pull tasks via bulk action returns a missing resource exception Key: SYNCOPE-1042 URL: https://issues.apache.org/jira/browse/SYNCOPE-1042 Project: Syncope Issue Type: Bug Components: console Affects Versions: 2.0.2 Reporter: Marco Di Sabatino Di Diodoro Priority: Minor Fix For: 2.0.3, 2.1.0 To reproduce the error, perform the following steps: 1) Go to Topology 2) Click on Resource 3) Click on Pull Tasks 4) View executed pull tasks 5) Select all and clean with a bulk action java.util.MissingResourceException: Unable to find property: 'start' for component: body:toggle:outerObjectsRepeater:2:outer:form:content:tasks:secondLevelContainer:second:executions:secondLevelContainer:second:container:selectedObjects:topToolbars:toolbars:2:headers:2:header:orderByLink:header_body:label [class=org.apache.wicket.markup.html.basic.Label]. Locale: null, style: null at org.apache.wicket.Localizer.getString(Localizer.java:268) at org.apache.wicket.model.ResourceModel$AssignmentWrapper.load(ResourceModel.java:129) at org.apache.wicket.model.ResourceModel$AssignmentWrapper.load(ResourceModel.java:99) at org.apache.wicket.model.LoadableDetachableModel.getObject(LoadableDetachableModel.java:135) at org.apache.wicket.Component.getDefaultModelObject(Component.java:1646) at org.apache.wicket.Component.getDefaultModelObjectAsString(Component.java:1674) -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (SYNCOPE-1034) Assigned Auxiliary classes disappear in the Type Extensions panel when click on cancel
Marco Di Sabatino Di Diodoro created SYNCOPE-1034: - Summary: Assigned Auxiliary classes disappear in the Type Extensions panel when click on cancel Key: SYNCOPE-1034 URL: https://issues.apache.org/jira/browse/SYNCOPE-1034 Project: Syncope Issue Type: Bug Components: console Affects Versions: 2.0.2 Reporter: Marco Di Sabatino Di Diodoro Priority: Minor Fix For: 2.0.3, 2.1.0 Assigned Auxiliary classes disappear in the Type Extensions panel when click on cancel: 1) Edit an existing type extension with an associated class. 2) Edit Auxiliary classes assignment. 3) Click on cancel. If you refresh the view, the auxiliary classes are still present. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (SYNCOPE-962) Upgrade to Wicket 7.5.0
[
https://issues.apache.org/jira/browse/SYNCOPE-962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Di Sabatino Di Diodoro resolved SYNCOPE-962.
--
Resolution: Fixed
Assignee: Marco Di Sabatino Di Diodoro
> Upgrade to Wicket 7.5.0
> ---
>
> Key: SYNCOPE-962
> URL: https://issues.apache.org/jira/browse/SYNCOPE-962
> Project: Syncope
> Issue Type: Task
> Components: console
>Reporter: Francesco Chicchiriccò
>Assignee: Marco Di Sabatino Di Diodoro
> Fix For: 2.0.2, 2.1.0
>
>
> Despite being considered a drop-in replacement for 7.4.0, upgrading Wicket to
> 7.5.0 seems to cause several issues.
> Even applying the fixes and workarounds [1] [2] provided by the Wicket
> community, when going to almost any page but Dashboard and Logs, a stacktrace
> is returned:
> {code}
> org.apache.wicket.WicketRuntimeException: The component(s) below failed to
> render. Possible reasons could be that: 1) you have added a component in code
> but forgot to reference it in the markup (thus the component will never be
> rendered), 2) if your components were added in a parent container then make
> sure the markup for the child container includes them in .
> 1. [Fragment [Component id = required]]
> 2. [Fragment [Component id = externalAction]]
> 3. [Fragment [Component id = required]]
> 4. [Fragment [Component id = externalAction]]
> 5. [Fragment [Component id = required]]
> 6. [Fragment [Component id = externalAction]]
> 7. [Fragment [Component id = required]]
> 8. [Fragment [Component id = externalAction]]
> 9. [Fragment [Component id = required]]
> 10. [Fragment [Component id = externalAction]]
> 11. [Fragment [Component id = required]]
> 12. [Fragment [Component id = externalAction]]
> 13. [ListView [Component id = buttons]]
> 14. [ListItem [Component id = 0]]
> 15. [DefaultModalCloseButton [Component id = button]]
> 16. [ListView [Component id = inputs]]
> 17. [ListView [Component id = buttons]]
> 18. [ListItem [Component id = 0]]
> 19. [DefaultModalCloseButton [Component id = button]]
> 20. [ListView [Component id = inputs]]
> 21. [ListView [Component id = buttons]]
> 22. [ListItem [Component id = 0]]
> 23. [DefaultModalCloseButton [Component id = button]]
> 24. [ListView [Component id = inputs]]
> 25. [ListItem [Component id = 0]]
> 26. [AjaxSubmitLink [Component id = submit]]
> 27. [ListView [Component id = buttons]]
> 28. [ListItem [Component id = 0]]
> 29. [DefaultModalCloseButton [Component id = button]]
> 30. [ListView [Component id = inputs]]
> 31. [ListView [Component id = buttons]]
> 32. [ListItem [Component id = 0]]
> 33. [DefaultModalCloseButton [Component id = button]]
> 34. [ListView [Component id = inputs]]
> 35. [Fragment [Component id = required]]
> 36. [Fragment [Component id = externalAction]]
> at org.apache.wicket.Page.checkRendering(Page.java:666)
> ~[wicket-core-7.5.0.jar:7.5.0]
> at org.apache.wicket.Page.onAfterRender(Page.java:821)
> ~[wicket-core-7.5.0.jar:7.5.0]
> at
> org.apache.wicket.markup.html.WebPage.onAfterRender(WebPage.java:224)
> ~[wicket-core-7.5.0.jar:7.5.0]
> at org.apache.wicket.Component.afterRender(Component.java:932)
> ~[wicket-core-7.5.0.jar:7.5.0]
> at org.apache.wicket.Component.render(Component.java:2353)
> ~[wicket-core-7.5.0.jar:7.5.0]
> at org.apache.wicket.Page.renderPage(Page.java:1018)
> ~[wicket-core-7.5.0.jar:7.5.0]
> at
> org.apache.wicket.request.handler.render.WebPageRenderer.renderPage(WebPageRenderer.java:124)
> ~[wicket-core-7.5.0.jar:7.5.0]
> at
> org.apache.wicket.request.handler.render.WebPageRenderer.respond(WebPageRenderer.java:236)
> ~[wicket-core-7.5.0.jar:7.5.0]
> at
> org.apache.wicket.core.request.handler.RenderPageRequestHandler.respond(RenderPageRequestHandler.java:175)
> ~[wicket-core-7.5.0.jar:7.5.0]
> at
> org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:895)
> ~[wicket-core-7.5.0.jar:7.5.0]
> at
> org.apache.wicket.request.RequestHandlerStack.execute(RequestHandlerStack.java:64)
> ~[wicket-request-7.4.0.jar:7.4.0]
> at
> org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:265)
> ~[wicket-core-7.5.0.jar:7.5.0]
> at
> org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:222)
> ~[wicket-core-7.5.0.jar:7.5.0]
> at
> org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:293)
> ~[wicket-core-7.5.0.jar:7.5.0]
> at
> org.apache.wicket.protocol.ws.AbstractUpgradeFilter.processRequestCycle(AbstractUpgradeFilter.java:70)
> ~[wicket-native-websocket-core-7.5.0.jar:7.5.0]
> at
> org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:203)
>
[jira] [Comment Edited] (SYNCOPE-962) Upgrade to Wicket 7.5.0
[
https://issues.apache.org/jira/browse/SYNCOPE-962?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15780061#comment-15780061
]
Marco Di Sabatino Di Diodoro edited comment on SYNCOPE-962 at 12/27/16 9:57 AM:
After upgrade to wicket 7.5.0, Syncope doesn't store the user password.
https://lists.apache.org/thread.html/0c2c196410aefefc1e57d91969a2dbf1b62d09b556e0ed7bda28218d@%3Cuser.syncope.apache.org%3E
was (Author: mdisabatino):
After upgrade to wicket 7.5.0, Syncope doesn't store the password.
> Upgrade to Wicket 7.5.0
> ---
>
> Key: SYNCOPE-962
> URL: https://issues.apache.org/jira/browse/SYNCOPE-962
> Project: Syncope
> Issue Type: Task
> Components: console
>Reporter: Francesco Chicchiriccò
> Fix For: 2.0.2, 2.1.0
>
>
> Despite being considered a drop-in replacement for 7.4.0, upgrading Wicket to
> 7.5.0 seems to cause several issues.
> Even applying the fixes and workarounds [1] [2] provided by the Wicket
> community, when going to almost any page but Dashboard and Logs, a stacktrace
> is returned:
> {code}
> org.apache.wicket.WicketRuntimeException: The component(s) below failed to
> render. Possible reasons could be that: 1) you have added a component in code
> but forgot to reference it in the markup (thus the component will never be
> rendered), 2) if your components were added in a parent container then make
> sure the markup for the child container includes them in .
> 1. [Fragment [Component id = required]]
> 2. [Fragment [Component id = externalAction]]
> 3. [Fragment [Component id = required]]
> 4. [Fragment [Component id = externalAction]]
> 5. [Fragment [Component id = required]]
> 6. [Fragment [Component id = externalAction]]
> 7. [Fragment [Component id = required]]
> 8. [Fragment [Component id = externalAction]]
> 9. [Fragment [Component id = required]]
> 10. [Fragment [Component id = externalAction]]
> 11. [Fragment [Component id = required]]
> 12. [Fragment [Component id = externalAction]]
> 13. [ListView [Component id = buttons]]
> 14. [ListItem [Component id = 0]]
> 15. [DefaultModalCloseButton [Component id = button]]
> 16. [ListView [Component id = inputs]]
> 17. [ListView [Component id = buttons]]
> 18. [ListItem [Component id = 0]]
> 19. [DefaultModalCloseButton [Component id = button]]
> 20. [ListView [Component id = inputs]]
> 21. [ListView [Component id = buttons]]
> 22. [ListItem [Component id = 0]]
> 23. [DefaultModalCloseButton [Component id = button]]
> 24. [ListView [Component id = inputs]]
> 25. [ListItem [Component id = 0]]
> 26. [AjaxSubmitLink [Component id = submit]]
> 27. [ListView [Component id = buttons]]
> 28. [ListItem [Component id = 0]]
> 29. [DefaultModalCloseButton [Component id = button]]
> 30. [ListView [Component id = inputs]]
> 31. [ListView [Component id = buttons]]
> 32. [ListItem [Component id = 0]]
> 33. [DefaultModalCloseButton [Component id = button]]
> 34. [ListView [Component id = inputs]]
> 35. [Fragment [Component id = required]]
> 36. [Fragment [Component id = externalAction]]
> at org.apache.wicket.Page.checkRendering(Page.java:666)
> ~[wicket-core-7.5.0.jar:7.5.0]
> at org.apache.wicket.Page.onAfterRender(Page.java:821)
> ~[wicket-core-7.5.0.jar:7.5.0]
> at
> org.apache.wicket.markup.html.WebPage.onAfterRender(WebPage.java:224)
> ~[wicket-core-7.5.0.jar:7.5.0]
> at org.apache.wicket.Component.afterRender(Component.java:932)
> ~[wicket-core-7.5.0.jar:7.5.0]
> at org.apache.wicket.Component.render(Component.java:2353)
> ~[wicket-core-7.5.0.jar:7.5.0]
> at org.apache.wicket.Page.renderPage(Page.java:1018)
> ~[wicket-core-7.5.0.jar:7.5.0]
> at
> org.apache.wicket.request.handler.render.WebPageRenderer.renderPage(WebPageRenderer.java:124)
> ~[wicket-core-7.5.0.jar:7.5.0]
> at
> org.apache.wicket.request.handler.render.WebPageRenderer.respond(WebPageRenderer.java:236)
> ~[wicket-core-7.5.0.jar:7.5.0]
> at
> org.apache.wicket.core.request.handler.RenderPageRequestHandler.respond(RenderPageRequestHandler.java:175)
> ~[wicket-core-7.5.0.jar:7.5.0]
> at
> org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:895)
> ~[wicket-core-7.5.0.jar:7.5.0]
> at
> org.apache.wicket.request.RequestHandlerStack.execute(RequestHandlerStack.java:64)
> ~[wicket-request-7.4.0.jar:7.4.0]
> at
> org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:265)
> ~[wicket-core-7.5.0.jar:7.5.0]
> at
> org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:222)
> ~[wicket-core-7.5.0.jar:7.5.0]
> at
> org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:293)
> ~[wicket-core-7.5.0.jar:7.5.0]
> at
>
[jira] [Reopened] (SYNCOPE-962) Upgrade to Wicket 7.5.0
[
https://issues.apache.org/jira/browse/SYNCOPE-962?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marco Di Sabatino Di Diodoro reopened SYNCOPE-962:
--
Assignee: (was: fabio martelli)
After upgrade to wicket 7.5.0, Syncope doesn't store the password.
> Upgrade to Wicket 7.5.0
> ---
>
> Key: SYNCOPE-962
> URL: https://issues.apache.org/jira/browse/SYNCOPE-962
> Project: Syncope
> Issue Type: Task
> Components: console
>Reporter: Francesco Chicchiriccò
> Fix For: 2.0.2, 2.1.0
>
>
> Despite being considered a drop-in replacement for 7.4.0, upgrading Wicket to
> 7.5.0 seems to cause several issues.
> Even applying the fixes and workarounds [1] [2] provided by the Wicket
> community, when going to almost any page but Dashboard and Logs, a stacktrace
> is returned:
> {code}
> org.apache.wicket.WicketRuntimeException: The component(s) below failed to
> render. Possible reasons could be that: 1) you have added a component in code
> but forgot to reference it in the markup (thus the component will never be
> rendered), 2) if your components were added in a parent container then make
> sure the markup for the child container includes them in .
> 1. [Fragment [Component id = required]]
> 2. [Fragment [Component id = externalAction]]
> 3. [Fragment [Component id = required]]
> 4. [Fragment [Component id = externalAction]]
> 5. [Fragment [Component id = required]]
> 6. [Fragment [Component id = externalAction]]
> 7. [Fragment [Component id = required]]
> 8. [Fragment [Component id = externalAction]]
> 9. [Fragment [Component id = required]]
> 10. [Fragment [Component id = externalAction]]
> 11. [Fragment [Component id = required]]
> 12. [Fragment [Component id = externalAction]]
> 13. [ListView [Component id = buttons]]
> 14. [ListItem [Component id = 0]]
> 15. [DefaultModalCloseButton [Component id = button]]
> 16. [ListView [Component id = inputs]]
> 17. [ListView [Component id = buttons]]
> 18. [ListItem [Component id = 0]]
> 19. [DefaultModalCloseButton [Component id = button]]
> 20. [ListView [Component id = inputs]]
> 21. [ListView [Component id = buttons]]
> 22. [ListItem [Component id = 0]]
> 23. [DefaultModalCloseButton [Component id = button]]
> 24. [ListView [Component id = inputs]]
> 25. [ListItem [Component id = 0]]
> 26. [AjaxSubmitLink [Component id = submit]]
> 27. [ListView [Component id = buttons]]
> 28. [ListItem [Component id = 0]]
> 29. [DefaultModalCloseButton [Component id = button]]
> 30. [ListView [Component id = inputs]]
> 31. [ListView [Component id = buttons]]
> 32. [ListItem [Component id = 0]]
> 33. [DefaultModalCloseButton [Component id = button]]
> 34. [ListView [Component id = inputs]]
> 35. [Fragment [Component id = required]]
> 36. [Fragment [Component id = externalAction]]
> at org.apache.wicket.Page.checkRendering(Page.java:666)
> ~[wicket-core-7.5.0.jar:7.5.0]
> at org.apache.wicket.Page.onAfterRender(Page.java:821)
> ~[wicket-core-7.5.0.jar:7.5.0]
> at
> org.apache.wicket.markup.html.WebPage.onAfterRender(WebPage.java:224)
> ~[wicket-core-7.5.0.jar:7.5.0]
> at org.apache.wicket.Component.afterRender(Component.java:932)
> ~[wicket-core-7.5.0.jar:7.5.0]
> at org.apache.wicket.Component.render(Component.java:2353)
> ~[wicket-core-7.5.0.jar:7.5.0]
> at org.apache.wicket.Page.renderPage(Page.java:1018)
> ~[wicket-core-7.5.0.jar:7.5.0]
> at
> org.apache.wicket.request.handler.render.WebPageRenderer.renderPage(WebPageRenderer.java:124)
> ~[wicket-core-7.5.0.jar:7.5.0]
> at
> org.apache.wicket.request.handler.render.WebPageRenderer.respond(WebPageRenderer.java:236)
> ~[wicket-core-7.5.0.jar:7.5.0]
> at
> org.apache.wicket.core.request.handler.RenderPageRequestHandler.respond(RenderPageRequestHandler.java:175)
> ~[wicket-core-7.5.0.jar:7.5.0]
> at
> org.apache.wicket.request.cycle.RequestCycle$HandlerExecutor.respond(RequestCycle.java:895)
> ~[wicket-core-7.5.0.jar:7.5.0]
> at
> org.apache.wicket.request.RequestHandlerStack.execute(RequestHandlerStack.java:64)
> ~[wicket-request-7.4.0.jar:7.4.0]
> at
> org.apache.wicket.request.cycle.RequestCycle.execute(RequestCycle.java:265)
> ~[wicket-core-7.5.0.jar:7.5.0]
> at
> org.apache.wicket.request.cycle.RequestCycle.processRequest(RequestCycle.java:222)
> ~[wicket-core-7.5.0.jar:7.5.0]
> at
> org.apache.wicket.request.cycle.RequestCycle.processRequestAndDetach(RequestCycle.java:293)
> ~[wicket-core-7.5.0.jar:7.5.0]
> at
> org.apache.wicket.protocol.ws.AbstractUpgradeFilter.processRequestCycle(AbstractUpgradeFilter.java:70)
> ~[wicket-native-websocket-core-7.5.0.jar:7.5.0]
> at
> org.apache.wicket.protocol.http.WicketFilter.processRequest(WicketFilter.java:203)
> ~[wicket-core-7.5.0.jar:7.5.0]
[jira] [Resolved] (SYNCOPE-965) Cron expression for scheduled job is not saved from the console
[ https://issues.apache.org/jira/browse/SYNCOPE-965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-965. -- Resolution: Fixed > Cron expression for scheduled job is not saved from the console > --- > > Key: SYNCOPE-965 > URL: https://issues.apache.org/jira/browse/SYNCOPE-965 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 1.2.9, 2.0.1 >Reporter: Marco Di Sabatino Di Diodoro >Assignee: Marco Di Sabatino Di Diodoro > Fix For: 1.2.10, 2.0.2, 2.1.0 > > > If you create or update an scheduled job from the console, the cron > expression is not saved on Syncope. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SYNCOPE-965) Cron expression for scheduled job is not saved from the console
[ https://issues.apache.org/jira/browse/SYNCOPE-965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro updated SYNCOPE-965: - Fix Version/s: 2.0.2 > Cron expression for scheduled job is not saved from the console > --- > > Key: SYNCOPE-965 > URL: https://issues.apache.org/jira/browse/SYNCOPE-965 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 1.2.9, 2.0.1 >Reporter: Marco Di Sabatino Di Diodoro >Assignee: Marco Di Sabatino Di Diodoro > Fix For: 1.2.10, 2.0.2 > > > If you create or update an scheduled job from the console, the cron > expression is not saved on Syncope. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SYNCOPE-965) Cron expression for scheduled job is not saved from the console
[ https://issues.apache.org/jira/browse/SYNCOPE-965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro updated SYNCOPE-965: - Affects Version/s: 2.0.1 > Cron expression for scheduled job is not saved from the console > --- > > Key: SYNCOPE-965 > URL: https://issues.apache.org/jira/browse/SYNCOPE-965 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 1.2.9, 2.0.1 >Reporter: Marco Di Sabatino Di Diodoro >Assignee: Marco Di Sabatino Di Diodoro > Fix For: 1.2.10, 2.0.2 > > > If you create or update an scheduled job from the console, the cron > expression is not saved on Syncope. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (SYNCOPE-965) Cron expression for scheduled job is not saved from the console
[ https://issues.apache.org/jira/browse/SYNCOPE-965?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro reassigned SYNCOPE-965: Assignee: Marco Di Sabatino Di Diodoro > Cron expression for scheduled job is not saved from the console > --- > > Key: SYNCOPE-965 > URL: https://issues.apache.org/jira/browse/SYNCOPE-965 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 1.2.9 >Reporter: Marco Di Sabatino Di Diodoro >Assignee: Marco Di Sabatino Di Diodoro > Fix For: 1.2.10 > > > If you create or update an scheduled job from the console, the cron > expression is not saved on Syncope. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SYNCOPE-965) Cron expression for scheduled job is not saved from the console
Marco Di Sabatino Di Diodoro created SYNCOPE-965: Summary: Cron expression for scheduled job is not saved from the console Key: SYNCOPE-965 URL: https://issues.apache.org/jira/browse/SYNCOPE-965 Project: Syncope Issue Type: Bug Components: console Affects Versions: 1.2.9 Reporter: Marco Di Sabatino Di Diodoro Fix For: 1.2.10 If you create or update an scheduled job from the console, the cron expression is not saved on Syncope. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SYNCOPE-943) Security question gets deleted when changing a user attribute in the console
[ https://issues.apache.org/jira/browse/SYNCOPE-943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-943. -- Resolution: Fixed > Security question gets deleted when changing a user attribute in the console > > > Key: SYNCOPE-943 > URL: https://issues.apache.org/jira/browse/SYNCOPE-943 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 1.2.8 >Reporter: Colm O hEigeartaigh >Assignee: Marco Di Sabatino Di Diodoro > Fix For: 1.2.9 > > > When you change a password of a user in the console (for 1.2.8 only), the > selected security question gets deleted. Steps to reproduce: > 1) Log onto console as "admin" and create a new security question. > 2) Create a new user, selecting the security question + giving an answer. > 3) Now edit the user again. You'll see the security question selected, and a > greyed out textfield for the security answer. > 4) Edit some attribute and save the user. > 5) Now edit the user again...the security question has disappeared... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (SYNCOPE-943) Security question gets deleted when changing a user attribute in the console
[ https://issues.apache.org/jira/browse/SYNCOPE-943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro reassigned SYNCOPE-943: Assignee: Marco Di Sabatino Di Diodoro > Security question gets deleted when changing a user attribute in the console > > > Key: SYNCOPE-943 > URL: https://issues.apache.org/jira/browse/SYNCOPE-943 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 1.2.8 >Reporter: Colm O hEigeartaigh >Assignee: Marco Di Sabatino Di Diodoro > Fix For: 1.2.9 > > > When you change a password of a user in the console (for 1.2.8 only), the > selected security question gets deleted. Steps to reproduce: > 1) Log onto console as "admin" and create a new security question. > 2) Create a new user, selecting the security question + giving an answer. > 3) Now edit the user again. You'll see the security question selected, and a > greyed out textfield for the security answer. > 4) Edit some attribute and save the user. > 5) Now edit the user again...the security question has disappeared... -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SYNCOPE-954) Wicket exception when running an enable or disable action
[ https://issues.apache.org/jira/browse/SYNCOPE-954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro resolved SYNCOPE-954. -- Resolution: Fixed > Wicket exception when running an enable or disable action > - > > Key: SYNCOPE-954 > URL: https://issues.apache.org/jira/browse/SYNCOPE-954 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 1.2.8 >Reporter: Marco Di Sabatino Di Diodoro >Assignee: Marco Di Sabatino Di Diodoro > Fix For: 1.2.9 > > > If you try to execute an enabling or disabling action, syncope returns an > wicket exception. > org.apache.wicket.WicketRuntimeException: Cannot replace a component which > has not been added: id='_header_', component=[HtmlHeaderContainer [Component > id = header]]: > [Page class = org.apache.syncope.console.pages.StatusModalPage, id = 5, > render count = 1] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (SYNCOPE-954) Wicket exception when running an enable or disable action
[ https://issues.apache.org/jira/browse/SYNCOPE-954?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marco Di Sabatino Di Diodoro reassigned SYNCOPE-954: Assignee: Marco Di Sabatino Di Diodoro > Wicket exception when running an enable or disable action > - > > Key: SYNCOPE-954 > URL: https://issues.apache.org/jira/browse/SYNCOPE-954 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 1.2.8 >Reporter: Marco Di Sabatino Di Diodoro >Assignee: Marco Di Sabatino Di Diodoro > Fix For: 1.2.9 > > > If you try to execute an enabling or disabling action, syncope returns an > wicket exception. > org.apache.wicket.WicketRuntimeException: Cannot replace a component which > has not been added: id='_header_', component=[HtmlHeaderContainer [Component > id = header]]: > [Page class = org.apache.syncope.console.pages.StatusModalPage, id = 5, > render count = 1] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
