[jira] [Resolved] (SYNCOPE-927) User creation randomly fails if capctha check has been disabled
[ https://issues.apache.org/jira/browse/SYNCOPE-927?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giacomo Lamonaco resolved SYNCOPE-927. -- Resolution: Fixed > User creation randomly fails if capctha check has been disabled > --- > > Key: SYNCOPE-927 > URL: https://issues.apache.org/jira/browse/SYNCOPE-927 > Project: Syncope > Issue Type: Bug > Components: enduser >Affects Versions: 2.0.0-M4 >Reporter: Giacomo Lamonaco >Assignee: Giacomo Lamonaco > Fix For: 2.0.0-M5, 2.0.0 > > > First of all disable captcha check in the enduser properties file. Rebuild > enduser reference and run it. Open enduser login page and try to register a > new user: it will refuse. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SYNCOPE-927) User creation randomly fails if capctha check has been disabled
Giacomo Lamonaco created SYNCOPE-927: Summary: User creation randomly fails if capctha check has been disabled Key: SYNCOPE-927 URL: https://issues.apache.org/jira/browse/SYNCOPE-927 Project: Syncope Issue Type: Bug Components: enduser Affects Versions: 2.0.0-M4 Reporter: Giacomo Lamonaco Assignee: Giacomo Lamonaco Fix For: 2.0.0-M5, 2.0.0 First of all disable captcha check in the enduser properties file. Rebuild enduser reference and run it. Open enduser login page and try to register a new user: it will refuse. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (SYNCOPE-853) Add AngularJS tests for enduser
[
https://issues.apache.org/jira/browse/SYNCOPE-853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Giacomo Lamonaco reassigned SYNCOPE-853:
Assignee: Giacomo Lamonaco
> Add AngularJS tests for enduser
> ---
>
> Key: SYNCOPE-853
> URL: https://issues.apache.org/jira/browse/SYNCOPE-853
> Project: Syncope
> Issue Type: Improvement
> Components: enduser
>Reporter: Francesco Chicchiriccò
>Assignee: Giacomo Lamonaco
> Fix For: 2.0.0
>
>
> Include tests for AngularJS frontend and possibly integrate them with maven
> build lifecycle in the {{fit/core-reference}} module, as already done for CLI
> and console.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Reopened] (SYNCOPE-913) Add and remove buttons in multivalue fields are not aligned
[ https://issues.apache.org/jira/browse/SYNCOPE-913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giacomo Lamonaco reopened SYNCOPE-913: -- Virtual attributes can be multivalue as well > Add and remove buttons in multivalue fields are not aligned > --- > > Key: SYNCOPE-913 > URL: https://issues.apache.org/jira/browse/SYNCOPE-913 > Project: Syncope > Issue Type: Improvement > Components: enduser >Affects Versions: 2.0.0-M4 >Reporter: Giacomo Lamonaco >Assignee: Giacomo Lamonaco >Priority: Minor > Fix For: 2.0.0 > > > When creating/editing an user, multi-value inputs are not aligned with add > and remove button: they should appear on the same row -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SYNCOPE-913) Add and remove buttons in multivalue fields are not aligned
[ https://issues.apache.org/jira/browse/SYNCOPE-913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giacomo Lamonaco resolved SYNCOPE-913. -- Resolution: Fixed > Add and remove buttons in multivalue fields are not aligned > --- > > Key: SYNCOPE-913 > URL: https://issues.apache.org/jira/browse/SYNCOPE-913 > Project: Syncope > Issue Type: Improvement > Components: enduser >Affects Versions: 2.0.0-M4 >Reporter: Giacomo Lamonaco >Assignee: Giacomo Lamonaco >Priority: Minor > Fix For: 2.0.0 > > > When creating/editing an user, multi-value inputs are not aligned with add > and remove button: they should appear on the same row -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (SYNCOPE-913) Add and remove buttons in multivalue fields are not aligned
[ https://issues.apache.org/jira/browse/SYNCOPE-913?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giacomo Lamonaco reassigned SYNCOPE-913: Assignee: Giacomo Lamonaco > Add and remove buttons in multivalue fields are not aligned > --- > > Key: SYNCOPE-913 > URL: https://issues.apache.org/jira/browse/SYNCOPE-913 > Project: Syncope > Issue Type: Improvement > Components: enduser >Affects Versions: 2.0.0-M4 >Reporter: Giacomo Lamonaco >Assignee: Giacomo Lamonaco >Priority: Minor > Fix For: 2.0.0 > > > When creating/editing an user, multi-value inputs are not aligned with add > and remove button: they should appear on the same row -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SYNCOPE-912) Registered users receive an error message after saving their own profile
[ https://issues.apache.org/jira/browse/SYNCOPE-912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giacomo Lamonaco resolved SYNCOPE-912. -- Resolution: Fixed > Registered users receive an error message after saving their own profile > > > Key: SYNCOPE-912 > URL: https://issues.apache.org/jira/browse/SYNCOPE-912 > Project: Syncope > Issue Type: Bug > Components: enduser >Affects Versions: 2.0.0-M4 >Reporter: Giacomo Lamonaco >Assignee: Giacomo Lamonaco > Fix For: 2.0.0 > > > After submitting a new user profile, enduser tries to read again that profile > - of course using user credentials. If workflow requires an approval process, > users are not authorized to access to their profile. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (SYNCOPE-912) Registered users receive an error message after saving their own profile
[ https://issues.apache.org/jira/browse/SYNCOPE-912?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giacomo Lamonaco reassigned SYNCOPE-912: Assignee: Giacomo Lamonaco > Registered users receive an error message after saving their own profile > > > Key: SYNCOPE-912 > URL: https://issues.apache.org/jira/browse/SYNCOPE-912 > Project: Syncope > Issue Type: Bug > Components: enduser >Affects Versions: 2.0.0-M4 >Reporter: Giacomo Lamonaco >Assignee: Giacomo Lamonaco > Fix For: 2.0.0 > > > After submitting a new user profile, enduser tries to read again that profile > - of course using user credentials. If workflow requires an approval process, > users are not authorized to access to their profile. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SYNCOPE-911) Enduser should allow empty values on non required select fields
[ https://issues.apache.org/jira/browse/SYNCOPE-911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giacomo Lamonaco resolved SYNCOPE-911. -- Resolution: Fixed > Enduser should allow empty values on non required select fields > --- > > Key: SYNCOPE-911 > URL: https://issues.apache.org/jira/browse/SYNCOPE-911 > Project: Syncope > Issue Type: Bug > Components: enduser >Affects Versions: 2.0.0-M4 >Reporter: Giacomo Lamonaco >Assignee: Giacomo Lamonaco > Fix For: 2.0.0 > > > Login to syncope enduser as a registered user, then open plain schemas tab. > In case of select fields, if user hasn't already chose a value, the first one > available is automatically picked up. At the end, if user update its own > profile, the value of that attribute will be updated to the selected value. > If that attribute is not required, user should be able to select an empty > value as option. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (SYNCOPE-911) Enduser should allow empty values on non required select fields
[ https://issues.apache.org/jira/browse/SYNCOPE-911?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giacomo Lamonaco reassigned SYNCOPE-911: Assignee: Giacomo Lamonaco > Enduser should allow empty values on non required select fields > --- > > Key: SYNCOPE-911 > URL: https://issues.apache.org/jira/browse/SYNCOPE-911 > Project: Syncope > Issue Type: Bug > Components: enduser >Affects Versions: 2.0.0-M4 >Reporter: Giacomo Lamonaco >Assignee: Giacomo Lamonaco > Fix For: 2.0.0 > > > Login to syncope enduser as a registered user, then open plain schemas tab. > In case of select fields, if user hasn't already chose a value, the first one > available is automatically picked up. At the end, if user update its own > profile, the value of that attribute will be updated to the selected value. > If that attribute is not required, user should be able to select an empty > value as option. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SYNCOPE-914) Spinner should be always in front of any other element
Giacomo Lamonaco created SYNCOPE-914: Summary: Spinner should be always in front of any other element Key: SYNCOPE-914 URL: https://issues.apache.org/jira/browse/SYNCOPE-914 Project: Syncope Issue Type: Improvement Components: enduser Affects Versions: 2.0.0-M4 Reporter: Giacomo Lamonaco Priority: Minor Fix For: 2.0.0 Sometimes spinner is not the element on top of the content: in example, input fields with focus can hide spinner. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SYNCOPE-912) Registered users receive an error message after saving their own profile
Giacomo Lamonaco created SYNCOPE-912: Summary: Registered users receive an error message after saving their own profile Key: SYNCOPE-912 URL: https://issues.apache.org/jira/browse/SYNCOPE-912 Project: Syncope Issue Type: Bug Components: enduser Affects Versions: 2.0.0-M4 Reporter: Giacomo Lamonaco Fix For: 2.0.0 After submitting a new user profile, enduser tries to read again that profile - of course using user credentials. If workflow requires an approval process, users are not authorized to access to their profile. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SYNCOPE-911) Enduser should allow empty values on non required select fields
Giacomo Lamonaco created SYNCOPE-911: Summary: Enduser should allow empty values on non required select fields Key: SYNCOPE-911 URL: https://issues.apache.org/jira/browse/SYNCOPE-911 Project: Syncope Issue Type: Bug Components: enduser Affects Versions: 2.0.0-M4 Reporter: Giacomo Lamonaco Fix For: 2.0.0 Login to syncope enduser as a registered user, then open plain schemas tab. In case of select fields, if user hasn't already chose a value, the first one available is automatically picked up. At the end, if user update its own profile, the value of that attribute will be updated to the selected value. If that attribute is not required, user should be able to select an empty value as option. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SYNCOPE-780) On logout session is not completely cleared out
[ https://issues.apache.org/jira/browse/SYNCOPE-780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giacomo Lamonaco resolved SYNCOPE-780. -- Resolution: Fixed > On logout session is not completely cleared out > --- > > Key: SYNCOPE-780 > URL: https://issues.apache.org/jira/browse/SYNCOPE-780 > Project: Syncope > Issue Type: Bug > Components: enduser >Affects Versions: 2.0.0-M2 > Environment: Google Chrome on Linux >Reporter: Francesco Chicchiriccò >Assignee: Giacomo Lamonaco > Fix For: 2.0.0-M2 > > > How to reproduce (with test data): > # log in as bellini > # logout > # log in as puccini > You still see bellini's data. > The only way to see puccini's data is to close the browser's window (simply > clearing out cookies does not seem to have effect) and login again as puccini. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SYNCOPE-780) On logout session is not completely cleared out
[ https://issues.apache.org/jira/browse/SYNCOPE-780?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15204011#comment-15204011 ] Giacomo Lamonaco commented on SYNCOPE-780: -- It seems to be a browser cache issue: in chrome, if caching is disabled, session data are completely destroyed. We need to specify some options to avoid caching in angular service call. > On logout session is not completely cleared out > --- > > Key: SYNCOPE-780 > URL: https://issues.apache.org/jira/browse/SYNCOPE-780 > Project: Syncope > Issue Type: Bug > Components: enduser >Affects Versions: 2.0.0-M2 >Reporter: Francesco Chicchiriccò >Assignee: Giacomo Lamonaco > Fix For: 2.0.0 > > > How to reproduce (with test data): > # log in as bellini > # logout > # log in as puccini > You still see bellini's data. > The only way to see puccini's data is to close the browser's window (simply > clearing out cookies does not seem to have effect) and login again as puccini. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (SYNCOPE-780) On logout session is not completely cleared out
[ https://issues.apache.org/jira/browse/SYNCOPE-780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giacomo Lamonaco reassigned SYNCOPE-780: Assignee: Giacomo Lamonaco > On logout session is not completely cleared out > --- > > Key: SYNCOPE-780 > URL: https://issues.apache.org/jira/browse/SYNCOPE-780 > Project: Syncope > Issue Type: Bug > Components: enduser >Affects Versions: 2.0.0-M2 >Reporter: Francesco Chicchiriccò >Assignee: Giacomo Lamonaco > Fix For: 2.0.0 > > > How to reproduce (with test data): > # log in as bellini > # logout > # log in as puccini > You still see bellini's data. > The only way to see puccini's data is to close the browser's window (simply > clearing out cookies does not seem to have effect) and login again as puccini. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (SYNCOPE-721) Enduser i18n
[ https://issues.apache.org/jira/browse/SYNCOPE-721?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giacomo Lamonaco reassigned SYNCOPE-721: Assignee: Giacomo Lamonaco > Enduser i18n > > > Key: SYNCOPE-721 > URL: https://issues.apache.org/jira/browse/SYNCOPE-721 > Project: Syncope > Issue Type: Sub-task > Components: enduser >Affects Versions: 2.0.0-M1 >Reporter: Andrea Patricelli >Assignee: Giacomo Lamonaco > Fix For: 2.0.0 > > > Add i18n to angular application. It may be useful to export and load once a > JSON file with translated labels and get translations from it at runtime. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SYNCOPE-719) UI enhancements
[ https://issues.apache.org/jira/browse/SYNCOPE-719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giacomo Lamonaco updated SYNCOPE-719: - Description: Enhancements to implement: - --Align login form to admin console's-- - --Align derived and virtual attributes management to admin console's-- - Add form frontend validation through AngularJS built-in form services. - --Secure authentication process: at the moment username and password are passed "clearly" to wicket resource in the payload of the POST. to achieve this configure HTTPS connection--. - Realms management (if needed): Add http resource to get available realms and possibiltity to select realm in user form. - Uploaded file preview (trivial, can even be ignored) - --Add loading spinner to application-- - --Add Resource management to create/edit user wizard (if needed).-- - --Add Group management to create/edit user wizard (if needed).-- - AngularJS unit testing: implement unit tests for angular frontend and possibly integrate them with maven build lifecycle. - Improve date management edit/create form: add timepicker when needed. - --Improve error and exception management: especially messages sent by resource to angular frontend.-- - --Add password stregth validator to user creation form.-- - --Add CAPTCHA field in self registration form.-- - Add javadoc and if possible javascript doc - --Add protection mechanisms against XSRF/CSRF attacks.-- was: Enhancements to implement: - --Align login form to admin console's-- - --Align derived and virtual attributes management to admin console's-- - Add form frontend validation through AngularJS built-in form services. - --Secure authentication process: at the moment username and password are passed "clearly" to wicket resource in the payload of the POST. to achieve this configure HTTPS connection--. - Realms management (if needed): Add http resource to get available realms and possibiltity to select realm in user form. - Uploaded file preview (trivial, can even be ignored) - --Add loading spinner to application-- - --Add Resource management to create/edit user wizard (if needed).-- - --Add Group management to create/edit user wizard (if needed).-- - AngularJS unit testing: implement unit tests for angular frontend and possibly integrate them with maven build lifecycle. - Improve date management edit/create form: add timepicker when needed. - --Improve error and exception management: especially messages sent by resource to angular frontend.-- - Add password stregth validator to user creation form. - --Add CAPTCHA field in self registration form.-- - Add javadoc and if possible javascript doc - --Add protection mechanisms against XSRF/CSRF attacks.-- > UI enhancements > --- > > Key: SYNCOPE-719 > URL: https://issues.apache.org/jira/browse/SYNCOPE-719 > Project: Syncope > Issue Type: Sub-task > Components: enduser >Affects Versions: 2.0.0-M1 >Reporter: Andrea Patricelli >Assignee: Andrea Patricelli > Fix For: 2.0.0 > > > Enhancements to implement: > - --Align login form to admin console's-- > - --Align derived and virtual attributes management to admin console's-- > - Add form frontend validation through AngularJS built-in form services. > - --Secure authentication process: at the moment username and password are > passed "clearly" to wicket resource in the payload of the POST. to achieve > this configure HTTPS connection--. > - Realms management (if needed): Add http resource to get available realms > and possibiltity to select realm in user form. > - Uploaded file preview (trivial, can even be ignored) > - --Add loading spinner to application-- > - --Add Resource management to create/edit user wizard (if needed).-- > - --Add Group management to create/edit user wizard (if needed).-- > - AngularJS unit testing: implement unit tests for angular frontend and > possibly integrate them with maven build lifecycle. > - Improve date management edit/create form: add timepicker when needed. > - --Improve error and exception management: especially messages sent by > resource to angular frontend.-- > - --Add password stregth validator to user creation form.-- > - --Add CAPTCHA field in self registration form.-- > - Add javadoc and if possible javascript doc > - --Add protection mechanisms against XSRF/CSRF attacks.-- -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SYNCOPE-719) UI enhancements
[ https://issues.apache.org/jira/browse/SYNCOPE-719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giacomo Lamonaco updated SYNCOPE-719: - Description: Enhancements to implement: - --Align login form to admin console's-- - --Align derived and virtual attributes management to admin console's-- - Add form frontend validation through AngularJS built-in form services. - --Secure authentication process: at the moment username and password are passed "clearly" to wicket resource in the payload of the POST. to achieve this configure HTTPS connection--. - Realms management (if needed): Add http resource to get available realms and possibiltity to select realm in user form. - Uploaded file preview (trivial, can even be ignored) - --Add loading spinner to application-- - --Add Resource management to create/edit user wizard (if needed).-- - --Add Group management to create/edit user wizard (if needed).-- - AngularJS unit testing: implement unit tests for angular frontend and possibly integrate them with maven build lifecycle. - Improve date management edit/create form: add timepicker when needed. - --Improve error and exception management: especially messages sent by resource to angular frontend.-- - Add password stregth validator to user creation form. - --Add CAPTCHA field in self registration form.-- - Add javadoc and if possible javascript doc - --Add protection mechanisms against XSRF/CSRF attacks.-- was: Enhancements to implement: - --Align login form to admin console's-- - --Align derived and virtual attributes management to admin console's-- - Add form frontend validation through AngularJS built-in form services. - --Secure authentication process: at the moment username and password are passed "clearly" to wicket resource in the payload of the POST. to achieve this configure HTTPS connection--. - Realms management (if needed): Add http resource to get available realms and possibiltity to select realm in user form. - Uploaded file preview (trivial, can even be ignored) - --Add loading spinner to application: http://mvnrepository.com/artifact/org.webjars.bower/angular-spinner-- - --Add Resource management to create/edit user wizard (if needed).-- - --Add Group management to create/edit user wizard (if needed).-- - AngularJS unit testing: implement unit tests for angular frontend and possibly integrate them with maven build lifecycle. - Improve date management edit/create form: add timepicker when needed. - --Improve error and exception management: especially messages sent by resource to angular frontend.-- - Add password stregth validator to user creation form. - --Add CAPTCHA field in self registration form.-- - Add javadoc and if possible javascript doc - --Add protection mechanisms against XSRF/CSRF attacks.-- > UI enhancements > --- > > Key: SYNCOPE-719 > URL: https://issues.apache.org/jira/browse/SYNCOPE-719 > Project: Syncope > Issue Type: Sub-task > Components: enduser >Affects Versions: 2.0.0-M1 >Reporter: Andrea Patricelli >Assignee: Andrea Patricelli > Fix For: 2.0.0 > > > Enhancements to implement: > - --Align login form to admin console's-- > - --Align derived and virtual attributes management to admin console's-- > - Add form frontend validation through AngularJS built-in form services. > - --Secure authentication process: at the moment username and password are > passed "clearly" to wicket resource in the payload of the POST. to achieve > this configure HTTPS connection--. > - Realms management (if needed): Add http resource to get available realms > and possibiltity to select realm in user form. > - Uploaded file preview (trivial, can even be ignored) > - --Add loading spinner to application-- > - --Add Resource management to create/edit user wizard (if needed).-- > - --Add Group management to create/edit user wizard (if needed).-- > - AngularJS unit testing: implement unit tests for angular frontend and > possibly integrate them with maven build lifecycle. > - Improve date management edit/create form: add timepicker when needed. > - --Improve error and exception management: especially messages sent by > resource to angular frontend.-- > - Add password stregth validator to user creation form. > - --Add CAPTCHA field in self registration form.-- > - Add javadoc and if possible javascript doc > - --Add protection mechanisms against XSRF/CSRF attacks.-- -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SYNCOPE-719) UI enhancements
[ https://issues.apache.org/jira/browse/SYNCOPE-719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giacomo Lamonaco updated SYNCOPE-719: - Description: Enhancements to implement: - --Align login form to admin console's-- - --Align derived and virtual attributes management to admin console's-- - Add form frontend validation through AngularJS built-in form services. - --Secure authentication process: at the moment username and password are passed "clearly" to wicket resource in the payload of the POST. to achieve this configure HTTPS connection--. - Realms management (if needed): Add http resource to get available realms and possibiltity to select realm in user form. - Uploaded file preview (trivial, can even be ignored) - --Add loading spinner to application: http://mvnrepository.com/artifact/org.webjars.bower/angular-spinner-- - --Add Resource management to create/edit user wizard (if needed).-- - --Add Group management to create/edit user wizard (if needed).-- - AngularJS unit testing: implement unit tests for angular frontend and possibly integrate them with maven build lifecycle. - Improve date management edit/create form: add timepicker when needed. - --Improve error and exception management: especially messages sent by resource to angular frontend.-- - Add password stregth validator to user creation form. - --Add CAPTCHA field in self registration form.-- - Add javadoc and if possible javascript doc - --Add protection mechanisms against XSRF/CSRF attacks.-- was: Enhancements to implement: - --Align login form to admin console's-- - --Align derived and virtual attributes management to admin console's-- - Add form frontend validation through AngularJS built-in form services. - --Secure authentication process: at the moment username and password are passed "clearly" to wicket resource in the payload of the POST. to achieve this configure HTTPS connection--. - Realms management (if needed): Add http resource to get available realms and possibiltity to select realm in user form. - Uploaded file preview (trivial, can even be ignored) - Add loading spinner to application: http://mvnrepository.com/artifact/org.webjars.bower/angular-spinner - --Add Resource management to create/edit user wizard (if needed).-- - --Add Group management to create/edit user wizard (if needed).-- - AngularJS unit testing: implement unit tests for angular frontend and possibly integrate them with maven build lifecycle. - Improve date management edit/create form: add timepicker when needed. - --Improve error and exception management: especially messages sent by resource to angular frontend.-- - Add password stregth validator to user creation form. - --Add CAPTCHA field in self registration form.-- - Add javadoc and if possible javascript doc - --Add protection mechanisms against XSRF/CSRF attacks.-- > UI enhancements > --- > > Key: SYNCOPE-719 > URL: https://issues.apache.org/jira/browse/SYNCOPE-719 > Project: Syncope > Issue Type: Sub-task > Components: enduser >Affects Versions: 2.0.0-M1 >Reporter: Andrea Patricelli >Assignee: Andrea Patricelli > Fix For: 2.0.0 > > > Enhancements to implement: > - --Align login form to admin console's-- > - --Align derived and virtual attributes management to admin console's-- > - Add form frontend validation through AngularJS built-in form services. > - --Secure authentication process: at the moment username and password are > passed "clearly" to wicket resource in the payload of the POST. to achieve > this configure HTTPS connection--. > - Realms management (if needed): Add http resource to get available realms > and possibiltity to select realm in user form. > - Uploaded file preview (trivial, can even be ignored) > - --Add loading spinner to application: > http://mvnrepository.com/artifact/org.webjars.bower/angular-spinner-- > - --Add Resource management to create/edit user wizard (if needed).-- > - --Add Group management to create/edit user wizard (if needed).-- > - AngularJS unit testing: implement unit tests for angular frontend and > possibly integrate them with maven build lifecycle. > - Improve date management edit/create form: add timepicker when needed. > - --Improve error and exception management: especially messages sent by > resource to angular frontend.-- > - Add password stregth validator to user creation form. > - --Add CAPTCHA field in self registration form.-- > - Add javadoc and if possible javascript doc > - --Add protection mechanisms against XSRF/CSRF attacks.-- -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SYNCOPE-719) UI enhancements
[ https://issues.apache.org/jira/browse/SYNCOPE-719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giacomo Lamonaco updated SYNCOPE-719: - Description: Enhancements to implement: - --Align login form to admin console's-- - --Align derived and virtual attributes management to admin console's-- - Add form frontend validation through AngularJS built-in form services. - --Secure authentication process: at the moment username and password are passed "clearly" to wicket resource in the payload of the POST. to achieve this configure HTTPS connection--. - Realms management (if needed): Add http resource to get available realms and possibiltity to select realm in user form. - Uploaded file preview (trivial, can even be ignored) - Add loading spinner to application: http://mvnrepository.com/artifact/org.webjars.bower/angular-spinner - --Add Resource management to create/edit user wizard (if needed).-- - --Add Group management to create/edit user wizard (if needed).-- - AngularJS unit testing: implement unit tests for angular frontend and possibly integrate them with maven build lifecycle. - Improve date management edit/create form: add timepicker when needed. - --Improve error and exception management: especially messages sent by resource to angular frontend.-- - Add password stregth validator to user creation form. - --Add CAPTCHA field in self registration form.-- - Add javadoc and if possible javascript doc - --Add protection mechanisms against XSRF/CSRF attacks.-- was: Enhancements to implement: - --Align login form to admin console's-- - --Align derived and virtual attributes management to admin console's-- - Add form frontend validation through AngularJS built-in form services. - --Secure authentication process: at the moment username and password are passed "clearly" to wicket resource in the payload of the POST. to achieve this configure HTTPS connection--. - Realms management (if needed): Add http resource to get available realms and possibiltity to select realm in user form. - Uploaded file preview (trivial, can even be ignored) - Add loading spinner to application: http://mvnrepository.com/artifact/org.webjars.bower/angular-spinner - --Add Resource management to create/edit user wizard (if needed).-- - Add Group management to create/edit user wizard (if needed). - AngularJS unit testing: implement unit tests for angular frontend and possibly integrate them with maven build lifecycle. - Improve date management edit/create form: add timepicker when needed. - --Improve error and exception management: especially messages sent by resource to angular frontend.-- - Add password stregth validator to user creation form. - --Add CAPTCHA field in self registration form.-- - Add javadoc and if possible javascript doc - --Add protection mechanisms against XSRF/CSRF attacks.-- > UI enhancements > --- > > Key: SYNCOPE-719 > URL: https://issues.apache.org/jira/browse/SYNCOPE-719 > Project: Syncope > Issue Type: Sub-task > Components: enduser >Affects Versions: 2.0.0-M1 >Reporter: Andrea Patricelli >Assignee: Andrea Patricelli > Fix For: 2.0.0 > > > Enhancements to implement: > - --Align login form to admin console's-- > - --Align derived and virtual attributes management to admin console's-- > - Add form frontend validation through AngularJS built-in form services. > - --Secure authentication process: at the moment username and password are > passed "clearly" to wicket resource in the payload of the POST. to achieve > this configure HTTPS connection--. > - Realms management (if needed): Add http resource to get available realms > and possibiltity to select realm in user form. > - Uploaded file preview (trivial, can even be ignored) > - Add loading spinner to application: > http://mvnrepository.com/artifact/org.webjars.bower/angular-spinner > - --Add Resource management to create/edit user wizard (if needed).-- > - --Add Group management to create/edit user wizard (if needed).-- > - AngularJS unit testing: implement unit tests for angular frontend and > possibly integrate them with maven build lifecycle. > - Improve date management edit/create form: add timepicker when needed. > - --Improve error and exception management: especially messages sent by > resource to angular frontend.-- > - Add password stregth validator to user creation form. > - --Add CAPTCHA field in self registration form.-- > - Add javadoc and if possible javascript doc > - --Add protection mechanisms against XSRF/CSRF attacks.-- -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SYNCOPE-720) Unauthenticated password reset functionality
[ https://issues.apache.org/jira/browse/SYNCOPE-720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giacomo Lamonaco resolved SYNCOPE-720. -- Resolution: Fixed Password reset functionality now is fully implemented > Unauthenticated password reset functionality > > > Key: SYNCOPE-720 > URL: https://issues.apache.org/jira/browse/SYNCOPE-720 > Project: Syncope > Issue Type: Sub-task > Components: enduser >Affects Versions: 2.0.0-M1 >Reporter: Andrea Patricelli >Assignee: Giacomo Lamonaco > Fix For: 2.0.0 > > > Implement missing password reset functionality. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SYNCOPE-719) UI enhancements
[ https://issues.apache.org/jira/browse/SYNCOPE-719?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giacomo Lamonaco updated SYNCOPE-719: - Description: Enhancements to implement: - --Align login form to admin console's-- - --Align derived and virtual attributes management to admin console's-- - Add form frontend validation through AngularJS built-in form services. - --Secure authentication process: at the moment username and password are passed "clearly" to wicket resource in the payload of the POST. to achieve this configure HTTPS connection--. - Realms management (if needed): Add http resource to get available realms and possibiltity to select realm in user form. - Uploaded file preview (trivial, can even be ignored) - Add loading spinner to application: http://mvnrepository.com/artifact/org.webjars.bower/angular-spinner - --Add Resource management to create/edit user wizard (if needed).-- - Add Group management to create/edit user wizard (if needed). - AngularJS unit testing: implement unit tests for angular frontend and possibly integrate them with maven build lifecycle. - Improve date management edit/create form: add timepicker when needed. - --Improve error and exception management: especially messages sent by resource to angular frontend.-- - Add password stregth validator to user creation form. - --Add CAPTCHA field in self registration form.-- - Add javadoc and if possible javascript doc - --Add protection mechanisms against XSRF/CSRF attacks.-- was: Enhancements to implement: - --Align login form to admin console's-- - --Align derived and virtual attributes management to admin console's-- - Add form frontend validation through AngularJS built-in form services. - Secure authentication process: at the moment username and password are passed "clearly" to wicket resource in the payload of the POST. to achieve this configure HTTPS connection. - Realms management (if needed): Add http resource to get available realms and possibiltity to select realm in user form. - Uploaded file preview (trivial, can even be ignored) - Add loading spinner to application: http://mvnrepository.com/artifact/org.webjars.bower/angular-spinner - --Add Resource management to create/edit user wizard (if needed).-- - Add Group management to create/edit user wizard (if needed). - AngularJS unit testing: implement unit tests for angular frontend and possibly integrate them with maven build lifecycle. - Improve date management edit/create form: add timepicker when needed. - --Improve error and exception management: especially messages sent by resource to angular frontend.-- - Add password stregth validator to user creation form. - --Add CAPTCHA field in self registration form.-- - Add javadoc and if possible javascript doc - --Add protection mechanisms against XSRF/CSRF attacks.-- > UI enhancements > --- > > Key: SYNCOPE-719 > URL: https://issues.apache.org/jira/browse/SYNCOPE-719 > Project: Syncope > Issue Type: Sub-task > Components: enduser >Affects Versions: 2.0.0-M1 >Reporter: Andrea Patricelli >Assignee: Andrea Patricelli > Fix For: 2.0.0 > > > Enhancements to implement: > - --Align login form to admin console's-- > - --Align derived and virtual attributes management to admin console's-- > - Add form frontend validation through AngularJS built-in form services. > - --Secure authentication process: at the moment username and password are > passed "clearly" to wicket resource in the payload of the POST. to achieve > this configure HTTPS connection--. > - Realms management (if needed): Add http resource to get available realms > and possibiltity to select realm in user form. > - Uploaded file preview (trivial, can even be ignored) > - Add loading spinner to application: > http://mvnrepository.com/artifact/org.webjars.bower/angular-spinner > - --Add Resource management to create/edit user wizard (if needed).-- > - Add Group management to create/edit user wizard (if needed). > - AngularJS unit testing: implement unit tests for angular frontend and > possibly integrate them with maven build lifecycle. > - Improve date management edit/create form: add timepicker when needed. > - --Improve error and exception management: especially messages sent by > resource to angular frontend.-- > - Add password stregth validator to user creation form. > - --Add CAPTCHA field in self registration form.-- > - Add javadoc and if possible javascript doc > - --Add protection mechanisms against XSRF/CSRF attacks.-- -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (SYNCOPE-720) Unauthenticated password reset functionality
[ https://issues.apache.org/jira/browse/SYNCOPE-720?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giacomo Lamonaco reassigned SYNCOPE-720: Assignee: Giacomo Lamonaco > Unauthenticated password reset functionality > > > Key: SYNCOPE-720 > URL: https://issues.apache.org/jira/browse/SYNCOPE-720 > Project: Syncope > Issue Type: Sub-task > Components: enduser >Affects Versions: 2.0.0-M1 >Reporter: Andrea Patricelli >Assignee: Giacomo Lamonaco > Fix For: 2.0.0 > > > Implement missing password reset functionality. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SYNCOPE-675) Role tree construction takes some time if there are a lot roles
[ https://issues.apache.org/jira/browse/SYNCOPE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giacomo Lamonaco updated SYNCOPE-675: - Fix Version/s: (was: 1.2.5) Role tree construction takes some time if there are a lot roles --- Key: SYNCOPE-675 URL: https://issues.apache.org/jira/browse/SYNCOPE-675 Project: Syncope Issue Type: Improvement Components: console Affects Versions: 1.2.4 Reporter: Giacomo Lamonaco Assignee: Giacomo Lamonaco Priority: Minor MembershipPanel and TreeRolePanel visualize roles through a wicket tree. Try to create a lot of roles in Syncope. Then try to open the role page or try to edit an user opening the edit modal page. You will experience some delay (it depends also on your system performance). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (SYNCOPE-675) Role tree construction takes some time if there are a lot roles
[ https://issues.apache.org/jira/browse/SYNCOPE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giacomo Lamonaco closed SYNCOPE-675. Role tree construction takes some time if there are a lot roles --- Key: SYNCOPE-675 URL: https://issues.apache.org/jira/browse/SYNCOPE-675 Project: Syncope Issue Type: Improvement Components: console Affects Versions: 1.2.4 Reporter: Giacomo Lamonaco Assignee: Giacomo Lamonaco Priority: Minor MembershipPanel and TreeRolePanel visualize roles through a wicket tree. Try to create a lot of roles in Syncope. Then try to open the role page or try to edit an user opening the edit modal page. You will experience some delay (it depends also on your system performance). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SYNCOPE-675) Role tree construction takes some time if there are a lot roles
[ https://issues.apache.org/jira/browse/SYNCOPE-675?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giacomo Lamonaco resolved SYNCOPE-675. -- Resolution: Won't Fix SYNCOPE-676 made this issue outdated Role tree construction takes some time if there are a lot roles --- Key: SYNCOPE-675 URL: https://issues.apache.org/jira/browse/SYNCOPE-675 Project: Syncope Issue Type: Improvement Components: console Affects Versions: 1.2.4 Reporter: Giacomo Lamonaco Assignee: Giacomo Lamonaco Priority: Minor Fix For: 1.2.5 MembershipPanel and TreeRolePanel visualize roles through a wicket tree. Try to create a lot of roles in Syncope. Then try to open the role page or try to edit an user opening the edit modal page. You will experience some delay (it depends also on your system performance). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SYNCOPE-675) Role tree construction takes some time if there are a lot roles
Giacomo Lamonaco created SYNCOPE-675: Summary: Role tree construction takes some time if there are a lot roles Key: SYNCOPE-675 URL: https://issues.apache.org/jira/browse/SYNCOPE-675 Project: Syncope Issue Type: Improvement Components: console Affects Versions: 1.2.4 Reporter: Giacomo Lamonaco Assignee: Giacomo Lamonaco Priority: Minor Fix For: 1.2.5 MembershipPanel and TreeRolePanel visualize roles through a wicket tree. Try to create a lot of roles in Syncope. Then try to open the role page or try to edit an user opening the edit modal page. You will experience some delay (it depends also on your system performance). -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SYNCOPE-660) Extend control over asynchronous job execution
[ https://issues.apache.org/jira/browse/SYNCOPE-660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giacomo Lamonaco resolved SYNCOPE-660. -- Resolution: Fixed Extend control over asynchronous job execution -- Key: SYNCOPE-660 URL: https://issues.apache.org/jira/browse/SYNCOPE-660 Project: Syncope Issue Type: Improvement Reporter: Francesco Chicchiriccò Assignee: Giacomo Lamonaco Fix For: 1.2.5, 2.0.0 Asynchronous job execution, generally delegated to Quartz, can currently be checked only at completion, and only by indirectly checking the status on related JPA entities (TaskExec, ReportExec, ...). A REST endpoint should be provided for reporting on jobs execution and providing the ability to control (e.g. stop / pause / resume / ...) . -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (SYNCOPE-660) Extend control over asynchronous job execution
[ https://issues.apache.org/jira/browse/SYNCOPE-660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giacomo Lamonaco reopened SYNCOPE-660: -- Interruption of heavy tasks - like syncronization of a lot of users - doesn't work correctly: its status is still alive. Extend control over asynchronous job execution -- Key: SYNCOPE-660 URL: https://issues.apache.org/jira/browse/SYNCOPE-660 Project: Syncope Issue Type: Improvement Reporter: Francesco Chicchiriccò Assignee: Giacomo Lamonaco Fix For: 1.2.5, 2.0.0 Asynchronous job execution, generally delegated to Quartz, can currently be checked only at completion, and only by indirectly checking the status on related JPA entities (TaskExec, ReportExec, ...). A REST endpoint should be provided for reporting on jobs execution and providing the ability to control (e.g. stop / pause / resume / ...) . -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SYNCOPE-674) NotificationManager should be able to return a list of created task ids
[ https://issues.apache.org/jira/browse/SYNCOPE-674?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giacomo Lamonaco resolved SYNCOPE-674. -- Resolution: Fixed NotificationManager should be able to return a list of created task ids --- Key: SYNCOPE-674 URL: https://issues.apache.org/jira/browse/SYNCOPE-674 Project: Syncope Issue Type: Improvement Components: core Reporter: Giacomo Lamonaco Assignee: Giacomo Lamonaco Priority: Minor Fix For: 1.2.5, 2.0.0 During tasks creation, the notification manager should be able to return a list of task id. In this way, it could be possible to retrieve immediately these tasks and modify them before their execution. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SYNCOPE-674) NotificationManager should be able to return a list of created task ids
Giacomo Lamonaco created SYNCOPE-674: Summary: NotificationManager should be able to return a list of created task ids Key: SYNCOPE-674 URL: https://issues.apache.org/jira/browse/SYNCOPE-674 Project: Syncope Issue Type: Improvement Components: core Reporter: Giacomo Lamonaco Assignee: Giacomo Lamonaco Priority: Minor Fix For: 1.2.5, 2.0.0 During tasks creation, the notification manager should be able to return a list of task id. In this way, it could be possible to retrieve immediately these tasks and modify them before their execution. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SYNCOPE-660) Extend control over asynchronous job execution
[ https://issues.apache.org/jira/browse/SYNCOPE-660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giacomo Lamonaco resolved SYNCOPE-660. -- Resolution: Fixed Extend control over asynchronous job execution -- Key: SYNCOPE-660 URL: https://issues.apache.org/jira/browse/SYNCOPE-660 Project: Syncope Issue Type: Improvement Reporter: Francesco Chicchiriccò Assignee: Giacomo Lamonaco Fix For: 1.2.5, 2.0.0 Asynchronous job execution, generally delegated to Quartz, can currently be checked only at completion, and only by indirectly checking the status on related JPA entities (TaskExec, ReportExec, ...). A REST endpoint should be provided for reporting on jobs execution and providing the ability to control (e.g. stop / pause / resume / ...) . -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (SYNCOPE-660) Extend control over asynchronous job execution
[ https://issues.apache.org/jira/browse/SYNCOPE-660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giacomo Lamonaco reopened SYNCOPE-660: -- Console counterpart mising Extend control over asynchronous job execution -- Key: SYNCOPE-660 URL: https://issues.apache.org/jira/browse/SYNCOPE-660 Project: Syncope Issue Type: Improvement Reporter: Francesco Chicchiriccò Assignee: Giacomo Lamonaco Fix For: 1.2.5, 2.0.0 Asynchronous job execution, generally delegated to Quartz, can currently be checked only at completion, and only by indirectly checking the status on related JPA entities (TaskExec, ReportExec, ...). A REST endpoint should be provided for reporting on jobs execution and providing the ability to control (e.g. stop / pause / resume / ...) . -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SYNCOPE-668) JobInstanceLoader class is not able to return the correct Task id or Report id from its job name
[ https://issues.apache.org/jira/browse/SYNCOPE-668?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giacomo Lamonaco resolved SYNCOPE-668. -- Resolution: Fixed JobInstanceLoader class is not able to return the correct Task id or Report id from its job name - Key: SYNCOPE-668 URL: https://issues.apache.org/jira/browse/SYNCOPE-668 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.2.4 Reporter: Giacomo Lamonaco Assignee: Giacomo Lamonaco Fix For: 1.2.5, 2.0.0 Create a Task or a Report in Syncope: the related job is created automatically. If you try to get the taskId or a reportId starting from a Job Name, using the getTaskIdFromJobName or getReportIdFromJobName method, you will receive a null value. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SYNCOPE-668) JobInstanceLoader class is not able to return the correct Task id or Report id from its job name
Giacomo Lamonaco created SYNCOPE-668: Summary: JobInstanceLoader class is not able to return the correct Task id or Report id from its job name Key: SYNCOPE-668 URL: https://issues.apache.org/jira/browse/SYNCOPE-668 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.2.4 Reporter: Giacomo Lamonaco Assignee: Giacomo Lamonaco Fix For: 1.2.5, 2.0.0 Create a Task or a Report in Syncope: the related job is created automatically. If you try to get the taskId or a reportId starting from a Job Name, using the getTaskIdFromJobName or getReportIdFromJobName method, you will receive a null value. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SYNCOPE-660) Extend control over asynchronous job execution
[ https://issues.apache.org/jira/browse/SYNCOPE-660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giacomo Lamonaco updated SYNCOPE-660: - Fix Version/s: 1.2.5 Assignee: Giacomo Lamonaco Extend control over asynchronous job execution -- Key: SYNCOPE-660 URL: https://issues.apache.org/jira/browse/SYNCOPE-660 Project: Syncope Issue Type: Improvement Reporter: Francesco Chicchiriccò Assignee: Giacomo Lamonaco Fix For: 1.2.5, 2.0.0 Asynchronous job execution, generally delegated to Quartz, can currently be checked only at completion, and only by indirectly checking the status on related JPA entities (TaskExec, ReportExec, ...). A REST endpoint should be provided for reporting on jobs execution and providing the ability to control (e.g. stop / pause / resume / ...) . -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (SYNCOPE-654) Some generic and uninformative error messages
[
https://issues.apache.org/jira/browse/SYNCOPE-654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Giacomo Lamonaco reassigned SYNCOPE-654:
Assignee: Giacomo Lamonaco
Some generic and uninformative error messages
-
Key: SYNCOPE-654
URL: https://issues.apache.org/jira/browse/SYNCOPE-654
Project: Syncope
Issue Type: Bug
Components: core
Affects Versions: 1.2.3
Reporter: Francesco Chicchiriccò
Assignee: Giacomo Lamonaco
Fix For: 1.2.4, 2.0.0
Under some circumstances, the error message reported is not very informative;
try, for example, to
# define a user or role schema with unique flag
# create first user (or group) with certain value for such a schema
# attempt to create another user (or group) with same value
# error is raised (correctly) but message says DataIntegrityViolation [The
transaction has been rolled back. See the nested exceptions for details on
the errors that occurred.]
Besides this specific case, more tests should be added to check at least
every case managed by {{RestServiceExceptionMapper}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Resolved] (SYNCOPE-654) Some generic and uninformative error messages
[
https://issues.apache.org/jira/browse/SYNCOPE-654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Giacomo Lamonaco resolved SYNCOPE-654.
--
Resolution: Fixed
Some generic and uninformative error messages
-
Key: SYNCOPE-654
URL: https://issues.apache.org/jira/browse/SYNCOPE-654
Project: Syncope
Issue Type: Bug
Components: core
Affects Versions: 1.2.3
Reporter: Francesco Chicchiriccò
Assignee: Giacomo Lamonaco
Fix For: 1.2.4, 2.0.0
Under some circumstances, the error message reported is not very informative;
try, for example, to
# define a user or role schema with unique flag
# create first user (or group) with certain value for such a schema
# attempt to create another user (or group) with same value
# error is raised (correctly) but message says DataIntegrityViolation [The
transaction has been rolled back. See the nested exceptions for details on
the errors that occurred.]
Besides this specific case, more tests should be added to check at least
every case managed by {{RestServiceExceptionMapper}}.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (SYNCOPE-628) Provide guide for enabling Jel.Camel
[ https://issues.apache.org/jira/browse/SYNCOPE-628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giacomo Lamonaco updated SYNCOPE-628: - Fix Version/s: (was: 2.0.0) Provide guide for enabling Jel.Camel Key: SYNCOPE-628 URL: https://issues.apache.org/jira/browse/SYNCOPE-628 Project: Syncope Issue Type: Improvement Components: console, documentation Reporter: Francesco Chicchiriccò Assignee: Giacomo Lamonaco [Jel.Camel|https://github.com/giacomolm/jel.camel] is a tool for Camel route graphical management, also reported in Camel's [user stories|http://camel.apache.org/user-stories.htm]. Similarly to [this guide for enabling the Activiti Modeler in the admin console|https://cwiki.apache.org/confluence/display/SYNCOPE/Enable+Activiti+Modeler], provide a guide for enabling Jel.Camel. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (SYNCOPE-628) Provide guide for enabling Jel.Camel
[ https://issues.apache.org/jira/browse/SYNCOPE-628?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giacomo Lamonaco closed SYNCOPE-628. Resolution: Unresolved Jel is not ready for a stable integration in Syncope. Provide guide for enabling Jel.Camel Key: SYNCOPE-628 URL: https://issues.apache.org/jira/browse/SYNCOPE-628 Project: Syncope Issue Type: Improvement Components: console, documentation Reporter: Francesco Chicchiriccò Assignee: Giacomo Lamonaco [Jel.Camel|https://github.com/giacomolm/jel.camel] is a tool for Camel route graphical management, also reported in Camel's [user stories|http://camel.apache.org/user-stories.htm]. Similarly to [this guide for enabling the Activiti Modeler in the admin console|https://cwiki.apache.org/confluence/display/SYNCOPE/Enable+Activiti+Modeler], provide a guide for enabling Jel.Camel. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SYNCOPE-638) MAttrTemplate and RAttrTemplate sequence values are not managed in content.xml
Giacomo Lamonaco created SYNCOPE-638: Summary: MAttrTemplate and RAttrTemplate sequence values are not managed in content.xml Key: SYNCOPE-638 URL: https://issues.apache.org/jira/browse/SYNCOPE-638 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.2.2 Reporter: Giacomo Lamonaco Assignee: Giacomo Lamonaco Fix For: 1.2.3, 1.3.0 Create a membership schema and assing it to a role. Now export your content.xml: you will see that there isn't an entry specifing MAttrTemplate and RAttrTemplate sequence value in Openjpa Sequences Table section. Moreover, if you try to insert these values manually, they will not be considered in a next run. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SYNCOPE-638) MAttrTemplate and RAttrTemplate sequence values are not managed in content.xml
[ https://issues.apache.org/jira/browse/SYNCOPE-638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giacomo Lamonaco updated SYNCOPE-638: - Assignee: (was: Giacomo Lamonaco) MAttrTemplate and RAttrTemplate sequence values are not managed in content.xml -- Key: SYNCOPE-638 URL: https://issues.apache.org/jira/browse/SYNCOPE-638 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.2.2 Reporter: Giacomo Lamonaco Fix For: 1.2.3, 1.3.0 Create a membership schema and assing it to a role. Now export your content.xml: you will see that there isn't an entry specifing MAttrTemplate and RAttrTemplate sequence value in Openjpa Sequences Table section. Moreover, if you try to insert these values manually, they will not be considered in a next run. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SYNCOPE-627) Camel provisioning manager: separate user / role route management and introduce Unit Test
[ https://issues.apache.org/jira/browse/SYNCOPE-627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giacomo Lamonaco resolved SYNCOPE-627. -- Resolution: Fixed Camel provisioning manager: separate user / role route management and introduce Unit Test - Key: SYNCOPE-627 URL: https://issues.apache.org/jira/browse/SYNCOPE-627 Project: Syncope Issue Type: Improvement Components: console, core Reporter: Francesco Chicchiriccò Assignee: Giacomo Lamonaco Fix For: 1.3.0 The current Camel provisioning manager does not distinguish between user and role operations for REST calls. Only the console module (partially) supports this difference. Maybe it's better to have fine-grained methods. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SYNCOPE-629) ATTRTEMPLATE entities not exported
[ https://issues.apache.org/jira/browse/SYNCOPE-629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giacomo Lamonaco resolved SYNCOPE-629. -- Resolution: Fixed ATTRTEMPLATE entities not exported -- Key: SYNCOPE-629 URL: https://issues.apache.org/jira/browse/SYNCOPE-629 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.2.1, 1.3.0 Reporter: Giacomo Lamonaco Assignee: Giacomo Lamonaco Fix For: 1.2.2, 1.3.0 R*ATTRTEMPLATE and M*ATTRTEMPLATE (6 tables) aren't correctly exported in the content.xml resulting file. This problem reflect in the following example scenario. Create a custom membership schema attribute. Go under role, and assign this attribute to any role: set this attribute as selected. Now under configuration export your current content. In the resulting file there isn't any information about template configuration. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SYNCOPE-629) Membership settings in role template aren't correctly exported
[ https://issues.apache.org/jira/browse/SYNCOPE-629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giacomo Lamonaco updated SYNCOPE-629: - Fix Version/s: 1.3.0 1.2.2 Membership settings in role template aren't correctly exported -- Key: SYNCOPE-629 URL: https://issues.apache.org/jira/browse/SYNCOPE-629 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.2.1, 1.3.0 Reporter: Giacomo Lamonaco Assignee: Giacomo Lamonaco Fix For: 1.2.2, 1.3.0 Create a custom membership schema attribute. Go under role, and assign this attribute to any role: set this attribute as selected. Now under configuration export your current content. In the resulting file there isn't any information about template configuration. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SYNCOPE-629) ATTRTEMPLATE entities aren't not exported
[ https://issues.apache.org/jira/browse/SYNCOPE-629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giacomo Lamonaco updated SYNCOPE-629: - Summary: ATTRTEMPLATE entities aren't not exported (was: ATTRTEMPLATE entity aren't not exported) ATTRTEMPLATE entities aren't not exported - Key: SYNCOPE-629 URL: https://issues.apache.org/jira/browse/SYNCOPE-629 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.2.1, 1.3.0 Reporter: Giacomo Lamonaco Assignee: Giacomo Lamonaco Fix For: 1.2.2, 1.3.0 R*ATTRTEMPLATE and M*ATTRTEMPLATE (6 tables) aren't correctly exported in the content.xml resulting file. This problem reflect in the following example scenario. Create a custom membership schema attribute. Go under role, and assign this attribute to any role: set this attribute as selected. Now under configuration export your current content. In the resulting file there isn't any information about template configuration. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SYNCOPE-629) ATTRTEMPLATE entity aren't not exported
[ https://issues.apache.org/jira/browse/SYNCOPE-629?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giacomo Lamonaco updated SYNCOPE-629: - Description: R*ATTRTEMPLATE and M*ATTRTEMPLATE (6 tables) aren't correctly exported in the content.xml resulting file. This problem reflect in the following example scenario. Create a custom membership schema attribute. Go under role, and assign this attribute to any role: set this attribute as selected. Now under configuration export your current content. In the resulting file there isn't any information about template configuration. was:Create a custom membership schema attribute. Go under role, and assign this attribute to any role: set this attribute as selected. Now under configuration export your current content. In the resulting file there isn't any information about template configuration. Summary: ATTRTEMPLATE entity aren't not exported (was: Membership settings in role template aren't correctly exported) ATTRTEMPLATE entity aren't not exported --- Key: SYNCOPE-629 URL: https://issues.apache.org/jira/browse/SYNCOPE-629 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.2.1, 1.3.0 Reporter: Giacomo Lamonaco Assignee: Giacomo Lamonaco Fix For: 1.2.2, 1.3.0 R*ATTRTEMPLATE and M*ATTRTEMPLATE (6 tables) aren't correctly exported in the content.xml resulting file. This problem reflect in the following example scenario. Create a custom membership schema attribute. Go under role, and assign this attribute to any role: set this attribute as selected. Now under configuration export your current content. In the resulting file there isn't any information about template configuration. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SYNCOPE-629) Membership settings in role template aren't correctly exported
Giacomo Lamonaco created SYNCOPE-629: Summary: Membership settings in role template aren't correctly exported Key: SYNCOPE-629 URL: https://issues.apache.org/jira/browse/SYNCOPE-629 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.2.1, 1.3.0 Reporter: Giacomo Lamonaco Assignee: Giacomo Lamonaco Create a custom membership schema attribute. Go under role, and assign this attribute to any role: set this attribute as selected. Now under configuration export your current content. In the resulting file there isn't any information about template configuration. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SYNCOPE-627) Camel provisioning manager: separate user / role route management and introduce Unit Test
[ https://issues.apache.org/jira/browse/SYNCOPE-627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giacomo Lamonaco updated SYNCOPE-627: - Summary: Camel provisioning manager: separate user / role route management and introduce Unit Test (was: Camel provisioning manager: separate user / role route management) Camel provisioning manager: separate user / role route management and introduce Unit Test - Key: SYNCOPE-627 URL: https://issues.apache.org/jira/browse/SYNCOPE-627 Project: Syncope Issue Type: Improvement Components: console, core Reporter: Francesco Chicchiriccò Assignee: Giacomo Lamonaco Fix For: 1.3.0 The current Camel provisioning manager does not distinguish between user and role operations for REST calls. Only the console module (partially) supports this difference. Maybe it's better to have fine-grained methods. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (SYNCOPE-627) Camel provisioning manager: separate user / role route management
[ https://issues.apache.org/jira/browse/SYNCOPE-627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giacomo Lamonaco reopened SYNCOPE-627: -- Console problems while updating routes Camel provisioning manager: separate user / role route management - Key: SYNCOPE-627 URL: https://issues.apache.org/jira/browse/SYNCOPE-627 Project: Syncope Issue Type: Improvement Components: console, core Reporter: Francesco Chicchiriccò Assignee: Giacomo Lamonaco Fix For: 1.3.0 The current Camel provisioning manager does not distinguish between user and role operations for REST calls. Only the console module (partially) supports this difference. Maybe it's better to have fine-grained methods. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (SYNCOPE-627) Camel provisioning manager: separate user / role route management
[ https://issues.apache.org/jira/browse/SYNCOPE-627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giacomo Lamonaco closed SYNCOPE-627. Resolution: Fixed Camel provisioning manager: separate user / role route management - Key: SYNCOPE-627 URL: https://issues.apache.org/jira/browse/SYNCOPE-627 Project: Syncope Issue Type: Improvement Components: console, core Reporter: Francesco Chicchiriccò Assignee: Giacomo Lamonaco Fix For: 1.3.0 The current Camel provisioning manager does not distinguish between user and role operations for REST calls. Only the console module (partially) supports this difference. Maybe it's better to have fine-grained methods. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SYNCOPE-627) Camel provisioning manager: separate user / role route management
[ https://issues.apache.org/jira/browse/SYNCOPE-627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giacomo Lamonaco resolved SYNCOPE-627. -- Resolution: Fixed Camel provisioning manager: separate user / role route management - Key: SYNCOPE-627 URL: https://issues.apache.org/jira/browse/SYNCOPE-627 Project: Syncope Issue Type: Improvement Components: console, core Reporter: Francesco Chicchiriccò Assignee: Giacomo Lamonaco Fix For: 1.3.0 The current Camel provisioning manager does not distinguish between user and role operations for REST calls. Only the console module (partially) supports this difference. Maybe it's better to have fine-grained methods. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Reopened] (SYNCOPE-627) Camel provisioning manager: separate user / role route management
[ https://issues.apache.org/jira/browse/SYNCOPE-627?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giacomo Lamonaco reopened SYNCOPE-627: -- Converting to resolved Camel provisioning manager: separate user / role route management - Key: SYNCOPE-627 URL: https://issues.apache.org/jira/browse/SYNCOPE-627 Project: Syncope Issue Type: Improvement Components: console, core Reporter: Francesco Chicchiriccò Assignee: Giacomo Lamonaco Fix For: 1.3.0 The current Camel provisioning manager does not distinguish between user and role operations for REST calls. Only the console module (partially) supports this difference. Maybe it's better to have fine-grained methods. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SYNCOPE-623) Provisioning manager integration
Giacomo Lamonaco created SYNCOPE-623: Summary: Provisioning manager integration Key: SYNCOPE-623 URL: https://issues.apache.org/jira/browse/SYNCOPE-623 Project: Syncope Issue Type: New Feature Components: common, console, core Reporter: Giacomo Lamonaco Assignee: Giacomo Lamonaco Fix For: 1.3.0 Hi all, last year with the help of Syncope team I proposed an early reformulation of provisioning phase. Provisioning refers to methods used to provide users and roles functionality: the main goal of my proposal was to re-organize this phase, allowing custom provisioning behaviours through a definition of a provisioning manager. Initially I submitted a request to dev@syncope: in this discussion [1] you can read all the tecnical details. Amongst other things, in this proposal I thought to use Apache Camel as base of the provisioning manager. In the subsequent 3/4 months, with the help of a talented Camel commiter, I obtained something that looks interesting. We decided to make provisioning pluggable: in this way user decide the default provisioning engine. Moreover a the end of this work we provided some console feature, in order to change provisioning definitions - only in the Camel case btw. Some days ago, I tried to merge all my modifications with the current version of Syncope: after some days of work, everything is back to work. I thought to create a github pull request [2],in order to give to Syncope Team members to examine this work. [1] http://syncope-dev.1063484.n5.nabble.com/Proposal-An-Apache-Camel-Integratation-Proposal-td5714531.html [2] https://github.com/apache/syncope/pull/2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SYNCOPE-624) Provisioning manager integration
Giacomo Lamonaco created SYNCOPE-624: Summary: Provisioning manager integration Key: SYNCOPE-624 URL: https://issues.apache.org/jira/browse/SYNCOPE-624 Project: Syncope Issue Type: New Feature Components: common, console, core Reporter: Giacomo Lamonaco Assignee: Giacomo Lamonaco Fix For: 1.3.0 Hi all, last year with the help of Syncope team I proposed an early reformulation of provisioning phase. Provisioning refers to methods used to provide users and roles functionality: the main goal of my proposal was to re-organize this phase, allowing custom provisioning behaviours through a definition of a provisioning manager. Initially I submitted a request to dev@syncope: in this discussion [1] you can read all the tecnical details. Amongst other things, in this proposal I thought to use Apache Camel as base of the provisioning manager. In the subsequent 3/4 months, with the help of a talented Camel commiter, I obtained something that looks interesting. We decided to make provisioning pluggable: in this way user decide the default provisioning engine. Moreover a the end of this work we provided some console feature, in order to change provisioning definitions - only in the Camel case btw. Some days ago, I tried to merge all my modifications with the current version of Syncope: after some days of work, everything is back to work. I thought to create a github pull request [2],in order to give to Syncope Team members to examine this work. [1] http://syncope-dev.1063484.n5.nabble.com/Proposal-An-Apache-Camel-Integratation-Proposal-td5714531.html [2] https://github.com/apache/syncope/pull/2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SYNCOPE-623) Provisioning manager integration
[ https://issues.apache.org/jira/browse/SYNCOPE-623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giacomo Lamonaco updated SYNCOPE-623: - Description: Hi all, last year with the help of Syncope team I proposed an early reformulation of provisioning phase. Provisioning refers to methods used to provide users and roles functionality: the main goal of my proposal was to re-organize this phase, allowing custom provisioning behaviours through a definition of a provisioning manager (see here [1] more details). The current strategy adopted in Syncope makes difficult the definition of custom provisioning behaviour. The solution enclosed with this issue aim to decompose the provisioning phase. Previously the user/role controller deals directly with provisioning, while now with this proposal both the controller delegates this task to provisioning manager. A first task was to move all provisioning functionality into the provisioning manager. If you now inspect the user/role controller code, you will not find anymore workflow and propagation dependencies. During the development, we thought to make the provisioning pluggable, in order to allow the choice of provisioning engine. The default provisioning engine can be choosed editing the provisioning.properties file. For this reason we hardcoded previous strategies as default provisioning manager, in order to keep the standard Syncope behaviour. As we proposed initially, we wanted also to experiment a provisionig manager based on a Apache Camel. Camel is a powerful integration framework implementing enterprise integration pattern. Our current solution embeds the provisioning logics into camel routes. Moreover the current solution extends also Syncope Console: we added new a new functionality - related to Camel case - that allows to read and edit routes definitions. You can find this new service under the Console-Configuration-Routes section. In this case, routes are expressed through Spring DSL. To finish, I thought to create a github pull request [2],in order to give to Syncope Team members to examine this work and possibly integrate it. [1] http://syncope-dev.1063484.n5.nabble.com/Proposal-An-Apache-Camel-Integratation-Proposal-td5714531.html [2] https://github.com/apache/syncope/pull/2 was: Hi all, last year with the help of Syncope team I proposed an early reformulation of provisioning phase. Provisioning refers to methods used to provide users and roles functionality: the main goal of my proposal was to re-organize this phase, allowing custom provisioning behaviours through a definition of a provisioning manager. Initially I submitted a request to dev@syncope: in this discussion [1] you can read all the tecnical details. Amongst other things, in this proposal I thought to use Apache Camel as base of the provisioning manager. In the subsequent 3/4 months, with the help of a talented Camel commiter, I obtained something that looks interesting. We decided to make provisioning pluggable: in this way user decide the default provisioning engine. Moreover a the end of this work we provided some console feature, in order to change provisioning definitions - only in the Camel case btw. Some days ago, I tried to merge all my modifications with the current version of Syncope: after some days of work, everything is back to work. I thought to create a github pull request [2],in order to give to Syncope Team members to examine this work. [1] http://syncope-dev.1063484.n5.nabble.com/Proposal-An-Apache-Camel-Integratation-Proposal-td5714531.html [2] https://github.com/apache/syncope/pull/2 Provisioning manager integration Key: SYNCOPE-623 URL: https://issues.apache.org/jira/browse/SYNCOPE-623 Project: Syncope Issue Type: New Feature Components: common, console, core Reporter: Giacomo Lamonaco Assignee: Giacomo Lamonaco Fix For: 1.3.0 Hi all, last year with the help of Syncope team I proposed an early reformulation of provisioning phase. Provisioning refers to methods used to provide users and roles functionality: the main goal of my proposal was to re-organize this phase, allowing custom provisioning behaviours through a definition of a provisioning manager (see here [1] more details). The current strategy adopted in Syncope makes difficult the definition of custom provisioning behaviour. The solution enclosed with this issue aim to decompose the provisioning phase. Previously the user/role controller deals directly with provisioning, while now with this proposal both the controller delegates this task to provisioning manager. A first task was to move all provisioning functionality into the provisioning manager. If you now inspect the user/role controller code, you will not find anymore
[jira] [Updated] (SYNCOPE-623) Provisioning manager integration
[ https://issues.apache.org/jira/browse/SYNCOPE-623?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giacomo Lamonaco updated SYNCOPE-623: - Description: Last year with the help of Syncope team I proposed an early reformulation of provisioning phase. Provisioning refers to methods used to provide users and roles functionality: the main goal of my proposal was to re-organize this phase, allowing custom provisioning behaviours through a definition of a provisioning manager (see here [1] more details). The current strategy adopted in Syncope makes difficult the definition of custom provisioning behaviour. The solution enclosed with this issue aim to decompose the provisioning phase. Previously the user/role controller deals directly with provisioning, while now with this proposal both the controller delegates this task to provisioning manager. A first task was to move all provisioning functionality into the provisioning manager. If you now inspect the user/role controller code, you will not find anymore workflow and propagation dependencies. During the development, we thought to make the provisioning pluggable, in order to allow the choice of provisioning engine. The default provisioning engine can be choosed editing the provisioning.properties file. For this reason we hardcoded previous strategies as default provisioning manager, in order to keep the standard Syncope behaviour. As we proposed initially, we wanted also to experiment a provisionig manager based on a Apache Camel. Camel is a powerful integration framework implementing enterprise integration pattern. Our current solution embeds the provisioning logics into camel routes. Moreover the current solution extends also Syncope Console: we added new a new functionality - related to Camel case - that allows to read and edit routes definitions. You can find this new service under the Console-Configuration-Routes section. In this case, routes are expressed through Spring DSL. To finish, I thought to create a github pull request [2],in order to give to Syncope Team members to examine this work and possibly integrate it. [1] http://syncope-dev.1063484.n5.nabble.com/Proposal-An-Apache-Camel-Integratation-Proposal-td5714531.html [2] https://github.com/apache/syncope/pull/2 was: Hi all, last year with the help of Syncope team I proposed an early reformulation of provisioning phase. Provisioning refers to methods used to provide users and roles functionality: the main goal of my proposal was to re-organize this phase, allowing custom provisioning behaviours through a definition of a provisioning manager (see here [1] more details). The current strategy adopted in Syncope makes difficult the definition of custom provisioning behaviour. The solution enclosed with this issue aim to decompose the provisioning phase. Previously the user/role controller deals directly with provisioning, while now with this proposal both the controller delegates this task to provisioning manager. A first task was to move all provisioning functionality into the provisioning manager. If you now inspect the user/role controller code, you will not find anymore workflow and propagation dependencies. During the development, we thought to make the provisioning pluggable, in order to allow the choice of provisioning engine. The default provisioning engine can be choosed editing the provisioning.properties file. For this reason we hardcoded previous strategies as default provisioning manager, in order to keep the standard Syncope behaviour. As we proposed initially, we wanted also to experiment a provisionig manager based on a Apache Camel. Camel is a powerful integration framework implementing enterprise integration pattern. Our current solution embeds the provisioning logics into camel routes. Moreover the current solution extends also Syncope Console: we added new a new functionality - related to Camel case - that allows to read and edit routes definitions. You can find this new service under the Console-Configuration-Routes section. In this case, routes are expressed through Spring DSL. To finish, I thought to create a github pull request [2],in order to give to Syncope Team members to examine this work and possibly integrate it. [1] http://syncope-dev.1063484.n5.nabble.com/Proposal-An-Apache-Camel-Integratation-Proposal-td5714531.html [2] https://github.com/apache/syncope/pull/2 Provisioning manager integration Key: SYNCOPE-623 URL: https://issues.apache.org/jira/browse/SYNCOPE-623 Project: Syncope Issue Type: New Feature Components: common, console, core Reporter: Giacomo Lamonaco Assignee: Giacomo Lamonaco Fix For: 1.3.0 Last year with the help of Syncope team I proposed an early reformulation of
[jira] [Updated] (SYNCOPE-570) Remove usage of deprecated com.thoughtworks.selenium.Selenium
[ https://issues.apache.org/jira/browse/SYNCOPE-570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giacomo Lamonaco updated SYNCOPE-570: - Attachment: (was: issue570.patch) Remove usage of deprecated com.thoughtworks.selenium.Selenium - Key: SYNCOPE-570 URL: https://issues.apache.org/jira/browse/SYNCOPE-570 Project: Syncope Issue Type: Improvement Components: console Affects Versions: 1.2.0 Environment: Selenium integration tests Reporter: Francesco Chicchiriccò Assignee: Giacomo Lamonaco Fix For: 1.2.1, 1.3.0 In recent versions of Selenium, currently used for console integration tests, the com.thoughtworks.selenium.Selenium was deprecated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SYNCOPE-570) Remove usage of deprecated com.thoughtworks.selenium.Selenium
[ https://issues.apache.org/jira/browse/SYNCOPE-570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giacomo Lamonaco updated SYNCOPE-570: - Attachment: (was: issue570.patch) Remove usage of deprecated com.thoughtworks.selenium.Selenium - Key: SYNCOPE-570 URL: https://issues.apache.org/jira/browse/SYNCOPE-570 Project: Syncope Issue Type: Improvement Components: console Affects Versions: 1.2.0 Environment: Selenium integration tests Reporter: Francesco Chicchiriccò Assignee: Giacomo Lamonaco Fix For: 1.2.1, 1.3.0 In recent versions of Selenium, currently used for console integration tests, the com.thoughtworks.selenium.Selenium was deprecated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SYNCOPE-570) Remove usage of deprecated com.thoughtworks.selenium.Selenium
[ https://issues.apache.org/jira/browse/SYNCOPE-570?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giacomo Lamonaco updated SYNCOPE-570: - Attachment: issue570.patch All the selenium tests now support Web Driver API. A patch is attached. Remove usage of deprecated com.thoughtworks.selenium.Selenium - Key: SYNCOPE-570 URL: https://issues.apache.org/jira/browse/SYNCOPE-570 Project: Syncope Issue Type: Improvement Components: console Affects Versions: 1.2.0 Environment: Selenium integration tests Reporter: Francesco Chicchiriccò Assignee: Giacomo Lamonaco Fix For: 1.2.1, 1.3.0 Attachments: issue570.patch In recent versions of Selenium, currently used for console integration tests, the com.thoughtworks.selenium.Selenium was deprecated. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SYNCOPE-554) Class Cast Exception when syncronization task starts
[ https://issues.apache.org/jira/browse/SYNCOPE-554?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14174814#comment-14174814 ] Giacomo Lamonaco commented on SYNCOPE-554: -- Hi! We experienced this problem on a particular LDAP resource, and we've solved disabling Use Blocks option in connector configuration. However, we are investigating it in more detail. Class Cast Exception when syncronization task starts Key: SYNCOPE-554 URL: https://issues.apache.org/jira/browse/SYNCOPE-554 Project: Syncope Issue Type: Bug Affects Versions: 1.2.0-M1 Reporter: Giacomo Lamonaco Create an LDAP connector instance based on ConnID and configure it for an external LDAP resource. Create a new resource based on the LDAP connector. Now create a new syncronization task and try to execute it. In my case, i receive this exception: 09:43:51.655 ERROR org.apache.syncope.core.quartz.AbstractTaskJob - While executing task 188 org.quartz.JobExecutionException: While syncing on connector at org.apache.syncope.core.sync.impl.SyncJob.executeWithSecurityContext(SyncJob.java:186) ~[SyncJob.class:?] at org.apache.syncope.core.sync.impl.SyncJob.executeWithSecurityContext(SyncJob.java:56) ~[SyncJob.class:?] at org.apache.syncope.core.sync.impl.AbstractSyncJob.doExecute(AbstractSyncJob.java:338) ~[AbstractSyncJob.class:?] at org.apache.syncope.core.quartz.AbstractTaskJob.execute(AbstractTaskJob.java:125) ~[AbstractTaskJob.class:?] at org.quartz.core.JobRunShell.run(JobRunShell.java:202) ~[quartz-2.2.1.jar:?] at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:573) ~[quartz-2.2.1.jar:?] Caused by: java.lang.ClassCastException: java.lang.NoClassDefFoundError cannot be cast to org.identityconnectors.framework.common.objects.ConnectorObject at org.identityconnectors.framework.impl.api.StreamHandlerUtil$ObjectStreamHandlerAdapter.handle(StreamHandlerUtil.java:89) ~[connector-framework-internal-1.4.0.0.jar:?] at org.identityconnectors.framework.impl.api.BufferedResultsProxy.invoke(BufferedResultsProxy.java:255) ~[connector-framework-internal-1.4.0.0.jar:?] at org.identityconnectors.framework.impl.api.DelegatingTimeoutProxy.invoke(DelegatingTimeoutProxy.java:94) ~[connector-framework-internal-1.4.0.0.jar:?] at com.sun.proxy.$Proxy213.search(Unknown Source) ~[?:?] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SYNCOPE-567) Security question is not displayed correctly during password reset
[ https://issues.apache.org/jira/browse/SYNCOPE-567?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giacomo Lamonaco updated SYNCOPE-567: - Attachment: issue567.patch It seems that ON_CHANGE event is not fired every time the username textfield loses focus: so i thought to replace it with the ON_BLUR event, that behaves as expected. I enclose a patch. Moreover, when the typed username doesn't exist the security question is cleared . Security question is not displayed correctly during password reset --- Key: SYNCOPE-567 URL: https://issues.apache.org/jira/browse/SYNCOPE-567 Project: Syncope Issue Type: Bug Components: console Affects Versions: 1.2.0 Reporter: Giacomo Lamonaco Fix For: 1.2.1, 1.3.0 Attachments: issue567.patch Login into the syncope console and go under Configuration. Click on Security Questions tab and create a new question. Save your configuration a go under User page. Create a new syncope user: during creation, choose your question and type your answer. Now logout from syncope console and click password reset. The only way of obtain Security question is type the username and press immediately TAB. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SYNCOPE-566) Name attribute value disappears after changing attribute type during schema manipulation
Giacomo Lamonaco created SYNCOPE-566: Summary: Name attribute value disappears after changing attribute type during schema manipulation Key: SYNCOPE-566 URL: https://issues.apache.org/jira/browse/SYNCOPE-566 Project: Syncope Issue Type: Bug Components: console Affects Versions: 1.2.0 Reporter: Giacomo Lamonaco Fix For: 1.2.1, 1.3.0 Login in the Syncope console and select Schema. Create a new schema value, under any tab: fill Name attribute and then try to change its type. As you can see Name value disappears. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (SYNCOPE-566) Name attribute value disappears after changing attribute type during schema manipulation
[ https://issues.apache.org/jira/browse/SYNCOPE-566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giacomo Lamonaco reassigned SYNCOPE-566: Assignee: Giacomo Lamonaco Name attribute value disappears after changing attribute type during schema manipulation Key: SYNCOPE-566 URL: https://issues.apache.org/jira/browse/SYNCOPE-566 Project: Syncope Issue Type: Bug Components: console Affects Versions: 1.2.0 Reporter: Giacomo Lamonaco Assignee: Giacomo Lamonaco Fix For: 1.2.1, 1.3.0 Login in the Syncope console and select Schema. Create a new schema value, under any tab: fill Name attribute and then try to change its type. As you can see Name value disappears. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SYNCOPE-566) Name attribute value disappears after changing attribute type during schema manipulation
[ https://issues.apache.org/jira/browse/SYNCOPE-566?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giacomo Lamonaco updated SYNCOPE-566: - Attachment: issue566.patch It seems that every time an user updates Type value, the whole schema form is refreshed, losing all temporary fields values. To avoid this kind of problem,can be defined a new container that will include all the extra parameters associated with the selected type: when an user select a particular type, the form will be updated only partially, refreshing only this container. Name attribute value disappears after changing attribute type during schema manipulation Key: SYNCOPE-566 URL: https://issues.apache.org/jira/browse/SYNCOPE-566 Project: Syncope Issue Type: Bug Components: console Affects Versions: 1.2.0 Reporter: Giacomo Lamonaco Assignee: Giacomo Lamonaco Fix For: 1.2.1, 1.3.0 Attachments: issue566.patch Login in the Syncope console and select Schema. Create a new schema value, under any tab: fill Name attribute and then try to change its type. As you can see Name value disappears. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SYNCOPE-567) Security question is not displayed correctly during password reset
Giacomo Lamonaco created SYNCOPE-567: Summary: Security question is not displayed correctly during password reset Key: SYNCOPE-567 URL: https://issues.apache.org/jira/browse/SYNCOPE-567 Project: Syncope Issue Type: Bug Components: console Affects Versions: 1.2.0 Reporter: Giacomo Lamonaco Fix For: 1.2.1, 1.3.0 Login into the syncope console and go under Configuration. Click on Security Questions tab and create a new question. Save your configuration a go under User page. Create a new syncope user: during creation, choose your question and type your answer. Now logout from syncope console and click password reset. The only way of obtain Security question is type the username and press immediately TAB. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Assigned] (SYNCOPE-565) Error on ResourceModalPage when override a SpinnerField in the ConnectorModalPage
[ https://issues.apache.org/jira/browse/SYNCOPE-565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giacomo Lamonaco reassigned SYNCOPE-565: Assignee: Giacomo Lamonaco Error on ResourceModalPage when override a SpinnerField in the ConnectorModalPage - Key: SYNCOPE-565 URL: https://issues.apache.org/jira/browse/SYNCOPE-565 Project: Syncope Issue Type: Bug Components: console Affects Versions: 1.2.0 Reporter: Marco Di Sabatino Di Diodoro Assignee: Giacomo Lamonaco Fix For: 1.2.1, 1.3.0 Class cast exception on ResourceModalPage when override a SpinnerField in the ConnectorModalPage. java.lang.ClassCastException: Cannot cast java.lang.Double to int at java.lang.Class.cast(Class.java:3005) at org.apache.syncope.console.wicket.markup.html.form.SpinnerFieldPanel$2.getObject(SpinnerFieldPanel.java:109) at org.apache.syncope.console.wicket.markup.html.form.SpinnerFieldPanel$2.getObject(SpinnerFieldPanel.java:100) at org.apache.wicket.Component.getDefaultModelObject(Component.java:1590) at org.apache.wicket.Component.getDefaultModelObjectAsString(Component.java:1618) at org.apache.wicket.markup.html.form.FormComponent.getModelValue(FormComponent.java:1291) at org.apache.wicket.markup.html.form.FormComponent.getValue(FormComponent.java:878) at org.apache.wicket.markup.html.form.TextField.onComponentTag(TextField.java:108) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SYNCOPE-565) Error on ResourceModalPage when override a SpinnerField in the ConnectorModalPage
[ https://issues.apache.org/jira/browse/SYNCOPE-565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giacomo Lamonaco updated SYNCOPE-565: - Attachment: issue565.patch It seems that ResourceConnConfPanel class is instantiated with int.class parameter instead of Integer.class : during the cast operation in the SpinnerFieldPanel class there isn't a check for this type, so it cast with the default value (Double). In this case, working with primitive types can lead to problems. A solution can be represented by forcing the ResourceConnConfPanel to use Integer.class, instead using Number class. I attach a patch. Error on ResourceModalPage when override a SpinnerField in the ConnectorModalPage - Key: SYNCOPE-565 URL: https://issues.apache.org/jira/browse/SYNCOPE-565 Project: Syncope Issue Type: Bug Components: console Affects Versions: 1.2.0 Reporter: Marco Di Sabatino Di Diodoro Assignee: Giacomo Lamonaco Fix For: 1.2.1, 1.3.0 Attachments: issue565.patch Class cast exception on ResourceModalPage when override a SpinnerField in the ConnectorModalPage. java.lang.ClassCastException: Cannot cast java.lang.Double to int at java.lang.Class.cast(Class.java:3005) at org.apache.syncope.console.wicket.markup.html.form.SpinnerFieldPanel$2.getObject(SpinnerFieldPanel.java:109) at org.apache.syncope.console.wicket.markup.html.form.SpinnerFieldPanel$2.getObject(SpinnerFieldPanel.java:100) at org.apache.wicket.Component.getDefaultModelObject(Component.java:1590) at org.apache.wicket.Component.getDefaultModelObjectAsString(Component.java:1618) at org.apache.wicket.markup.html.form.FormComponent.getModelValue(FormComponent.java:1291) at org.apache.wicket.markup.html.form.FormComponent.getValue(FormComponent.java:878) at org.apache.wicket.markup.html.form.TextField.onComponentTag(TextField.java:108) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SYNCOPE-565) Error on ResourceModalPage when override a SpinnerField in the ConnectorModalPage
[ https://issues.apache.org/jira/browse/SYNCOPE-565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giacomo Lamonaco updated SYNCOPE-565: - Attachment: (was: issue565.patch) Error on ResourceModalPage when override a SpinnerField in the ConnectorModalPage - Key: SYNCOPE-565 URL: https://issues.apache.org/jira/browse/SYNCOPE-565 Project: Syncope Issue Type: Bug Components: console Affects Versions: 1.2.0 Reporter: Marco Di Sabatino Di Diodoro Assignee: Giacomo Lamonaco Fix For: 1.2.1, 1.3.0 Class cast exception on ResourceModalPage when override a SpinnerField in the ConnectorModalPage. java.lang.ClassCastException: Cannot cast java.lang.Double to int at java.lang.Class.cast(Class.java:3005) at org.apache.syncope.console.wicket.markup.html.form.SpinnerFieldPanel$2.getObject(SpinnerFieldPanel.java:109) at org.apache.syncope.console.wicket.markup.html.form.SpinnerFieldPanel$2.getObject(SpinnerFieldPanel.java:100) at org.apache.wicket.Component.getDefaultModelObject(Component.java:1590) at org.apache.wicket.Component.getDefaultModelObjectAsString(Component.java:1618) at org.apache.wicket.markup.html.form.FormComponent.getModelValue(FormComponent.java:1291) at org.apache.wicket.markup.html.form.FormComponent.getValue(FormComponent.java:878) at org.apache.wicket.markup.html.form.TextField.onComponentTag(TextField.java:108) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SYNCOPE-565) Error on ResourceModalPage when override a SpinnerField in the ConnectorModalPage
[ https://issues.apache.org/jira/browse/SYNCOPE-565?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giacomo Lamonaco updated SYNCOPE-565: - Attachment: issue565.patch As suggested by [~ilgrosso], i edited my patch in in order to maintain the right level of abstraction. For this reason, i used a particular Spring class, called ClassUtils, that allows to convert primitive type into the corresponding primitive wrapper type, if necessary. I update my patch. Error on ResourceModalPage when override a SpinnerField in the ConnectorModalPage - Key: SYNCOPE-565 URL: https://issues.apache.org/jira/browse/SYNCOPE-565 Project: Syncope Issue Type: Bug Components: console Affects Versions: 1.2.0 Reporter: Marco Di Sabatino Di Diodoro Assignee: Giacomo Lamonaco Fix For: 1.2.1, 1.3.0 Attachments: issue565.patch Class cast exception on ResourceModalPage when override a SpinnerField in the ConnectorModalPage. java.lang.ClassCastException: Cannot cast java.lang.Double to int at java.lang.Class.cast(Class.java:3005) at org.apache.syncope.console.wicket.markup.html.form.SpinnerFieldPanel$2.getObject(SpinnerFieldPanel.java:109) at org.apache.syncope.console.wicket.markup.html.form.SpinnerFieldPanel$2.getObject(SpinnerFieldPanel.java:100) at org.apache.wicket.Component.getDefaultModelObject(Component.java:1590) at org.apache.wicket.Component.getDefaultModelObjectAsString(Component.java:1618) at org.apache.wicket.markup.html.form.FormComponent.getModelValue(FormComponent.java:1291) at org.apache.wicket.markup.html.form.FormComponent.getValue(FormComponent.java:878) at org.apache.wicket.markup.html.form.TextField.onComponentTag(TextField.java:108) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SYNCOPE-561) HTML reports are not displayed correctly if resources miss
Giacomo Lamonaco created SYNCOPE-561: Summary: HTML reports are not displayed correctly if resources miss Key: SYNCOPE-561 URL: https://issues.apache.org/jira/browse/SYNCOPE-561 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.2.0 Reporter: Giacomo Lamonaco Assignee: Giacomo Lamonaco Priority: Minor Fix For: 1.2.1, 1.3.0 Open syncope console and go under reports. Create a new report, containing a User portlet. In the configuration tab, set your favourite matching condition and add your attributes, leaving all the rest untouched. Now save your configurations and try to execute this report. After the execution, export your report in HTML format. You can see that the report is not displayed correctly, due the fact that subsequent users are included into the previous. It seems that some closing tags are missing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SYNCOPE-561) HTML reports are not displayed correctly if resources miss
[ https://issues.apache.org/jira/browse/SYNCOPE-561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giacomo Lamonaco updated SYNCOPE-561: - Attachment: issue561.patch It seems that userReportlet2html.xsl file needs to check if user resources exist, before including them in the ul: after adding this condition, the report is displayed correctly. I attach the patch. HTML reports are not displayed correctly if resources miss -- Key: SYNCOPE-561 URL: https://issues.apache.org/jira/browse/SYNCOPE-561 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.2.0 Reporter: Giacomo Lamonaco Assignee: Giacomo Lamonaco Priority: Minor Fix For: 1.2.1, 1.3.0 Attachments: issue561.patch Open syncope console and go under reports. Create a new report, containing a User portlet. In the configuration tab, set your favourite matching condition and add your attributes, leaving all the rest untouched. Now save your configurations and try to execute this report. After the execution, export your report in HTML format. You can see that the report is not displayed correctly, due the fact that subsequent users are included into the previous. It seems that some closing tags are missing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SYNCOPE-561) HTML reports are not displayed correctly if resources miss
[ https://issues.apache.org/jira/browse/SYNCOPE-561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giacomo Lamonaco updated SYNCOPE-561: - Attachment: (was: issue561.patch) HTML reports are not displayed correctly if resources miss -- Key: SYNCOPE-561 URL: https://issues.apache.org/jira/browse/SYNCOPE-561 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.2.0 Reporter: Giacomo Lamonaco Assignee: Giacomo Lamonaco Priority: Minor Fix For: 1.2.1, 1.3.0 Open syncope console and go under reports. Create a new report, containing a User portlet. In the configuration tab, set your favourite matching condition and add your attributes, leaving all the rest untouched. Now save your configurations and try to execute this report. After the execution, export your report in HTML format. You can see that the report is not displayed correctly, due the fact that subsequent users are included into the previous. It seems that some closing tags are missing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SYNCOPE-561) HTML reports are not displayed correctly if resources miss
[ https://issues.apache.org/jira/browse/SYNCOPE-561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giacomo Lamonaco updated SYNCOPE-561: - Attachment: issue561.patch Updating patch with a more efficient one HTML reports are not displayed correctly if resources miss -- Key: SYNCOPE-561 URL: https://issues.apache.org/jira/browse/SYNCOPE-561 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.2.0 Reporter: Giacomo Lamonaco Assignee: Giacomo Lamonaco Priority: Minor Fix For: 1.2.1, 1.3.0 Attachments: issue561.patch Open syncope console and go under reports. Create a new report, containing a User portlet. In the configuration tab, set your favourite matching condition and add your attributes, leaving all the rest untouched. Now save your configurations and try to execute this report. After the execution, export your report in HTML format. You can see that the report is not displayed correctly, due the fact that subsequent users are included into the previous. It seems that some closing tags are missing. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SYNCOPE-554) Class Cast Exception when syncronization task starts
Giacomo Lamonaco created SYNCOPE-554: Summary: Class Cast Exception when syncronization task starts Key: SYNCOPE-554 URL: https://issues.apache.org/jira/browse/SYNCOPE-554 Project: Syncope Issue Type: Bug Affects Versions: 1.2.0-M1 Reporter: Giacomo Lamonaco Fix For: 1.2.0, 1.3.0 Create an LDAP connector instance based on ConnID and configure it for an external LDAP resource. Create a new resource based on the LDAP connector. Now create a new syncronization task and try to execute it. In my case, i receive this exception: 09:43:51.655 ERROR org.apache.syncope.core.quartz.AbstractTaskJob - While executing task 188 org.quartz.JobExecutionException: While syncing on connector at org.apache.syncope.core.sync.impl.SyncJob.executeWithSecurityContext(SyncJob.java:186) ~[SyncJob.class:?] at org.apache.syncope.core.sync.impl.SyncJob.executeWithSecurityContext(SyncJob.java:56) ~[SyncJob.class:?] at org.apache.syncope.core.sync.impl.AbstractSyncJob.doExecute(AbstractSyncJob.java:338) ~[AbstractSyncJob.class:?] at org.apache.syncope.core.quartz.AbstractTaskJob.execute(AbstractTaskJob.java:125) ~[AbstractTaskJob.class:?] at org.quartz.core.JobRunShell.run(JobRunShell.java:202) ~[quartz-2.2.1.jar:?] at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:573) ~[quartz-2.2.1.jar:?] Caused by: java.lang.ClassCastException: java.lang.NoClassDefFoundError cannot be cast to org.identityconnectors.framework.common.objects.ConnectorObject at org.identityconnectors.framework.impl.api.StreamHandlerUtil$ObjectStreamHandlerAdapter.handle(StreamHandlerUtil.java:89) ~[connector-framework-internal-1.4.0.0.jar:?] at org.identityconnectors.framework.impl.api.BufferedResultsProxy.invoke(BufferedResultsProxy.java:255) ~[connector-framework-internal-1.4.0.0.jar:?] at org.identityconnectors.framework.impl.api.DelegatingTimeoutProxy.invoke(DelegatingTimeoutProxy.java:94) ~[connector-framework-internal-1.4.0.0.jar:?] at com.sun.proxy.$Proxy213.search(Unknown Source) ~[?:?] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SYNCOPE-554) Class Cast Exception when syncronization task starts
[ https://issues.apache.org/jira/browse/SYNCOPE-554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giacomo Lamonaco updated SYNCOPE-554: - Fix Version/s: (was: 1.2.0) (was: 1.3.0) Class Cast Exception when syncronization task starts Key: SYNCOPE-554 URL: https://issues.apache.org/jira/browse/SYNCOPE-554 Project: Syncope Issue Type: Bug Affects Versions: 1.2.0-M1 Reporter: Giacomo Lamonaco Create an LDAP connector instance based on ConnID and configure it for an external LDAP resource. Create a new resource based on the LDAP connector. Now create a new syncronization task and try to execute it. In my case, i receive this exception: 09:43:51.655 ERROR org.apache.syncope.core.quartz.AbstractTaskJob - While executing task 188 org.quartz.JobExecutionException: While syncing on connector at org.apache.syncope.core.sync.impl.SyncJob.executeWithSecurityContext(SyncJob.java:186) ~[SyncJob.class:?] at org.apache.syncope.core.sync.impl.SyncJob.executeWithSecurityContext(SyncJob.java:56) ~[SyncJob.class:?] at org.apache.syncope.core.sync.impl.AbstractSyncJob.doExecute(AbstractSyncJob.java:338) ~[AbstractSyncJob.class:?] at org.apache.syncope.core.quartz.AbstractTaskJob.execute(AbstractTaskJob.java:125) ~[AbstractTaskJob.class:?] at org.quartz.core.JobRunShell.run(JobRunShell.java:202) ~[quartz-2.2.1.jar:?] at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:573) ~[quartz-2.2.1.jar:?] Caused by: java.lang.ClassCastException: java.lang.NoClassDefFoundError cannot be cast to org.identityconnectors.framework.common.objects.ConnectorObject at org.identityconnectors.framework.impl.api.StreamHandlerUtil$ObjectStreamHandlerAdapter.handle(StreamHandlerUtil.java:89) ~[connector-framework-internal-1.4.0.0.jar:?] at org.identityconnectors.framework.impl.api.BufferedResultsProxy.invoke(BufferedResultsProxy.java:255) ~[connector-framework-internal-1.4.0.0.jar:?] at org.identityconnectors.framework.impl.api.DelegatingTimeoutProxy.invoke(DelegatingTimeoutProxy.java:94) ~[connector-framework-internal-1.4.0.0.jar:?] at com.sun.proxy.$Proxy213.search(Unknown Source) ~[?:?] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (SYNCOPE-554) Class Cast Exception when syncronization task starts
[ https://issues.apache.org/jira/browse/SYNCOPE-554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giacomo Lamonaco closed SYNCOPE-554. Resolution: Invalid Class Cast Exception when syncronization task starts Key: SYNCOPE-554 URL: https://issues.apache.org/jira/browse/SYNCOPE-554 Project: Syncope Issue Type: Bug Affects Versions: 1.2.0-M1 Reporter: Giacomo Lamonaco Create an LDAP connector instance based on ConnID and configure it for an external LDAP resource. Create a new resource based on the LDAP connector. Now create a new syncronization task and try to execute it. In my case, i receive this exception: 09:43:51.655 ERROR org.apache.syncope.core.quartz.AbstractTaskJob - While executing task 188 org.quartz.JobExecutionException: While syncing on connector at org.apache.syncope.core.sync.impl.SyncJob.executeWithSecurityContext(SyncJob.java:186) ~[SyncJob.class:?] at org.apache.syncope.core.sync.impl.SyncJob.executeWithSecurityContext(SyncJob.java:56) ~[SyncJob.class:?] at org.apache.syncope.core.sync.impl.AbstractSyncJob.doExecute(AbstractSyncJob.java:338) ~[AbstractSyncJob.class:?] at org.apache.syncope.core.quartz.AbstractTaskJob.execute(AbstractTaskJob.java:125) ~[AbstractTaskJob.class:?] at org.quartz.core.JobRunShell.run(JobRunShell.java:202) ~[quartz-2.2.1.jar:?] at org.quartz.simpl.SimpleThreadPool$WorkerThread.run(SimpleThreadPool.java:573) ~[quartz-2.2.1.jar:?] Caused by: java.lang.ClassCastException: java.lang.NoClassDefFoundError cannot be cast to org.identityconnectors.framework.common.objects.ConnectorObject at org.identityconnectors.framework.impl.api.StreamHandlerUtil$ObjectStreamHandlerAdapter.handle(StreamHandlerUtil.java:89) ~[connector-framework-internal-1.4.0.0.jar:?] at org.identityconnectors.framework.impl.api.BufferedResultsProxy.invoke(BufferedResultsProxy.java:255) ~[connector-framework-internal-1.4.0.0.jar:?] at org.identityconnectors.framework.impl.api.DelegatingTimeoutProxy.invoke(DelegatingTimeoutProxy.java:94) ~[connector-framework-internal-1.4.0.0.jar:?] at com.sun.proxy.$Proxy213.search(Unknown Source) ~[?:?] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SYNCOPE-482) Updating workflow definition throught console XML editor doesn't really update
Giacomo Lamonaco created SYNCOPE-482: Summary: Updating workflow definition throught console XML editor doesn't really update Key: SYNCOPE-482 URL: https://issues.apache.org/jira/browse/SYNCOPE-482 Project: Syncope Issue Type: Bug Components: console Affects Versions: 1.2.0 Reporter: Giacomo Lamonaco Assignee: Giacomo Lamonaco Fix For: 1.2.0 Open Configuration and select Workflow tab. Open the XML editor, write something in the text area and save the modifications. Now re-open the xml editor: your changes doesn't appear because they aren't applied to workflow. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (SYNCOPE-482) Updating workflow definition throught console XML editor doesn't really update
[ https://issues.apache.org/jira/browse/SYNCOPE-482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giacomo Lamonaco updated SYNCOPE-482: - Attachment: SYNCOPE-482.patch Updating workflow definition throught console XML editor doesn't really update -- Key: SYNCOPE-482 URL: https://issues.apache.org/jira/browse/SYNCOPE-482 Project: Syncope Issue Type: Bug Components: console Affects Versions: 1.2.0 Reporter: Giacomo Lamonaco Assignee: Giacomo Lamonaco Fix For: 1.2.0 Attachments: SYNCOPE-482.patch, SYNCOPE-482.patch Open Configuration and select Workflow tab. Open the XML editor, write something in the text area and save the modifications. Now re-open the xml editor: your changes doesn't appear because they aren't applied to workflow. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
[jira] [Updated] (SYNCOPE-482) Updating workflow definition throught console XML editor doesn't really update
[ https://issues.apache.org/jira/browse/SYNCOPE-482?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Giacomo Lamonaco updated SYNCOPE-482: - Attachment: (was: SYNCOPE-482.patch) Updating workflow definition throught console XML editor doesn't really update -- Key: SYNCOPE-482 URL: https://issues.apache.org/jira/browse/SYNCOPE-482 Project: Syncope Issue Type: Bug Components: console Affects Versions: 1.2.0 Reporter: Giacomo Lamonaco Assignee: Giacomo Lamonaco Fix For: 1.2.0 Attachments: SYNCOPE-482.patch Open Configuration and select Workflow tab. Open the XML editor, write something in the text area and save the modifications. Now re-open the xml editor: your changes doesn't appear because they aren't applied to workflow. -- This message was sent by Atlassian JIRA (v6.1.5#6160)
