[jira] [Commented] (SYNCOPE-1090) Error defining clause to search for group owners
[ https://issues.apache.org/jira/browse/SYNCOPE-1090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16022588#comment-16022588 ] Matteo Alessandroni commented on SYNCOPE-1090: -- Confirm that it happens only when going back to select "Choose one" option. > Error defining clause to search for group owners > > > Key: SYNCOPE-1090 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1090 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.0.3 >Reporter: fabio martelli >Assignee: fabio martelli > Fix For: 2.0.4, 2.1.0 > > > In order to search for users to select a group owner an exception occurs > executing the following steps. > 1. edit group > 2. go to group oner tab > 3. click + to start to define a user search clause > 4. select Attribute in the first combo > 5. select an attribute in the second one > 6. come back to the first one and select "Chose One" > The following exception occurs at the step 6. > java.lang.IllegalArgumentException: No enum constant > org.apache.syncope.client.console.panels.search.SearchClause.Type. > at java.lang.Enum.valueOf(Enum.java:238) > at > org.apache.syncope.client.console.panels.search.SearchClause$Type.valueOf(SearchClause.java:38) > at > org.apache.syncope.client.console.panels.search.SearchClausePanel$10.onUpdate(SearchClausePanel.java:438) > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (SYNCOPE-1093) Add some feedbacks when linking not existing groups/resources to existing user
Matteo Alessandroni created SYNCOPE-1093:
Summary: Add some feedbacks when linking not existing
groups/resources to existing user
Key: SYNCOPE-1093
URL: https://issues.apache.org/jira/browse/SYNCOPE-1093
Project: Syncope
Issue Type: Improvement
Components: enduser
Affects Versions: 2.0.3
Reporter: Matteo Alessandroni
Priority: Minor
When using *syncope-enduser* to create or edit a User, it would be nice to have
a feedback when user tries to link a group or resource that does not exist and
block user from entering any group/resource when no groups/resources are
available in the system.
For instance ("Group" test case):
- I am in "Groups" tab and manually enter a not existing group name in "Groups"
input element;
- Click "Next" and I'm on next tab;
- Go back to "Groups" tab and the group I have entered is not there anymore.
*Problem*: I have got no feedbacks about the situation and I have initially
thought my group was linked to my user.
*Possible solution* ("Group" test case):
* _Case 1_: there is a group at least:
** If user inserts a not existing group (he does not choose one from dropdown)
and clicks on "Next" button --> show a message to warn that he must choose a
group from dropdown : Sample ;
** The group name he have entered will be removed from input element : Sample;
** If user inserts no groups, everything should work as usual.
* _Case 2_: there are no groups:
** "Groups" input element should be disabled by default.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (SYNCOPE-1093) Add some feedbacks when linking not existing groups/resources to existing user
[
https://issues.apache.org/jira/browse/SYNCOPE-1093?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matteo Alessandroni updated SYNCOPE-1093:
-
Affects Version/s: (was: 2.0.3)
> Add some feedbacks when linking not existing groups/resources to existing user
> --
>
> Key: SYNCOPE-1093
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1093
> Project: Syncope
> Issue Type: Improvement
> Components: enduser
>Reporter: Matteo Alessandroni
>Priority: Minor
> Fix For: 2.0.4, 2.1.0
>
>
> When using *syncope-enduser* to create or edit a User, it would be nice to
> have a feedback when user tries to link a group or resource that does not
> exist and block user from entering any group/resource when no
> groups/resources are available in the system.
> For instance ("Group" test case):
> - I am in "Groups" tab and manually enter a not existing group name in
> "Groups" input element;
> - Click "Next" and I'm on next tab;
> - Go back to "Groups" tab and the group I have entered is not there anymore.
> *Problem*: I have got no feedbacks about the situation and I have initially
> thought my group was linked to my user.
> *Possible solution* ("Group" test case):
> * _Case 1_: there is a group at least:
> ** If user inserts a not existing group (he does not choose one from
> dropdown) and clicks on "Next" button --> show a message to warn that he
> must choose a group from dropdown : Sample ;
> ** The group name he have entered will be removed from input element : Sample;
> ** If user inserts no groups, everything should work as usual.
> * _Case 2_: there are no groups:
> ** "Groups" input element should be disabled by default.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (SYNCOPE-1108) NullPointerException while saving an empty template
Matteo Alessandroni created SYNCOPE-1108: Summary: NullPointerException while saving an empty template Key: SYNCOPE-1108 URL: https://issues.apache.org/jira/browse/SYNCOPE-1108 Project: Syncope Issue Type: Bug Components: console Affects Versions: 2.0.3, 2.0.4 Reporter: Matteo Alessandroni Priority: Minor Fix For: 2.1.0 Steps to reproduce: * in Admin Console, go to Reports -> Templates * edit an existing template or create a new one * save with empty content -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SYNCOPE-1113) Report files are downloaded with same extension
Matteo Alessandroni created SYNCOPE-1113: Summary: Report files are downloaded with same extension Key: SYNCOPE-1113 URL: https://issues.apache.org/jira/browse/SYNCOPE-1113 Project: Syncope Issue Type: Bug Components: console Affects Versions: 2.0.3, 2.0.4 Environment: Firefox browser Reporter: Matteo Alessandroni Priority: Minor Fix For: 2.0.4, 2.1.0 Steps to reproduce: # go to Reports; # execute a report and go to "view" section; # click on the just executed report and export it in one of the available formats; # try to export the same report in the other formats *problem*: the exported files will always have the same format as in the first export (step 3). -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SYNCOPE-1134) Action menu not working after page refresh
[ https://issues.apache.org/jira/browse/SYNCOPE-1134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16068128#comment-16068128 ] Matteo Alessandroni commented on SYNCOPE-1134: -- Update: the issue comes out only when action menu is visible before refreshing. > Action menu not working after page refresh > -- > > Key: SYNCOPE-1134 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1134 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.0.3 >Reporter: Andrea Patricelli >Priority: Minor > Fix For: 2.0.4, 2.1.0 > > > # Login on Syncope Admin Console > # Go to Realms -> USER page and click on some user > # An action menu will be shown on the right > # Refresh the page with CTRL+R or CTRL+SHIFT+R or refresh button. > # Click again on some user -> action menu will NOT appear and you need to > change page in order to let it wotk again. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SYNCOPE-1145) Connector and Resource configuration versioning
[ https://issues.apache.org/jira/browse/SYNCOPE-1145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16076088#comment-16076088 ] Matteo Alessandroni commented on SYNCOPE-1145: -- Hallo, I'd be happy to contribute by starting working on the console side. Is it ok for you? Matteo > Connector and Resource configuration versioning > --- > > Key: SYNCOPE-1145 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1145 > Project: Syncope > Issue Type: New Feature > Components: common, console, core >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò > Fix For: 2.0.5, 2.1.0 > > > It often happens that, while playing with Connectors' and Resources' > configuration, everything works up until a certain point, then some > misconfiguration happens and errors start appearing. > In such situations, it would be handy to have a simple mechanism to revert to > a previous (working) situation. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SYNCOPE-1145) Connector and Resource configuration versioning
[ https://issues.apache.org/jira/browse/SYNCOPE-1145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16076093#comment-16076093 ] Matteo Alessandroni commented on SYNCOPE-1145: -- Great, glad to help. Thank you! > Connector and Resource configuration versioning > --- > > Key: SYNCOPE-1145 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1145 > Project: Syncope > Issue Type: New Feature > Components: common, console, core >Reporter: Francesco Chicchiriccò >Assignee: Francesco Chicchiriccò > Fix For: 2.0.5, 2.1.0 > > > It often happens that, while playing with Connectors' and Resources' > configuration, everything works up until a certain point, then some > misconfiguration happens and errors start appearing. > In such situations, it would be handy to have a simple mechanism to revert to > a previous (working) situation. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SYNCOPE-1151) Glinch in the root realm information
[ https://issues.apache.org/jira/browse/SYNCOPE-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16085422#comment-16085422 ] Matteo Alessandroni commented on SYNCOPE-1151: -- Hi, Root realm can't be propagated to external resources, so the solution should be not to show the 'Assigned resources' block when in '/' realm. I'll open a PR for that. Matteo > Glinch in the root realm information > - > > Key: SYNCOPE-1151 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1151 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.0.4 >Reporter: Filipe Silva >Priority: Minor > Fix For: 2.0.5, 2.1.0 > > Attachments: Selection_032.png, Selection_033.png > > > A small incoherence in the root real info screen and edit screen: > Choosing the realms (left side) or choosing the root ( / ) realm gives (see > Selection_032.png file) > !Selection_032.png|thumbnail! > but after creating an realm "below" the root it gives (see Selection_033.png > file) > !Selection_033.png|thumbnail! > (I highlight the change) > I think that the last one is the correct one because that in the only way to > in the edit realm screen of the root ( / ) to be able to edit the assigned > resources (because it also changes) -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SYNCOPE-1170) Can't remove a "Dynamic USER assignment"
[ https://issues.apache.org/jira/browse/SYNCOPE-1170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni updated SYNCOPE-1170: - Component/s: (was: console) common > Can't remove a "Dynamic USER assignment" > > > Key: SYNCOPE-1170 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1170 > Project: Syncope > Issue Type: Bug > Components: common >Reporter: Colm O hEigeartaigh >Assignee: Matteo Alessandroni > Fix For: 2.0.5, 2.1.0 > > > Steps to reproduce: > a) Create a user "alice". > b) Create a group "employee" with a dynamic user assignment (username == > alice). > c) Verify that alice is a dynamic member of the group "employee". > d) Now edit "employee" and "-" the search condition for dynamic user > assignment and click finish. > e) The condition is not deleted as expected, alice is still a member of the > group. Edit the group again and the dynamic user condition search is still in > place. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (SYNCOPE-1170) Can't remove a "Dynamic USER assignment"
[ https://issues.apache.org/jira/browse/SYNCOPE-1170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni reassigned SYNCOPE-1170: Assignee: Matteo Alessandroni > Can't remove a "Dynamic USER assignment" > > > Key: SYNCOPE-1170 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1170 > Project: Syncope > Issue Type: Bug > Components: common >Reporter: Colm O hEigeartaigh >Assignee: Matteo Alessandroni > Fix For: 2.0.5, 2.1.0 > > > Steps to reproduce: > a) Create a user "alice". > b) Create a group "employee" with a dynamic user assignment (username == > alice). > c) Verify that alice is a dynamic member of the group "employee". > d) Now edit "employee" and "-" the search condition for dynamic user > assignment and click finish. > e) The condition is not deleted as expected, alice is still a member of the > group. Edit the group again and the dynamic user condition search is still in > place. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SYNCOPE-1181) Conditions in "Search Panel"
Matteo Alessandroni created SYNCOPE-1181: Summary: Conditions in "Search Panel" Key: SYNCOPE-1181 URL: https://issues.apache.org/jira/browse/SYNCOPE-1181 Project: Syncope Issue Type: Improvement Reporter: Matteo Alessandroni -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SYNCOPE-1181) Conditions in Search Panel are multiplied while editing groups or users
[ https://issues.apache.org/jira/browse/SYNCOPE-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni updated SYNCOPE-1181: - Component/s: console Summary: Conditions in Search Panel are multiplied while editing groups or users (was: Conditions in "Search Panel" ) > Conditions in Search Panel are multiplied while editing groups or users > --- > > Key: SYNCOPE-1181 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1181 > Project: Syncope > Issue Type: Improvement > Components: console >Reporter: Matteo Alessandroni > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SYNCOPE-1181) Conditions in Search Panel are multiplied while editing groups or users
[ https://issues.apache.org/jira/browse/SYNCOPE-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni updated SYNCOPE-1181: - Description: Steps to reproduce: * Go to 'Groups' view * Edit one group * Navigate the wizard until you find the Dynamic assignments step * Add one condition and make sure it's filled and correct, for instance in 'Dynamic USER assignment' accordion * Click 'finish' * Re-edit the same group * Navigate the wizard until you find the Dynamic assignments step * Add one new condition without filling the dropdowns (they all should show the 'Choose one' option) * Click 'finish' > Conditions in Search Panel are multiplied while editing groups or users > --- > > Key: SYNCOPE-1181 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1181 > Project: Syncope > Issue Type: Improvement > Components: console >Reporter: Matteo Alessandroni > > Steps to reproduce: > * Go to 'Groups' view > * Edit one group > * Navigate the wizard until you find the Dynamic assignments step > * Add one condition and make sure it's filled and correct, for instance in > 'Dynamic USER assignment' accordion > * Click 'finish' > * Re-edit the same group > * Navigate the wizard until you find the Dynamic assignments step > * Add one new condition without filling the dropdowns (they all should show > the 'Choose one' option) > * Click 'finish' -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (SYNCOPE-1170) Can't remove a "Dynamic USER assignment"
[ https://issues.apache.org/jira/browse/SYNCOPE-1170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni resolved SYNCOPE-1170. -- Resolution: Fixed > Can't remove a "Dynamic USER assignment" > > > Key: SYNCOPE-1170 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1170 > Project: Syncope > Issue Type: Bug > Components: common >Reporter: Colm O hEigeartaigh >Assignee: Matteo Alessandroni > Fix For: 2.0.5, 2.1.0 > > > Steps to reproduce: > a) Create a user "alice". > b) Create a group "employee" with a dynamic user assignment (username == > alice). > c) Verify that alice is a dynamic member of the group "employee". > d) Now edit "employee" and "-" the search condition for dynamic user > assignment and click finish. > e) The condition is not deleted as expected, alice is still a member of the > group. Edit the group again and the dynamic user condition search is still in > place. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (SYNCOPE-1178) PlainSchema page empty while self update on Enduser
[ https://issues.apache.org/jira/browse/SYNCOPE-1178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni reassigned SYNCOPE-1178: Assignee: Matteo Alessandroni > PlainSchema page empty while self update on Enduser > > > Key: SYNCOPE-1178 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1178 > Project: Syncope > Issue Type: Bug > Components: enduser >Reporter: Andrea Patricelli >Assignee: Matteo Alessandroni > Fix For: 2.0.5, 2.1.0 > > > Sometimes, while updating an user, PlainSchema tab is empty and this also > leads test to fail. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (SYNCOPE-1170) Can't remove a "Dynamic USER assignment"
[ https://issues.apache.org/jira/browse/SYNCOPE-1170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni closed SYNCOPE-1170. > Can't remove a "Dynamic USER assignment" > > > Key: SYNCOPE-1170 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1170 > Project: Syncope > Issue Type: Bug > Components: common >Reporter: Colm O hEigeartaigh >Assignee: Matteo Alessandroni > Fix For: 2.0.5, 2.1.0 > > > Steps to reproduce: > a) Create a user "alice". > b) Create a group "employee" with a dynamic user assignment (username == > alice). > c) Verify that alice is a dynamic member of the group "employee". > d) Now edit "employee" and "-" the search condition for dynamic user > assignment and click finish. > e) The condition is not deleted as expected, alice is still a member of the > group. Edit the group again and the dynamic user condition search is still in > place. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Reopened] (SYNCOPE-1170) Can't remove a "Dynamic USER assignment"
[ https://issues.apache.org/jira/browse/SYNCOPE-1170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni reopened SYNCOPE-1170: -- > Can't remove a "Dynamic USER assignment" > > > Key: SYNCOPE-1170 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1170 > Project: Syncope > Issue Type: Bug > Components: common >Reporter: Colm O hEigeartaigh >Assignee: Matteo Alessandroni > Fix For: 2.0.5, 2.1.0 > > > Steps to reproduce: > a) Create a user "alice". > b) Create a group "employee" with a dynamic user assignment (username == > alice). > c) Verify that alice is a dynamic member of the group "employee". > d) Now edit "employee" and "-" the search condition for dynamic user > assignment and click finish. > e) The condition is not deleted as expected, alice is still a member of the > group. Edit the group again and the dynamic user condition search is still in > place. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (SYNCOPE-1170) Can't remove a "Dynamic USER assignment"
[ https://issues.apache.org/jira/browse/SYNCOPE-1170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni resolved SYNCOPE-1170. -- Resolution: Fixed > Can't remove a "Dynamic USER assignment" > > > Key: SYNCOPE-1170 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1170 > Project: Syncope > Issue Type: Bug > Components: common >Reporter: Colm O hEigeartaigh >Assignee: Matteo Alessandroni > Fix For: 2.0.5, 2.1.0 > > > Steps to reproduce: > a) Create a user "alice". > b) Create a group "employee" with a dynamic user assignment (username == > alice). > c) Verify that alice is a dynamic member of the group "employee". > d) Now edit "employee" and "-" the search condition for dynamic user > assignment and click finish. > e) The condition is not deleted as expected, alice is still a member of the > group. Edit the group again and the dynamic user condition search is still in > place. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SYNCOPE-1178) PlainSchema page empty while self update on Enduser
[ https://issues.apache.org/jira/browse/SYNCOPE-1178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni updated SYNCOPE-1178: - Component/s: core > PlainSchema page empty while self update on Enduser > > > Key: SYNCOPE-1178 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1178 > Project: Syncope > Issue Type: Bug > Components: core, enduser >Reporter: Andrea Patricelli >Assignee: Matteo Alessandroni > Fix For: 2.0.5, 2.1.0 > > > Sometimes, while updating an user, PlainSchema tab is empty and this also > leads test to fail. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (SYNCOPE-1178) PlainSchema page empty while self update on Enduser
[ https://issues.apache.org/jira/browse/SYNCOPE-1178?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni resolved SYNCOPE-1178. -- Resolution: Fixed > PlainSchema page empty while self update on Enduser > > > Key: SYNCOPE-1178 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1178 > Project: Syncope > Issue Type: Bug > Components: core, enduser >Reporter: Andrea Patricelli >Assignee: Matteo Alessandroni > Fix For: 2.0.5, 2.1.0 > > > Sometimes, while updating an user, PlainSchema tab is empty and this also > leads test to fail. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (SYNCOPE-1155) Hard-coded /syncope-enduser HTTP subcontext
[
https://issues.apache.org/jira/browse/SYNCOPE-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matteo Alessandroni reassigned SYNCOPE-1155:
Assignee: Matteo Alessandroni
> Hard-coded /syncope-enduser HTTP subcontext
> ---
>
> Key: SYNCOPE-1155
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1155
> Project: Syncope
> Issue Type: Improvement
> Components: enduser
>Reporter: Francesco Chicchiriccò
>Assignee: Matteo Alessandroni
> Fix For: 2.0.5, 2.1.0
>
>
> Several files in the Enduser JS sources contain references like as follows:
> {code}
> any.getAuxClasses = function () {
> return $http.get("/syncope-enduser/api/auxClasses")
> .then(function (response) {
> return response.data;
> }, function (response) {
> console.error("Something went wrong during
> auxiliaryClasses retrieval, exit with status: ",
> response);
> return $q.reject(response.data ||
> response.statusText);
> });
> };
> {code}
> e.g. static references to {{/syncope-enduser}}.
> This would cause troubles when there is need to deploy the WAR file with a
> different name, or behind a reverse proxy.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (SYNCOPE-1155) Hard-coded /syncope-enduser HTTP subcontext
[
https://issues.apache.org/jira/browse/SYNCOPE-1155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matteo Alessandroni resolved SYNCOPE-1155.
--
Resolution: Fixed
> Hard-coded /syncope-enduser HTTP subcontext
> ---
>
> Key: SYNCOPE-1155
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1155
> Project: Syncope
> Issue Type: Improvement
> Components: enduser
>Reporter: Francesco Chicchiriccò
>Assignee: Matteo Alessandroni
> Fix For: 2.0.5, 2.1.0
>
>
> Several files in the Enduser JS sources contain references like as follows:
> {code}
> any.getAuxClasses = function () {
> return $http.get("/syncope-enduser/api/auxClasses")
> .then(function (response) {
> return response.data;
> }, function (response) {
> console.error("Something went wrong during
> auxiliaryClasses retrieval, exit with status: ",
> response);
> return $q.reject(response.data ||
> response.statusText);
> });
> };
> {code}
> e.g. static references to {{/syncope-enduser}}.
> This would cause troubles when there is need to deploy the WAR file with a
> different name, or behind a reverse proxy.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (SYNCOPE-1183) Realm attribute available (as a detail) to use as a column in the "realm view" object list
[ https://issues.apache.org/jira/browse/SYNCOPE-1183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni reassigned SYNCOPE-1183: Assignee: Matteo Alessandroni > Realm attribute available (as a detail) to use as a column in the "realm > view" object list > -- > > Key: SYNCOPE-1183 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1183 > Project: Syncope > Issue Type: Improvement > Components: console >Reporter: Filipe Silva >Assignee: Matteo Alessandroni >Priority: Trivial > Fix For: 2.0.5, 2.1.0 > > > Hi > I have to create a derived schema for each AnyType (with realm as the > Expression) in syncope to be able to provide in the realm object list that > information (very useful if in a parent realm). > I would suggest to have that info available as a detail in the column list > for use. > Thanks > Filipe Silva -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (SYNCOPE-1183) Realm attribute available (as a detail) to use as a column in the "realm view" object list
[ https://issues.apache.org/jira/browse/SYNCOPE-1183?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni resolved SYNCOPE-1183. -- Resolution: Fixed > Realm attribute available (as a detail) to use as a column in the "realm > view" object list > -- > > Key: SYNCOPE-1183 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1183 > Project: Syncope > Issue Type: Improvement > Components: console >Reporter: Filipe Silva >Assignee: Matteo Alessandroni >Priority: Trivial > Fix For: 2.0.5, 2.1.0 > > > Hi > I have to create a derived schema for each AnyType (with realm as the > Expression) in syncope to be able to provide in the realm object list that > information (very useful if in a parent realm). > I would suggest to have that info available as a detail in the column list > for use. > Thanks > Filipe Silva -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (SYNCOPE-1161) Option to clone a resource
[ https://issues.apache.org/jira/browse/SYNCOPE-1161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni reassigned SYNCOPE-1161: Assignee: Matteo Alessandroni > Option to clone a resource > -- > > Key: SYNCOPE-1161 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1161 > Project: Syncope > Issue Type: Wish > Components: console >Affects Versions: 2.0.4 >Reporter: Filipe Silva >Assignee: Matteo Alessandroni >Priority: Minor > Fix For: 2.0.5, 2.1.0 > > > Sometimes we need to create a new resource in a connector based in a previous > one (for instance to separate the provision types) an option to clone the > resource would be nice -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (SYNCOPE-1161) Option to clone a resource
[ https://issues.apache.org/jira/browse/SYNCOPE-1161?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni resolved SYNCOPE-1161. -- Resolution: Fixed > Option to clone a resource > -- > > Key: SYNCOPE-1161 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1161 > Project: Syncope > Issue Type: Wish > Components: console >Affects Versions: 2.0.4 >Reporter: Filipe Silva >Assignee: Matteo Alessandroni >Priority: Minor > Fix For: 2.0.5, 2.1.0 > > > Sometimes we need to create a new resource in a connector based in a previous > one (for instance to separate the provision types) an option to clone the > resource would be nice -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (SYNCOPE-1171) Skip Relationships page when no relationship types exist
[ https://issues.apache.org/jira/browse/SYNCOPE-1171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni reassigned SYNCOPE-1171: Assignee: Matteo Alessandroni > Skip Relationships page when no relationship types exist > > > Key: SYNCOPE-1171 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1171 > Project: Syncope > Issue Type: Improvement > Components: console >Reporter: Colm O hEigeartaigh >Assignee: Matteo Alessandroni >Priority: Trivial > Fix For: 2.0.5, 2.1.0 > > Attachments: relationships.png > > > When creating a new user in the console, with no relationship types defined, > you come to a page that says: > Relationships > No relationships defined > It would be better just to skip this page altogether if no relationship types > are available. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (SYNCOPE-1171) Skip Relationships page when no relationship types exist
[ https://issues.apache.org/jira/browse/SYNCOPE-1171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni resolved SYNCOPE-1171. -- Resolution: Fixed > Skip Relationships page when no relationship types exist > > > Key: SYNCOPE-1171 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1171 > Project: Syncope > Issue Type: Improvement > Components: console >Reporter: Colm O hEigeartaigh >Assignee: Matteo Alessandroni >Priority: Trivial > Fix For: 2.0.5, 2.1.0 > > Attachments: relationships.png > > > When creating a new user in the console, with no relationship types defined, > you come to a page that says: > Relationships > No relationships defined > It would be better just to skip this page altogether if no relationship types > are available. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (SYNCOPE-1115) Display attributes for propagation tasks
[
https://issues.apache.org/jira/browse/SYNCOPE-1115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matteo Alessandroni reassigned SYNCOPE-1115:
Assignee: Matteo Alessandroni
> Display attributes for propagation tasks
>
>
> Key: SYNCOPE-1115
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1115
> Project: Syncope
> Issue Type: Improvement
> Components: console
>Reporter: Francesco Chicchiriccò
>Assignee: Matteo Alessandroni
> Fix For: 2.0.5, 2.1.0
>
>
> The set of attributes sent with a propagation task are available in the
> {{PropagationTaskTO}} as JSON string in the {{attributes}} field.
> It can be shown through the recent {{BinaryTextPreviewer}} from SYNCOPE-1095.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (SYNCOPE-1115) Display attributes for propagation tasks
[
https://issues.apache.org/jira/browse/SYNCOPE-1115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matteo Alessandroni resolved SYNCOPE-1115.
--
Resolution: Fixed
> Display attributes for propagation tasks
>
>
> Key: SYNCOPE-1115
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1115
> Project: Syncope
> Issue Type: Improvement
> Components: console
>Reporter: Francesco Chicchiriccò
>Assignee: Matteo Alessandroni
> Fix For: 2.0.5, 2.1.0
>
>
> The set of attributes sent with a propagation task are available in the
> {{PropagationTaskTO}} as JSON string in the {{attributes}} field.
> It can be shown through the recent {{BinaryTextPreviewer}} from SYNCOPE-1095.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (SYNCOPE-1096) Download button should be disabled while populating for the first time a binary attribute
[ https://issues.apache.org/jira/browse/SYNCOPE-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni reassigned SYNCOPE-1096: Assignee: Matteo Alessandroni > Download button should be disabled while populating for the first time a > binary attribute > - > > Key: SYNCOPE-1096 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1096 > Project: Syncope > Issue Type: Improvement > Components: console >Affects Versions: 2.0.3 >Reporter: Andrea Patricelli >Assignee: Matteo Alessandroni >Priority: Minor > Fix For: 2.0.5, 2.1.0 > > > Download button does not work on first binary attribute set. It should be > disabled otherwise it is misleading viewing the preview (if available) and > not beaing able to download the content. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (SYNCOPE-1096) Download button should be disabled while populating for the first time a binary attribute
[ https://issues.apache.org/jira/browse/SYNCOPE-1096?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni resolved SYNCOPE-1096. -- Resolution: Fixed > Download button should be disabled while populating for the first time a > binary attribute > - > > Key: SYNCOPE-1096 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1096 > Project: Syncope > Issue Type: Improvement > Components: console >Affects Versions: 2.0.3 >Reporter: Andrea Patricelli >Assignee: Matteo Alessandroni >Priority: Minor > Fix For: 2.0.5, 2.1.0 > > > Download button does not work on first binary attribute set. It should be > disabled otherwise it is misleading viewing the preview (if available) and > not beaing able to download the content. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (SYNCOPE-1097) Downloaded file for binary attribute better naming
[ https://issues.apache.org/jira/browse/SYNCOPE-1097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni reassigned SYNCOPE-1097: Assignee: Matteo Alessandroni > Downloaded file for binary attribute better naming > -- > > Key: SYNCOPE-1097 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1097 > Project: Syncope > Issue Type: Improvement > Components: console >Reporter: Andrea Patricelli >Assignee: Matteo Alessandroni >Priority: Minor > Fix For: 2.0.5, 2.1.0 > > > Name of the downloaded file should be like: _. extension for that mimetype> -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (SYNCOPE-1190) Username not refreshed on toggle menu after user update
[ https://issues.apache.org/jira/browse/SYNCOPE-1190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni reassigned SYNCOPE-1190: Assignee: Matteo Alessandroni > Username not refreshed on toggle menu after user update > --- > > Key: SYNCOPE-1190 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1190 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.0.4 >Reporter: Andrea Patricelli >Assignee: Matteo Alessandroni >Priority: Minor > Fix For: 2.0.5, 2.1.0 > > > 1. Login into console > 2. Edit user username and save > 3. you'll see that username is not updated into toggle panel -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (SYNCOPE-1097) Downloaded file for binary attribute better naming
[ https://issues.apache.org/jira/browse/SYNCOPE-1097?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni resolved SYNCOPE-1097. -- Resolution: Fixed > Downloaded file for binary attribute better naming > -- > > Key: SYNCOPE-1097 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1097 > Project: Syncope > Issue Type: Improvement > Components: console >Reporter: Andrea Patricelli >Assignee: Matteo Alessandroni >Priority: Minor > Fix For: 2.0.5, 2.1.0 > > > Name of the downloaded file should be like: _. extension for that mimetype> -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (SYNCOPE-1190) Username not refreshed on toggle menu after user update
[ https://issues.apache.org/jira/browse/SYNCOPE-1190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni resolved SYNCOPE-1190. -- Resolution: Fixed > Username not refreshed on toggle menu after user update > --- > > Key: SYNCOPE-1190 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1190 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.0.4 >Reporter: Andrea Patricelli >Assignee: Matteo Alessandroni >Priority: Minor > Fix For: 2.0.5, 2.1.0 > > > 1. Login into console > 2. Edit user username and save > 3. you'll see that username is not updated into toggle panel -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (SYNCOPE-1181) Conditions in Search Panel are multiplied while editing groups or users
[ https://issues.apache.org/jira/browse/SYNCOPE-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni reassigned SYNCOPE-1181: Assignee: Matteo Alessandroni > Conditions in Search Panel are multiplied while editing groups or users > --- > > Key: SYNCOPE-1181 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1181 > Project: Syncope > Issue Type: Improvement > Components: console >Reporter: Matteo Alessandroni >Assignee: Matteo Alessandroni > > Steps to reproduce: > * Go to 'Groups' view > * Edit one group > * Navigate the wizard until you find the Dynamic assignments step > * Add one condition and make sure it's filled and correct, for instance in > 'Dynamic USER assignment' accordion > * Click 'finish' > * Re-edit the same group > * Navigate the wizard until you find the Dynamic assignments step > * Add one new condition without filling the dropdowns (they all should show > the 'Choose one' option) > * Click 'finish' -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Reopened] (SYNCOPE-1190) Username not refreshed on toggle menu after user update
[
https://issues.apache.org/jira/browse/SYNCOPE-1190?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matteo Alessandroni reopened SYNCOPE-1190:
--
Reopening because it creates problems in other situations like "cloning",
"creating" etc...
The problem is while sending the
{{TogglePanel.ActionLinkToggleUpdateEventPayload}} event when clicking "finish"
in each wizard.
Still working on it!
> Username not refreshed on toggle menu after user update
> ---
>
> Key: SYNCOPE-1190
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1190
> Project: Syncope
> Issue Type: Bug
> Components: console
>Affects Versions: 2.0.4
>Reporter: Andrea Patricelli
>Assignee: Matteo Alessandroni
>Priority: Minor
> Fix For: 2.0.5, 2.1.0
>
>
> 1. Login into console
> 2. Edit user username and save
> 3. you'll see that username is not updated into toggle panel
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (SYNCOPE-1181) Conditions in Search Panel are multiplied while editing groups or users
[ https://issues.apache.org/jira/browse/SYNCOPE-1181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni resolved SYNCOPE-1181. -- Resolution: Fixed > Conditions in Search Panel are multiplied while editing groups or users > --- > > Key: SYNCOPE-1181 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1181 > Project: Syncope > Issue Type: Improvement > Components: console >Reporter: Matteo Alessandroni >Assignee: Matteo Alessandroni > > Steps to reproduce: > * Go to 'Groups' view > * Edit one group > * Navigate the wizard until you find the Dynamic assignments step > * Add one condition and make sure it's filled and correct, for instance in > 'Dynamic USER assignment' accordion > * Click 'finish' > * Re-edit the same group > * Navigate the wizard until you find the Dynamic assignments step > * Add one new condition without filling the dropdowns (they all should show > the 'Choose one' option) > * Click 'finish' -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (SYNCOPE-1199) Syncope performance: AnyObjectTO's creation time grows with it's quantity
[
https://issues.apache.org/jira/browse/SYNCOPE-1199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matteo Alessandroni reassigned SYNCOPE-1199:
Assignee: Matteo Alessandroni
> Syncope performance: AnyObjectTO's creation time grows with it's quantity
> -
>
> Key: SYNCOPE-1199
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1199
> Project: Syncope
> Issue Type: Bug
>Affects Versions: 2.0.2, 2.0.4
> Environment: Syncope 2.0.2 and 2.0.4 + PostgreSQL 9; Jmeter;
> https://github.com/Talend/platform-services/tree/master/iam/idp
>Reporter: Iurii Smyrnov
>Assignee: Matteo Alessandroni
> Attachments: CreateTestSyncope.jmx, Latency for 1000 create roles
> (directly syncope 2.0.4) no SCIM.csv, Latency for 1000 create roles (directly
> syncope 2.0.4).png, Latency for 1037 create roles (directly syncope 2.0.2) no
> SCIM.csv, Latency for 1037 create roles (directly syncope 2.0.2).png, Latency
> for 3000 create roles (directly syncope 2.0.2).csv, Latency for 3000 create
> roles (directly syncope 2.0.2).png, Latency for 3000 create roles (directly
> syncope 2.0.4).png, MasterContent.xml
>
>
> *AnyObjetcTO's creation time (latency) grows with it's quantity.*
> Testing results are attached (Latency in milliseconds).
> Note: We've tested PostgreSQL DB directly (without Syncope) and we've got
> stable AnyObjetcTO's creation time (not increasing).
> User Syncope 2.0.4 or 2.0.4 and + PostgreSQL 9
> URI: http://localhost:9080/syncope/rest/anyObjects
> http headers:
> 1.Content-Type / application/json
> 2 Accept / application/json
> verb: POST
> body:
> {
> "plainAttrs":[
> {
>"values":[
> "test-value"
>],
>"schema":"roleEntitlements"
> }
> ],
> "type":"RoleAT",
> "realm":"/",
> "@class":"org.apache.syncope.common.lib.to.AnyObjectTO",
> "auxClasses":["RoleATClass"],
> "name":"Role_Account_1"
> }
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (SYNCOPE-1199) Syncope performance: AnyObjectTO's creation time grows with it's quantity
[
https://issues.apache.org/jira/browse/SYNCOPE-1199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matteo Alessandroni closed SYNCOPE-1199.
Resolution: Not A Problem
At the beginning we had the same problem, but we found out that the problem was
related to the *Postgres JDBC Driver* version.
In my case the old default version (I used the one from
{{/usr/share/java/postgresql-jdbc4.jar}}, version 9.2) was causing a lot of
latency during tests.
Upgrading to a newer version solved the problem.
I have attached the results of the last jMeter test I have successfully
executed.
Regards,
Matteo
> Syncope performance: AnyObjectTO's creation time grows with it's quantity
> -
>
> Key: SYNCOPE-1199
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1199
> Project: Syncope
> Issue Type: Bug
>Affects Versions: 2.0.2, 2.0.4
> Environment: Syncope 2.0.2 and 2.0.4 + PostgreSQL 9; Jmeter;
> https://github.com/Talend/platform-services/tree/master/iam/idp
>Reporter: Iurii Smyrnov
>Assignee: Matteo Alessandroni
> Attachments: CreateTestSyncope.jmx, Latency for 1000 create roles
> (directly syncope 2.0.4) no SCIM.csv, Latency for 1000 create roles (directly
> syncope 2.0.4).png, Latency for 1037 create roles (directly syncope 2.0.2) no
> SCIM.csv, Latency for 1037 create roles (directly syncope 2.0.2).png, Latency
> for 3000 create roles (directly syncope 2.0.2).csv, Latency for 3000 create
> roles (directly syncope 2.0.2).png, Latency for 3000 create roles (directly
> syncope 2.0.4).png, MasterContent.xml
>
>
> *AnyObjetcTO's creation time (latency) grows with it's quantity.*
> Testing results are attached (Latency in milliseconds).
> Note: We've tested PostgreSQL DB directly (without Syncope) and we've got
> stable AnyObjetcTO's creation time (not increasing).
> User Syncope 2.0.4 or 2.0.4 and + PostgreSQL 9
> URI: http://localhost:9080/syncope/rest/anyObjects
> http headers:
> 1.Content-Type / application/json
> 2 Accept / application/json
> verb: POST
> body:
> {
> "plainAttrs":[
> {
>"values":[
> "test-value"
>],
>"schema":"roleEntitlements"
> }
> ],
> "type":"RoleAT",
> "realm":"/",
> "@class":"org.apache.syncope.common.lib.to.AnyObjectTO",
> "auxClasses":["RoleATClass"],
> "name":"Role_Account_1"
> }
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Reopened] (SYNCOPE-1199) Syncope performance: AnyObjectTO's creation time grows with it's quantity
[
https://issues.apache.org/jira/browse/SYNCOPE-1199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matteo Alessandroni reopened SYNCOPE-1199:
--
> Syncope performance: AnyObjectTO's creation time grows with it's quantity
> -
>
> Key: SYNCOPE-1199
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1199
> Project: Syncope
> Issue Type: Bug
>Affects Versions: 2.0.2, 2.0.4
> Environment: Syncope 2.0.2 and 2.0.4 + PostgreSQL 9; Jmeter;
> https://github.com/Talend/platform-services/tree/master/iam/idp
>Reporter: Iurii Smyrnov
>Assignee: Matteo Alessandroni
> Attachments: CreateTestSyncope.jmx, Latency for 1000 create roles
> (directly syncope 2.0.4) no SCIM.csv, Latency for 1000 create roles (directly
> syncope 2.0.4).png, Latency for 1037 create roles (directly syncope 2.0.2) no
> SCIM.csv, Latency for 1037 create roles (directly syncope 2.0.2).png, Latency
> for 3000 create roles (directly syncope 2.0.2).csv, Latency for 3000 create
> roles (directly syncope 2.0.2).png, Latency for 3000 create roles (directly
> syncope 2.0.4).png, MasterContent.xml
>
>
> *AnyObjetcTO's creation time (latency) grows with it's quantity.*
> Testing results are attached (Latency in milliseconds).
> Note: We've tested PostgreSQL DB directly (without Syncope) and we've got
> stable AnyObjetcTO's creation time (not increasing).
> User Syncope 2.0.4 or 2.0.4 and + PostgreSQL 9
> URI: http://localhost:9080/syncope/rest/anyObjects
> http headers:
> 1.Content-Type / application/json
> 2 Accept / application/json
> verb: POST
> body:
> {
> "plainAttrs":[
> {
>"values":[
> "test-value"
>],
>"schema":"roleEntitlements"
> }
> ],
> "type":"RoleAT",
> "realm":"/",
> "@class":"org.apache.syncope.common.lib.to.AnyObjectTO",
> "auxClasses":["RoleATClass"],
> "name":"Role_Account_1"
> }
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (SYNCOPE-1199) Syncope performance: AnyObjectTO's creation time grows with it's quantity
[
https://issues.apache.org/jira/browse/SYNCOPE-1199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matteo Alessandroni updated SYNCOPE-1199:
-
Attachment: CreateTestSyncope_onlyCreationAggregateReport_AnyObject.csv
CreateTestSyncope_graph_AnyObject.csv
CreateTestSyncope_genericResults_AnyObject.csv
> Syncope performance: AnyObjectTO's creation time grows with it's quantity
> -
>
> Key: SYNCOPE-1199
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1199
> Project: Syncope
> Issue Type: Bug
>Affects Versions: 2.0.2, 2.0.4
> Environment: Syncope 2.0.2 and 2.0.4 + PostgreSQL 9; Jmeter;
> https://github.com/Talend/platform-services/tree/master/iam/idp
>Reporter: Iurii Smyrnov
>Assignee: Matteo Alessandroni
> Attachments: CreateTestSyncope_genericResults_AnyObject.csv,
> CreateTestSyncope_graph_AnyObject.csv, CreateTestSyncope.jmx,
> CreateTestSyncope_onlyCreationAggregateReport_AnyObject.csv, Latency for 1000
> create roles (directly syncope 2.0.4) no SCIM.csv, Latency for 1000 create
> roles (directly syncope 2.0.4).png, Latency for 1037 create roles (directly
> syncope 2.0.2) no SCIM.csv, Latency for 1037 create roles (directly syncope
> 2.0.2).png, Latency for 3000 create roles (directly syncope 2.0.2).csv,
> Latency for 3000 create roles (directly syncope 2.0.2).png, Latency for 3000
> create roles (directly syncope 2.0.4).png, MasterContent.xml
>
>
> *AnyObjetcTO's creation time (latency) grows with it's quantity.*
> Testing results are attached (Latency in milliseconds).
> Note: We've tested PostgreSQL DB directly (without Syncope) and we've got
> stable AnyObjetcTO's creation time (not increasing).
> User Syncope 2.0.4 or 2.0.4 and + PostgreSQL 9
> URI: http://localhost:9080/syncope/rest/anyObjects
> http headers:
> 1.Content-Type / application/json
> 2 Accept / application/json
> verb: POST
> body:
> {
> "plainAttrs":[
> {
>"values":[
> "test-value"
>],
>"schema":"roleEntitlements"
> }
> ],
> "type":"RoleAT",
> "realm":"/",
> "@class":"org.apache.syncope.common.lib.to.AnyObjectTO",
> "auxClasses":["RoleATClass"],
> "name":"Role_Account_1"
> }
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (SYNCOPE-1199) Syncope performance: AnyObjectTO's creation time grows with it's quantity
[
https://issues.apache.org/jira/browse/SYNCOPE-1199?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Matteo Alessandroni closed SYNCOPE-1199.
Resolution: Not A Problem
> Syncope performance: AnyObjectTO's creation time grows with it's quantity
> -
>
> Key: SYNCOPE-1199
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1199
> Project: Syncope
> Issue Type: Bug
>Affects Versions: 2.0.2, 2.0.4
> Environment: Syncope 2.0.2 and 2.0.4 + PostgreSQL 9; Jmeter;
> https://github.com/Talend/platform-services/tree/master/iam/idp
>Reporter: Iurii Smyrnov
>Assignee: Matteo Alessandroni
> Attachments: CreateTestSyncope_genericResults_AnyObject.csv,
> CreateTestSyncope_graph_AnyObject.csv, CreateTestSyncope.jmx,
> CreateTestSyncope_onlyCreationAggregateReport_AnyObject.csv, Latency for 1000
> create roles (directly syncope 2.0.4) no SCIM.csv, Latency for 1000 create
> roles (directly syncope 2.0.4).png, Latency for 1037 create roles (directly
> syncope 2.0.2) no SCIM.csv, Latency for 1037 create roles (directly syncope
> 2.0.2).png, Latency for 3000 create roles (directly syncope 2.0.2).csv,
> Latency for 3000 create roles (directly syncope 2.0.2).png, Latency for 3000
> create roles (directly syncope 2.0.4).png, MasterContent.xml
>
>
> *AnyObjetcTO's creation time (latency) grows with it's quantity.*
> Testing results are attached (Latency in milliseconds).
> Note: We've tested PostgreSQL DB directly (without Syncope) and we've got
> stable AnyObjetcTO's creation time (not increasing).
> User Syncope 2.0.4 or 2.0.4 and + PostgreSQL 9
> URI: http://localhost:9080/syncope/rest/anyObjects
> http headers:
> 1.Content-Type / application/json
> 2 Accept / application/json
> verb: POST
> body:
> {
> "plainAttrs":[
> {
>"values":[
> "test-value"
>],
>"schema":"roleEntitlements"
> }
> ],
> "type":"RoleAT",
> "realm":"/",
> "@class":"org.apache.syncope.common.lib.to.AnyObjectTO",
> "auxClasses":["RoleATClass"],
> "name":"Role_Account_1"
> }
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (SYNCOPE-1199) Syncope performance: AnyObjectTO's creation time grows with it's quantity
[
https://issues.apache.org/jira/browse/SYNCOPE-1199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16141578#comment-16141578
]
Matteo Alessandroni commented on SYNCOPE-1199:
--
I have used [this
one|https://search.maven.org/remotecontent?filepath=org/postgresql/postgresql/42.1.4/postgresql-42.1.4.jar]
> Syncope performance: AnyObjectTO's creation time grows with it's quantity
> -
>
> Key: SYNCOPE-1199
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1199
> Project: Syncope
> Issue Type: Bug
>Affects Versions: 2.0.2, 2.0.4
> Environment: Syncope 2.0.2 and 2.0.4 + PostgreSQL 9; Jmeter;
> https://github.com/Talend/platform-services/tree/master/iam/idp
>Reporter: Iurii Smyrnov
>Assignee: Matteo Alessandroni
> Attachments: CreateTestSyncope_genericResults_AnyObject.csv,
> CreateTestSyncope_graph_AnyObject.csv, CreateTestSyncope.jmx,
> CreateTestSyncope_onlyCreationAggregateReport_AnyObject.csv, Latency for 1000
> create roles (directly syncope 2.0.4) no SCIM.csv, Latency for 1000 create
> roles (directly syncope 2.0.4).png, Latency for 1037 create roles (directly
> syncope 2.0.2) no SCIM.csv, Latency for 1037 create roles (directly syncope
> 2.0.2).png, Latency for 3000 create roles (directly syncope 2.0.2).csv,
> Latency for 3000 create roles (directly syncope 2.0.2).png, Latency for 3000
> create roles (directly syncope 2.0.4).png, MasterContent.xml
>
>
> *AnyObjetcTO's creation time (latency) grows with it's quantity.*
> Testing results are attached (Latency in milliseconds).
> Note: We've tested PostgreSQL DB directly (without Syncope) and we've got
> stable AnyObjetcTO's creation time (not increasing).
> User Syncope 2.0.4 or 2.0.4 and + PostgreSQL 9
> URI: http://localhost:9080/syncope/rest/anyObjects
> http headers:
> 1.Content-Type / application/json
> 2 Accept / application/json
> verb: POST
> body:
> {
> "plainAttrs":[
> {
>"values":[
> "test-value"
>],
>"schema":"roleEntitlements"
> }
> ],
> "type":"RoleAT",
> "realm":"/",
> "@class":"org.apache.syncope.common.lib.to.AnyObjectTO",
> "auxClasses":["RoleATClass"],
> "name":"Role_Account_1"
> }
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (SYNCOPE-1199) Syncope performance: AnyObjectTO's creation time grows with it's quantity
[
https://issues.apache.org/jira/browse/SYNCOPE-1199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16141585#comment-16141585
]
Matteo Alessandroni commented on SYNCOPE-1199:
--
You're welcome, Regards!
Matteo
> Syncope performance: AnyObjectTO's creation time grows with it's quantity
> -
>
> Key: SYNCOPE-1199
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1199
> Project: Syncope
> Issue Type: Bug
>Affects Versions: 2.0.2, 2.0.4
> Environment: Syncope 2.0.2 and 2.0.4 + PostgreSQL 9; Jmeter;
> https://github.com/Talend/platform-services/tree/master/iam/idp
>Reporter: Iurii Smyrnov
>Assignee: Matteo Alessandroni
> Attachments: CreateTestSyncope_genericResults_AnyObject.csv,
> CreateTestSyncope_graph_AnyObject.csv, CreateTestSyncope.jmx,
> CreateTestSyncope_onlyCreationAggregateReport_AnyObject.csv, Latency for 1000
> create roles (directly syncope 2.0.4) no SCIM.csv, Latency for 1000 create
> roles (directly syncope 2.0.4).png, Latency for 1037 create roles (directly
> syncope 2.0.2) no SCIM.csv, Latency for 1037 create roles (directly syncope
> 2.0.2).png, Latency for 3000 create roles (directly syncope 2.0.2).csv,
> Latency for 3000 create roles (directly syncope 2.0.2).png, Latency for 3000
> create roles (directly syncope 2.0.4).png, MasterContent.xml
>
>
> *AnyObjetcTO's creation time (latency) grows with it's quantity.*
> Testing results are attached (Latency in milliseconds).
> Note: We've tested PostgreSQL DB directly (without Syncope) and we've got
> stable AnyObjetcTO's creation time (not increasing).
> User Syncope 2.0.4 or 2.0.4 and + PostgreSQL 9
> URI: http://localhost:9080/syncope/rest/anyObjects
> http headers:
> 1.Content-Type / application/json
> 2 Accept / application/json
> verb: POST
> body:
> {
> "plainAttrs":[
> {
>"values":[
> "test-value"
>],
>"schema":"roleEntitlements"
> }
> ],
> "type":"RoleAT",
> "realm":"/",
> "@class":"org.apache.syncope.common.lib.to.AnyObjectTO",
> "auxClasses":["RoleATClass"],
> "name":"Role_Account_1"
> }
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (SYNCOPE-1199) Syncope performance: AnyObjectTO's creation time grows with it's quantity
[
https://issues.apache.org/jira/browse/SYNCOPE-1199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16141702#comment-16141702
]
Matteo Alessandroni commented on SYNCOPE-1199:
--
Hi,
I have used postgres 9.5 and Syncope 2.0.5-SNAPSHOT.
Matteo
> Syncope performance: AnyObjectTO's creation time grows with it's quantity
> -
>
> Key: SYNCOPE-1199
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1199
> Project: Syncope
> Issue Type: Bug
>Affects Versions: 2.0.2, 2.0.4
> Environment: Syncope 2.0.2 and 2.0.4 + PostgreSQL 9; Jmeter;
> https://github.com/Talend/platform-services/tree/master/iam/idp
>Reporter: Iurii Smyrnov
>Assignee: Matteo Alessandroni
> Attachments: CreateTestSyncope_genericResults_AnyObject.csv,
> CreateTestSyncope_graph_AnyObject.csv, CreateTestSyncope.jmx,
> CreateTestSyncope_onlyCreationAggregateReport_AnyObject.csv, Latency for 1000
> create roles (directly syncope 2.0.4) no SCIM.csv, Latency for 1000 create
> roles (directly syncope 2.0.4).png, Latency for 1037 create roles (directly
> syncope 2.0.2) no SCIM.csv, Latency for 1037 create roles (directly syncope
> 2.0.2).png, Latency for 3000 create roles (directly syncope 2.0.2).csv,
> Latency for 3000 create roles (directly syncope 2.0.2).png, Latency for 3000
> create roles (directly syncope 2.0.4).png, MasterContent.xml
>
>
> *AnyObjetcTO's creation time (latency) grows with it's quantity.*
> Testing results are attached (Latency in milliseconds).
> Note: We've tested PostgreSQL DB directly (without Syncope) and we've got
> stable AnyObjetcTO's creation time (not increasing).
> User Syncope 2.0.4 or 2.0.4 and + PostgreSQL 9
> URI: http://localhost:9080/syncope/rest/anyObjects
> http headers:
> 1.Content-Type / application/json
> 2 Accept / application/json
> verb: POST
> body:
> {
> "plainAttrs":[
> {
>"values":[
> "test-value"
>],
>"schema":"roleEntitlements"
> }
> ],
> "type":"RoleAT",
> "realm":"/",
> "@class":"org.apache.syncope.common.lib.to.AnyObjectTO",
> "auxClasses":["RoleATClass"],
> "name":"Role_Account_1"
> }
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (SYNCOPE-1199) Syncope performance: AnyObjectTO's creation time grows with it's quantity
[
https://issues.apache.org/jira/browse/SYNCOPE-1199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16146967#comment-16146967
]
Matteo Alessandroni commented on SYNCOPE-1199:
--
Hi Iurii,
great, glad to hear that!
Matteo
> Syncope performance: AnyObjectTO's creation time grows with it's quantity
> -
>
> Key: SYNCOPE-1199
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1199
> Project: Syncope
> Issue Type: Bug
>Affects Versions: 2.0.2, 2.0.4
> Environment: Syncope 2.0.2 and 2.0.4 + PostgreSQL 9; Jmeter;
> https://github.com/Talend/platform-services/tree/master/iam/idp
>Reporter: Iurii Smyrnov
>Assignee: Matteo Alessandroni
> Attachments: CreateTestSyncope_genericResults_AnyObject.csv,
> CreateTestSyncope_graph_AnyObject.csv, CreateTestSyncope.jmx,
> CreateTestSyncope_onlyCreationAggregateReport_AnyObject.csv, Latency for 1000
> create roles (directly syncope 2.0.4) no SCIM.csv, Latency for 1000 create
> roles (directly syncope 2.0.4).png, Latency for 1037 create roles (directly
> syncope 2.0.2) no SCIM.csv, Latency for 1037 create roles (directly syncope
> 2.0.2).png, Latency for 3000 create roles (directly syncope 2.0.2).csv,
> Latency for 3000 create roles (directly syncope 2.0.2).png, Latency for 3000
> create roles (directly syncope 2.0.4).png, MasterContent.xml
>
>
> *AnyObjetcTO's creation time (latency) grows with it's quantity.*
> Testing results are attached (Latency in milliseconds).
> Note: We've tested PostgreSQL DB directly (without Syncope) and we've got
> stable AnyObjetcTO's creation time (not increasing).
> User Syncope 2.0.4 or 2.0.4 and + PostgreSQL 9
> URI: http://localhost:9080/syncope/rest/anyObjects
> http headers:
> 1.Content-Type / application/json
> 2 Accept / application/json
> verb: POST
> body:
> {
> "plainAttrs":[
> {
>"values":[
> "test-value"
>],
>"schema":"roleEntitlements"
> }
> ],
> "type":"RoleAT",
> "realm":"/",
> "@class":"org.apache.syncope.common.lib.to.AnyObjectTO",
> "auxClasses":["RoleATClass"],
> "name":"Role_Account_1"
> }
>
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (SYNCOPE-1203) Not possible to add provision rules for "Realm" type
Matteo Alessandroni created SYNCOPE-1203: Summary: Not possible to add provision rules for "Realm" type Key: SYNCOPE-1203 URL: https://issues.apache.org/jira/browse/SYNCOPE-1203 Project: Syncope Issue Type: Bug Components: console Affects Versions: 2.0.5 Reporter: Matteo Alessandroni Fix For: 2.0.6, 2.1.0 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SYNCOPE-1233) NullPointerException in Topology after creating a connector with no displayName using pure REST call
Matteo Alessandroni created SYNCOPE-1233: Summary: NullPointerException in Topology after creating a connector with no displayName using pure REST call Key: SYNCOPE-1233 URL: https://issues.apache.org/jira/browse/SYNCOPE-1233 Project: Syncope Issue Type: Bug Components: console Affects Versions: 2.0.6, 2.0.7 Reporter: Matteo Alessandroni Assignee: Matteo Alessandroni -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (SYNCOPE-1233) NullPointerException in Topology after creating a connector with no displayName using pure REST call
[ https://issues.apache.org/jira/browse/SYNCOPE-1233?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni resolved SYNCOPE-1233. -- Resolution: Fixed > NullPointerException in Topology after creating a connector with no > displayName using pure REST call > > > Key: SYNCOPE-1233 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1233 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.0.6, 2.0.7 >Reporter: Matteo Alessandroni >Assignee: Matteo Alessandroni > Fix For: 2.0.7, 2.1.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SYNCOPE-1227) Password template not nullable after setting
[ https://issues.apache.org/jira/browse/SYNCOPE-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni updated SYNCOPE-1227: - Description: - Login into console and go to Topology - Select a resource -> pull tasks -> select a pull task -> template -> USER and create/edit a template for an USER. - Click on Password accordion and set a password JEXL for example: 'Password123' - Click on next until end is reached and then finish. - Re-open template and try to clear password by deleting previous JEXL - Closing accordion restored previous value and does not allow you to reset template password value. was: - Login into console and go to Topology - Select a resource -> pull tasks -> select a pull task -> template -> USER and create/edit a template for an USER. - click on Password accordion and set a password JEXL for example stati string 'Password123' - Click on next until end is reached and then finish. - Re-open template and try to clear password by deleting previous JEXL - Closing accordion restored previous value and does not allow you to reset template password value. > Password template not nullable after setting > > > Key: SYNCOPE-1227 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1227 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.0.6 >Reporter: Andrea Patricelli > Fix For: 2.0.7, 2.1.0 > > > - Login into console and go to Topology > - Select a resource -> pull tasks -> select a pull task -> template -> USER > and create/edit a template for an USER. > - Click on Password accordion and set a password JEXL for example: > 'Password123' > - Click on next until end is reached and then finish. > - Re-open template and try to clear password by deleting previous JEXL > - Closing accordion restored previous value and does not allow you to reset > template password value. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (SYNCOPE-1227) Password template not nullable after setting
[ https://issues.apache.org/jira/browse/SYNCOPE-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni reassigned SYNCOPE-1227: Assignee: Matteo Alessandroni > Password template not nullable after setting > > > Key: SYNCOPE-1227 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1227 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.0.6 >Reporter: Andrea Patricelli >Assignee: Matteo Alessandroni > Fix For: 2.0.7, 2.1.0 > > > - Login into console and go to Topology > - Select a resource -> pull tasks -> select a pull task -> template -> USER > and create/edit a template for an USER. > - Click on Password accordion and set a password JEXL for example: > 'Password123' > - Click on next until end is reached and then finish. > - Re-open template and try to clear password by deleting previous JEXL > - Closing accordion restored previous value and does not allow you to reset > template password value. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (SYNCOPE-1227) Password template not nullable after setting
[ https://issues.apache.org/jira/browse/SYNCOPE-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni resolved SYNCOPE-1227. -- Resolution: Fixed > Password template not nullable after setting > > > Key: SYNCOPE-1227 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1227 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.0.6 >Reporter: Andrea Patricelli >Assignee: Matteo Alessandroni > Fix For: 2.0.7, 2.1.0 > > > - Login into console and go to Topology > - Select a resource -> pull tasks -> select a pull task -> template -> USER > and create/edit a template for an USER. > - Click on Password accordion and set a password JEXL for example: > 'Password123' > - Click on next until end is reached and then finish. > - Re-open template and try to clear password by deleting previous JEXL > - Closing accordion restored previous value and does not allow you to reset > template password value. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (SYNCOPE-1231) Hidden columns in bulk action resul modal page
[ https://issues.apache.org/jira/browse/SYNCOPE-1231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni reassigned SYNCOPE-1231: Assignee: Matteo Alessandroni > Hidden columns in bulk action resul modal page > -- > > Key: SYNCOPE-1231 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1231 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.0.6 >Reporter: fabio martelli >Assignee: Matteo Alessandroni > Fix For: 2.0.7, 2.1.0 > > > Sometimes, user bulk action result modal page hides columns. > This depends on the number of configured columns to be shown. > Probably is better to fix the column to show... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (SYNCOPE-1229) Pull task execution bulk delete fails
[ https://issues.apache.org/jira/browse/SYNCOPE-1229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni reassigned SYNCOPE-1229: Assignee: Matteo Alessandroni > Pull task execution bulk delete fails > - > > Key: SYNCOPE-1229 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1229 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.0.6 >Reporter: fabio martelli >Assignee: Matteo Alessandroni > Fix For: 2.0.7, 2.1.0 > > > Bulk delete of pull task executions fails reporting FAILURE status -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (SYNCOPE-1235) Unlink Group from External Resource resets dynamic membership conditions
[ https://issues.apache.org/jira/browse/SYNCOPE-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni reassigned SYNCOPE-1235: Assignee: Matteo Alessandroni > Unlink Group from External Resource resets dynamic membership conditions > > > Key: SYNCOPE-1235 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1235 > Project: Syncope > Issue Type: Bug >Affects Versions: 2.0.6 >Reporter: Francesco Chicchiriccò >Assignee: Matteo Alessandroni > Fix For: 2.0.7, 2.1.0 > > > How to reproduce: > # create a Group with dynamic membership condition(s) and assign an External > Resource > # unlink the Group from the External Resource > Now, when reading the Group, the dynamic membership condition(s) set above > are voided. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (SYNCOPE-1229) Pull task execution bulk delete fails
[ https://issues.apache.org/jira/browse/SYNCOPE-1229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni resolved SYNCOPE-1229. -- Resolution: Fixed > Pull task execution bulk delete fails > - > > Key: SYNCOPE-1229 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1229 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.0.6 >Reporter: fabio martelli >Assignee: Matteo Alessandroni > Fix For: 2.0.7, 2.1.0 > > > Bulk delete of pull task executions fails reporting FAILURE status -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SYNCOPE-1235) Unlink Group from External Resource resets dynamic membership conditions
[ https://issues.apache.org/jira/browse/SYNCOPE-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni updated SYNCOPE-1235: - Description: How to reproduce: # create a Group with dynamic membership condition(s) and assign an External Resource # unlink or unassign the Group from the External Resource Now, when reading the Group, the dynamic membership condition(s) set above are voided. was: How to reproduce: # create a Group with dynamic membership condition(s) and assign an External Resource # unlink the Group from the External Resource Now, when reading the Group, the dynamic membership condition(s) set above are voided. > Unlink Group from External Resource resets dynamic membership conditions > > > Key: SYNCOPE-1235 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1235 > Project: Syncope > Issue Type: Bug >Affects Versions: 2.0.6 >Reporter: Francesco Chicchiriccò >Assignee: Matteo Alessandroni > Fix For: 2.0.7, 2.1.0 > > > How to reproduce: > # create a Group with dynamic membership condition(s) and assign an External > Resource > # unlink or unassign the Group from the External Resource > Now, when reading the Group, the dynamic membership condition(s) set above > are voided. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SYNCOPE-1235) Unlink or unassign Group from External Resource resets dynamic membership conditions
[ https://issues.apache.org/jira/browse/SYNCOPE-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni updated SYNCOPE-1235: - Summary: Unlink or unassign Group from External Resource resets dynamic membership conditions (was: Unlink Group from External Resource resets dynamic membership conditions) > Unlink or unassign Group from External Resource resets dynamic membership > conditions > > > Key: SYNCOPE-1235 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1235 > Project: Syncope > Issue Type: Bug >Affects Versions: 2.0.6 >Reporter: Francesco Chicchiriccò >Assignee: Matteo Alessandroni > Fix For: 2.0.7, 2.1.0 > > > How to reproduce: > # create a Group with dynamic membership condition(s) and assign an External > Resource > # unlink or unassign the Group from the External Resource > Now, when reading the Group, the dynamic membership condition(s) set above > are voided. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (SYNCOPE-1235) Unlink or unassign Group from External Resource resets dynamic membership conditions
[ https://issues.apache.org/jira/browse/SYNCOPE-1235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni resolved SYNCOPE-1235. -- Resolution: Fixed > Unlink or unassign Group from External Resource resets dynamic membership > conditions > > > Key: SYNCOPE-1235 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1235 > Project: Syncope > Issue Type: Bug >Affects Versions: 2.0.6 >Reporter: Francesco Chicchiriccò >Assignee: Matteo Alessandroni > Fix For: 2.0.7, 2.1.0 > > > How to reproduce: > # create a Group with dynamic membership condition(s) and assign an External > Resource > # unlink or unassign the Group from the External Resource > Now, when reading the Group, the dynamic membership condition(s) set above > are voided. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (SYNCOPE-1230) Bad toggle handling during task execution delete
[ https://issues.apache.org/jira/browse/SYNCOPE-1230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni reassigned SYNCOPE-1230: Assignee: Matteo Alessandroni > Bad toggle handling during task execution delete > > > Key: SYNCOPE-1230 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1230 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.0.6 >Reporter: fabio martelli >Assignee: Matteo Alessandroni > Fix For: 2.0.7, 2.1.0 > > > Steps to reproduce: > # execute a simple pull task > # wait for its execution and then inspect the execution status by licking on > 'view' > # click on one of the listed execution to open the toggle menu > # click on delete > ... execution will be deleted but the toggle about the delete execution will > be closed and reopened again. > Correct behavior: toggle has to be closed and not reopened. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (SYNCOPE-1230) Bad toggle handling during task execution delete
[ https://issues.apache.org/jira/browse/SYNCOPE-1230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni resolved SYNCOPE-1230. -- Resolution: Fixed > Bad toggle handling during task execution delete > > > Key: SYNCOPE-1230 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1230 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.0.6 >Reporter: fabio martelli >Assignee: Matteo Alessandroni > Fix For: 2.0.7, 2.1.0 > > > Steps to reproduce: > # execute a simple pull task > # wait for its execution and then inspect the execution status by licking on > 'view' > # click on one of the listed execution to open the toggle menu > # click on delete > ... execution will be deleted but the toggle about the delete execution will > be closed and reopened again. > Correct behavior: toggle has to be closed and not reopened. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (SYNCOPE-1231) Hidden columns in bulk action resul modal page
[ https://issues.apache.org/jira/browse/SYNCOPE-1231?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni resolved SYNCOPE-1231. -- Resolution: Fixed > Hidden columns in bulk action resul modal page > -- > > Key: SYNCOPE-1231 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1231 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.0.6 >Reporter: fabio martelli >Assignee: Matteo Alessandroni > Fix For: 2.0.7, 2.1.0 > > > Sometimes, user bulk action result modal page hides columns. > This depends on the number of configured columns to be shown. > Probably is better to fix the column to show... -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (SYNCOPE-1236) Pagination error for executed tasks
[ https://issues.apache.org/jira/browse/SYNCOPE-1236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni reassigned SYNCOPE-1236: Assignee: Matteo Alessandroni > 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 >Assignee: Matteo Alessandroni > 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] [Resolved] (SYNCOPE-1236) Pagination error for executed tasks
[ https://issues.apache.org/jira/browse/SYNCOPE-1236?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni resolved SYNCOPE-1236. -- Resolution: Fixed > 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 >Assignee: Matteo Alessandroni > 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] [Created] (SYNCOPE-1237) Copy element key to clipboard by clicking on key icon in table views
Matteo Alessandroni created SYNCOPE-1237: Summary: Copy element key to clipboard by clicking on key icon in table views Key: SYNCOPE-1237 URL: https://issues.apache.org/jira/browse/SYNCOPE-1237 Project: Syncope Issue Type: Improvement Components: console Reporter: Matteo Alessandroni Priority: Trivial Fix For: 2.0.7 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (SYNCOPE-1237) Copy element key to clipboard by clicking on key icon in table views
[ https://issues.apache.org/jira/browse/SYNCOPE-1237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni reassigned SYNCOPE-1237: Assignee: Matteo Alessandroni > Copy element key to clipboard by clicking on key icon in table views > - > > Key: SYNCOPE-1237 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1237 > Project: Syncope > Issue Type: Improvement > Components: console >Reporter: Matteo Alessandroni >Assignee: Matteo Alessandroni >Priority: Trivial > Fix For: 2.0.7, 2.1.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SYNCOPE-1237) Copy element key to clipboard by clicking on key icon in table views
[ https://issues.apache.org/jira/browse/SYNCOPE-1237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni updated SYNCOPE-1237: - Fix Version/s: 2.1.0 > Copy element key to clipboard by clicking on key icon in table views > - > > Key: SYNCOPE-1237 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1237 > Project: Syncope > Issue Type: Improvement > Components: console >Reporter: Matteo Alessandroni >Priority: Trivial > Fix For: 2.0.7, 2.1.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SYNCOPE-1237) Copy table row element key to clipboard by clicking on its name in toggle menu
[ https://issues.apache.org/jira/browse/SYNCOPE-1237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni updated SYNCOPE-1237: - Summary: Copy table row element key to clipboard by clicking on its name in toggle menu (was: Copy element key to clipboard by clicking on key icon in table views ) > Copy table row element key to clipboard by clicking on its name in toggle menu > -- > > Key: SYNCOPE-1237 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1237 > Project: Syncope > Issue Type: Improvement > Components: console >Reporter: Matteo Alessandroni >Assignee: Matteo Alessandroni >Priority: Trivial > Fix For: 2.0.7, 2.1.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (SYNCOPE-1226) List the attributes to be displayed show deleted attributes
[ https://issues.apache.org/jira/browse/SYNCOPE-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni reassigned SYNCOPE-1226: Assignee: Matteo Alessandroni > List the attributes to be displayed show deleted attributes > --- > > Key: SYNCOPE-1226 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1226 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.0.6 >Reporter: Filipe Silva >Assignee: Matteo Alessandroni >Priority: Trivial > Fix For: 2.0.7, 2.1.0 > > > List the attributes to be displayed show deleted/ "not affected any more" > attributes > How to test that: > * In Admin console create a plain schema > * Add that schema to a type > * In Realms view add a column with that attribute for that type (attributes > to be displayed) > * delete the schema or take it out from the type > * In Realms view call attributes to be displayed: in the selected list the > "delete"/"not affected" attribute still appears -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (SYNCOPE-1237) Copy table row element key to clipboard by clicking on its name in toggle menu
[ https://issues.apache.org/jira/browse/SYNCOPE-1237?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni resolved SYNCOPE-1237. -- Resolution: Fixed > Copy table row element key to clipboard by clicking on its name in toggle menu > -- > > Key: SYNCOPE-1237 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1237 > Project: Syncope > Issue Type: Improvement > Components: console >Reporter: Matteo Alessandroni >Assignee: Matteo Alessandroni >Priority: Trivial > Fix For: 2.0.7, 2.1.0 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (SYNCOPE-1226) List the attributes to be displayed show deleted attributes
[ https://issues.apache.org/jira/browse/SYNCOPE-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni resolved SYNCOPE-1226. -- Resolution: Fixed > List the attributes to be displayed show deleted attributes > --- > > Key: SYNCOPE-1226 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1226 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.0.6 >Reporter: Filipe Silva >Assignee: Matteo Alessandroni >Priority: Trivial > Fix For: 2.0.7, 2.1.0 > > > List the attributes to be displayed show deleted/ "not affected any more" > attributes > How to test that: > * In Admin console create a plain schema > * Add that schema to a type > * In Realms view add a column with that attribute for that type (attributes > to be displayed) > * delete the schema or take it out from the type > * In Realms view call attributes to be displayed: in the selected list the > "delete"/"not affected" attribute still appears -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (SYNCOPE-1242) Simple way to see elements full text value in Palette Panels
Matteo Alessandroni created SYNCOPE-1242: Summary: Simple way to see elements full text value in Palette Panels Key: SYNCOPE-1242 URL: https://issues.apache.org/jira/browse/SYNCOPE-1242 Project: Syncope Issue Type: Improvement Components: console Reporter: Matteo Alessandroni Assignee: Matteo Alessandroni Priority: Trivial Fix For: 2.0.7, 2.1.0 *Current behaviour, e.g.*: * Create a new Plain Schema with a very long name; * Go to Users view and click on the icon to choose what columns to see; * In "Plain Attributes" Palette Panel, specifically in "Available" column, you won't see the full name of the created Plain Schema. *Solution*: make it possible to use mouse overing each element in that column in order to show full name -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (SYNCOPE-1242) Simple way to see elements full text value in Palette Panels
[ https://issues.apache.org/jira/browse/SYNCOPE-1242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni resolved SYNCOPE-1242. -- Resolution: Fixed > Simple way to see elements full text value in Palette Panels > > > Key: SYNCOPE-1242 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1242 > Project: Syncope > Issue Type: Improvement > Components: console >Reporter: Matteo Alessandroni >Assignee: Matteo Alessandroni >Priority: Trivial > Fix For: 2.0.7, 2.1.0 > > > *Current behaviour, e.g.*: > * Create a new Plain Schema with a very long name; > * Go to Users view and click on the icon to choose what columns to see; > * In "Plain Attributes" Palette Panel, specifically in "Available" column, > you won't see the full name of the created Plain Schema. > *Solution*: > make it possible to use mouse overing each element in that column in order to > show full name -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (SYNCOPE-1240) Topology panel doesn't refresh after a connector has been created
[ https://issues.apache.org/jira/browse/SYNCOPE-1240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni reassigned SYNCOPE-1240: Assignee: Matteo Alessandroni > 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 >Assignee: Matteo Alessandroni > 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 SYNCOPE-1238 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (SYNCOPE-1240) Topology panel doesn't refresh after a connector has been created
[ https://issues.apache.org/jira/browse/SYNCOPE-1240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni closed SYNCOPE-1240. Resolution: Cannot Reproduce > 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 >Assignee: Matteo Alessandroni > > The topology panel doesn't refresh after a connector or resource has been > added. The problem is related to SYNCOPE-1238 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SYNCOPE-1240) Topology panel doesn't refresh after a connector has been created
[ https://issues.apache.org/jira/browse/SYNCOPE-1240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni updated SYNCOPE-1240: - Fix Version/s: (was: 2.0.7) (was: 2.1.0) > 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 >Assignee: Matteo Alessandroni > > The topology panel doesn't refresh after a connector or resource has been > added. The problem is related to SYNCOPE-1238 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (SYNCOPE-1246) Group membership search stucks with several thousands of groups
[ https://issues.apache.org/jira/browse/SYNCOPE-1246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni reassigned SYNCOPE-1246: Assignee: Matteo Alessandroni > Group membership search stucks with several thousands of groups > --- > > Key: SYNCOPE-1246 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1246 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.0.6 > Environment: Syncope installation with several thousdands of groups. > Real test case counts ~15k groups and 160k users >Reporter: Andrea Patricelli >Assignee: Matteo Alessandroni > Fix For: 2.0.7, 2.1.0 > > > Pre-requisite: on Syncope there are several thousands of groups and users > assigned to them. > 1. Login on Syncope admin console > 2. Go to USER tab and click on User Search > 3. from the leftmost select choose GROUP_MEMBERSHIP > You'll notice that console stucks and no other links work, due to some > internal timeout or long process that retrieves all group names to fill the > right field of the search. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (SYNCOPE-1245) Timeout when retrieving members of a group
[ https://issues.apache.org/jira/browse/SYNCOPE-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni updated SYNCOPE-1245: - Summary: Timeout when retrieving members of a group (was: Timeout when retrieving mebers of a group ) > Timeout when retrieving members of a group > --- > > Key: SYNCOPE-1245 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1245 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.0.6 > Environment: Syncope installation with several thousdands of groups. > Real test case counts ~15k groups and 160k users >Reporter: Andrea Patricelli > Fix For: 2.0.7, 2.1.0 > > > Pre--requisite: on Syncope there are several thousands of groups and users > assigned to them. > 1. Login on Syncope admin console > 2. Go to GROUP page and select a group with assigned several thousands of > users, then click on members -> USER. > You'll see, with a certain level of probability, a stacktrace by wicket > showing timeout exception. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (SYNCOPE-1246) Group membership search stucks with several thousands of groups
[ https://issues.apache.org/jira/browse/SYNCOPE-1246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni resolved SYNCOPE-1246. -- Resolution: Fixed > Group membership search stucks with several thousands of groups > --- > > Key: SYNCOPE-1246 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1246 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.0.6 > Environment: Syncope installation with several thousdands of groups. > Real test case counts ~15k groups and 160k users >Reporter: Andrea Patricelli >Assignee: Matteo Alessandroni > Fix For: 2.0.7, 2.1.0 > > > Pre-requisite: on Syncope there are several thousands of groups and users > assigned to them. > 1. Login on Syncope admin console > 2. Go to USER tab and click on User Search > 3. from the leftmost select choose GROUP_MEMBERSHIP > You'll notice that console stucks and no other links work, due to some > internal timeout or long process that retrieves all group names to fill the > right field of the search. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (SYNCOPE-1245) Timeout when retrieving members of a group
[ https://issues.apache.org/jira/browse/SYNCOPE-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni resolved SYNCOPE-1245. -- Resolution: Won't Fix Fix Version/s: (was: 2.0.7) (was: 2.1.0) > Timeout when retrieving members of a group > --- > > Key: SYNCOPE-1245 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1245 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.0.6 > Environment: Syncope installation with several thousdands of groups. > Real test case counts ~15k groups and 160k users >Reporter: Andrea Patricelli > > Pre--requisite: on Syncope there are several thousands of groups and users > assigned to them. > 1. Login on Syncope admin console > 2. Go to GROUP page and select a group with assigned several thousands of > users, then click on members -> USER. > You'll see, with a certain level of probability, a stacktrace by wicket > showing timeout exception. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Reopened] (SYNCOPE-1245) Timeout when retrieving members of a group
[ https://issues.apache.org/jira/browse/SYNCOPE-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni reopened SYNCOPE-1245: -- > Timeout when retrieving members of a group > --- > > Key: SYNCOPE-1245 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1245 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.0.6 > Environment: Syncope installation with several thousdands of groups. > Real test case counts ~15k groups and 160k users >Reporter: Andrea Patricelli > > Pre--requisite: on Syncope there are several thousands of groups and users > assigned to them. > 1. Login on Syncope admin console > 2. Go to GROUP page and select a group with assigned several thousands of > users, then click on members -> USER. > You'll see, with a certain level of probability, a stacktrace by wicket > showing timeout exception. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (SYNCOPE-1245) Timeout when retrieving members of a group
[ https://issues.apache.org/jira/browse/SYNCOPE-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni resolved SYNCOPE-1245. -- Resolution: Cannot Reproduce > Timeout when retrieving members of a group > --- > > Key: SYNCOPE-1245 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1245 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.0.6 > Environment: Syncope installation with several thousdands of groups. > Real test case counts ~15k groups and 160k users >Reporter: Andrea Patricelli > > Pre--requisite: on Syncope there are several thousands of groups and users > assigned to them. > 1. Login on Syncope admin console > 2. Go to GROUP page and select a group with assigned several thousands of > users, then click on members -> USER. > You'll see, with a certain level of probability, a stacktrace by wicket > showing timeout exception. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (SYNCOPE-1245) Timeout when retrieving members of a group
[ https://issues.apache.org/jira/browse/SYNCOPE-1245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni closed SYNCOPE-1245. > Timeout when retrieving members of a group > --- > > Key: SYNCOPE-1245 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1245 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.0.6 > Environment: Syncope installation with several thousdands of groups. > Real test case counts ~15k groups and 160k users >Reporter: Andrea Patricelli > > Pre--requisite: on Syncope there are several thousands of groups and users > assigned to them. > 1. Login on Syncope admin console > 2. Go to GROUP page and select a group with assigned several thousands of > users, then click on members -> USER. > You'll see, with a certain level of probability, a stacktrace by wicket > showing timeout exception. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (SYNCOPE-1247) Group search and auto-completion does not work with several thousands of groups
[ https://issues.apache.org/jira/browse/SYNCOPE-1247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni reassigned SYNCOPE-1247: Assignee: Matteo Alessandroni > Group search and auto-completion does not work with several thousands of > groups > --- > > Key: SYNCOPE-1247 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1247 > Project: Syncope > Issue Type: Bug > Components: enduser >Affects Versions: 2.0.6 > Environment: Syncope installation with several thousdands of groups. > Real test case counts ~15k groups and 160k users >Reporter: Andrea Patricelli >Assignee: Matteo Alessandroni > Fix For: 2.0.7, 2.1.0 > > > Pre-requisite: on Syncope there are several thousands of groups and users > assigned to them. > 1. Login on Syncope enduser or simply click on Self registration > 2. Go to groups tab and try to search a group by start typing the name. > You'll find that auto-complete does not work and that group is not retrieved. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (SYNCOPE-1247) Group search and auto-completion does not work with several thousands of groups
[ https://issues.apache.org/jira/browse/SYNCOPE-1247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni resolved SYNCOPE-1247. -- Resolution: Fixed > Group search and auto-completion does not work with several thousands of > groups > --- > > Key: SYNCOPE-1247 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1247 > Project: Syncope > Issue Type: Bug > Components: enduser >Affects Versions: 2.0.6 > Environment: Syncope installation with several thousdands of groups. > Real test case counts ~15k groups and 160k users >Reporter: Andrea Patricelli >Assignee: Matteo Alessandroni > Fix For: 2.0.7, 2.1.0 > > > Pre-requisite: on Syncope there are several thousands of groups and users > assigned to them. > 1. Login on Syncope enduser or simply click on Self registration > 2. Go to groups tab and try to search a group by start typing the name. > You'll find that auto-complete does not work and that group is not retrieved. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Assigned] (SYNCOPE-1268) Missing previews for some binary attributes
[ https://issues.apache.org/jira/browse/SYNCOPE-1268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni reassigned SYNCOPE-1268: Assignee: Matteo Alessandroni > Missing previews for some binary attributes > --- > > Key: SYNCOPE-1268 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1268 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.0.7 >Reporter: fabio martelli >Assignee: Matteo Alessandroni >Priority: Major > Fix For: 2.0.8, 2.1.0 > > > Missing previews for: > * images (gif, jpg, png) > * wrong preview for large json (more than 5M) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (SYNCOPE-1268) Missing previews for some binary attributes
[ https://issues.apache.org/jira/browse/SYNCOPE-1268?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni closed SYNCOPE-1268. Resolution: Cannot Reproduce Fix Version/s: (was: 2.0.8) (was: 2.1.0) > Missing previews for some binary attributes > --- > > Key: SYNCOPE-1268 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1268 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 2.0.7 >Reporter: fabio martelli >Assignee: Matteo Alessandroni >Priority: Major > > Missing previews for: > * images (gif, jpg, png) > * wrong preview for large json (more than 5M) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SYNCOPE-1267) Provide check of mimetypes before generate a binary attribute preview
[ https://issues.apache.org/jira/browse/SYNCOPE-1267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni reassigned SYNCOPE-1267: Assignee: Matteo Alessandroni > Provide check of mimetypes before generate a binary attribute preview > - > > Key: SYNCOPE-1267 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1267 > Project: Syncope > Issue Type: Improvement > Components: console >Affects Versions: 2.0.7 >Reporter: fabio martelli >Assignee: Matteo Alessandroni >Priority: Major > Fix For: 2.0.8, 2.1.0 > > > Provide check of mimetypes before generate a binary attribute preview. > If the mimetype does not correspond to the expected one, avoid to compute the > preview and notify the error. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SYNCOPE-1267) Provide check of mimetypes before generate a binary attribute preview
[ https://issues.apache.org/jira/browse/SYNCOPE-1267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni resolved SYNCOPE-1267. -- Resolution: Fixed > Provide check of mimetypes before generate a binary attribute preview > - > > Key: SYNCOPE-1267 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1267 > Project: Syncope > Issue Type: Improvement > Components: console >Affects Versions: 2.0.7 >Reporter: fabio martelli >Assignee: Matteo Alessandroni >Priority: Major > Fix For: 2.0.8, 2.1.0 > > > Provide check of mimetypes before generate a binary attribute preview. > If the mimetype does not correspond to the expected one, avoid to compute the > preview and notify the error. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SYNCOPE-1258) Upgrade to Font Awesome 5
[ https://issues.apache.org/jira/browse/SYNCOPE-1258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni reassigned SYNCOPE-1258: Assignee: Matteo Alessandroni > Upgrade to Font Awesome 5 > - > > Key: SYNCOPE-1258 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1258 > Project: Syncope > Issue Type: Task > Components: console, enduser >Reporter: Francesco Chicchiriccò >Assignee: Matteo Alessandroni >Priority: Major > Fix For: 2.0.8, 2.1.0 > > > Currently using 4.7.0, now 5.0.2 is available via webjars. > Upgrade Guide: https://fontawesome.com/how-to-use/upgrading-from-4 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SYNCOPE-1258) Upgrade to Font Awesome 5
[
https://issues.apache.org/jira/browse/SYNCOPE-1258?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16381869#comment-16381869
]
Matteo Alessandroni commented on SYNCOPE-1258:
--
Can't fully complete the task until new Font Awesome 5 support will be added to
{{wicket-bootstrap}} too.
See [this issue|https://github.com/l0rdn1kk0n/wicket-bootstrap/issues/707] for
reference.
> Upgrade to Font Awesome 5
> -
>
> Key: SYNCOPE-1258
> URL: https://issues.apache.org/jira/browse/SYNCOPE-1258
> Project: Syncope
> Issue Type: Task
> Components: console, enduser
>Reporter: Francesco Chicchiriccò
>Assignee: Matteo Alessandroni
>Priority: Major
> Fix For: 2.1.0
>
>
> Currently using 4.7.0, now 5.0.2 is available via webjars.
> Upgrade Guide: https://fontawesome.com/how-to-use/upgrading-from-4
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (SYNCOPE-1258) Upgrade to Font Awesome 5
[ https://issues.apache.org/jira/browse/SYNCOPE-1258?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni updated SYNCOPE-1258: - Fix Version/s: (was: 2.0.8) > Upgrade to Font Awesome 5 > - > > Key: SYNCOPE-1258 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1258 > Project: Syncope > Issue Type: Task > Components: console, enduser >Reporter: Francesco Chicchiriccò >Assignee: Matteo Alessandroni >Priority: Major > Fix For: 2.1.0 > > > Currently using 4.7.0, now 5.0.2 is available via webjars. > Upgrade Guide: https://fontawesome.com/how-to-use/upgrading-from-4 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SYNCOPE-1225) Search funcionality in Schemas
[ https://issues.apache.org/jira/browse/SYNCOPE-1225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni reassigned SYNCOPE-1225: Assignee: Matteo Alessandroni > Search funcionality in Schemas > -- > > Key: SYNCOPE-1225 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1225 > Project: Syncope > Issue Type: Improvement > Components: console >Affects Versions: 2.0.6 >Reporter: Filipe Silva >Assignee: Matteo Alessandroni >Priority: Trivial > Fix For: 2.0.8, 2.1.0 > > > I think it would be very useful in environments with several issues to be > able to search schemas using it's attributes (key, type,etc) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SYNCOPE-1225) Search funcionality in Schemas
[ https://issues.apache.org/jira/browse/SYNCOPE-1225?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni resolved SYNCOPE-1225. -- Resolution: Fixed > Search funcionality in Schemas > -- > > Key: SYNCOPE-1225 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1225 > Project: Syncope > Issue Type: Improvement > Components: console >Affects Versions: 2.0.6 >Reporter: Filipe Silva >Assignee: Matteo Alessandroni >Priority: Trivial > Fix For: 2.0.8, 2.1.0 > > > I think it would be very useful in environments with several issues to be > able to search schemas using it's attributes (key, type,etc) -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (SYNCOPE-1283) Support Azure AD
Matteo Alessandroni created SYNCOPE-1283: Summary: Support Azure AD Key: SYNCOPE-1283 URL: https://issues.apache.org/jira/browse/SYNCOPE-1283 Project: Syncope Issue Type: New Feature Reporter: Matteo Alessandroni Assignee: Matteo Alessandroni Fix For: 2.0.9, 2.1.0 Since new [Azure connector|https://connid.atlassian.net/wiki/spaces/BASE/pages/308674561/Azure] is now ready on [ConnId|http://connid.tirasa.net/] project, it would be good to add it to Syncope project. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Resolved] (SYNCOPE-1283) Support Azure AD
[ https://issues.apache.org/jira/browse/SYNCOPE-1283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni resolved SYNCOPE-1283. -- Resolution: Fixed > Support Azure AD > > > Key: SYNCOPE-1283 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1283 > Project: Syncope > Issue Type: New Feature >Reporter: Matteo Alessandroni >Assignee: Matteo Alessandroni >Priority: Minor > Fix For: 2.0.9, 2.1.0 > > > Since new [Azure > connector|https://connid.atlassian.net/wiki/spaces/BASE/pages/308674561/Azure] > is now ready on [ConnId|http://connid.tirasa.net/] project, it would be good > to add it to Syncope project. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SYNCOPE-1148) SAML-initiated self-registration
[ https://issues.apache.org/jira/browse/SYNCOPE-1148?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matteo Alessandroni reassigned SYNCOPE-1148: Assignee: Matteo Alessandroni > SAML-initiated self-registration > > > Key: SYNCOPE-1148 > URL: https://issues.apache.org/jira/browse/SYNCOPE-1148 > Project: Syncope > Issue Type: Improvement > Components: enduser, extensions >Reporter: Francesco Chicchiriccò >Assignee: Matteo Alessandroni >Priority: Major > Fix For: 2.0.9, 2.1.0 > > > The scenario to cover is when an unmatched user presents a valid SAML 2.0 > Authentication assertion to the Enduser UI. > Currently, an error is reported. > A different behavior could be configured, instead, to start the > self-registration process, with some values pre-populated from the > Authentication Assertion, according to the mapping defined for the SAML 2.0 > IdP. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
