[jira] [Closed] (SYNCOPE-310) Palette elements get translated
[ https://issues.apache.org/jira/browse/SYNCOPE-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimiliano Perrone closed SYNCOPE-310. Release 1.0.6 Palette elements get translated --- Key: SYNCOPE-310 URL: https://issues.apache.org/jira/browse/SYNCOPE-310 Project: Syncope Issue Type: Bug Components: console Affects Versions: 1.0.5, 1.1.0 Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Fix For: 1.0.6, 1.1.0 Options shown in Wicket's palette are treated as label and searched for available translations. For example, the 'title' role schema is rendered as Policy Management (i.e. the modal window title) when managing synchronization policies. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (SYNCOPE-309) Enter key not bound to user form submit
[ https://issues.apache.org/jira/browse/SYNCOPE-309?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimiliano Perrone closed SYNCOPE-309. Release 1.0.6 Enter key not bound to user form submit --- Key: SYNCOPE-309 URL: https://issues.apache.org/jira/browse/SYNCOPE-309 Project: Syncope Issue Type: Bug Components: console Affects Versions: 1.0.5, 1.1.0 Environment: Google Chrome Reporter: Francesco Chicchiriccò Assignee: fabio martelli Priority: Minor Fix For: 1.0.6, 1.1.0 When editing an user from the admin console, if entering an attribute value and hitting 'enter', a derived attribute is added. Since this happens in another tab, when clicking on Save to submit the form, an error is reported 'Schema' is required. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (SYNCOPE-301) Status is not updated when synchronizing existing users
[ https://issues.apache.org/jira/browse/SYNCOPE-301?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimiliano Perrone closed SYNCOPE-301. Release 1.0.6 Status is not updated when synchronizing existing users --- Key: SYNCOPE-301 URL: https://issues.apache.org/jira/browse/SYNCOPE-301 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.0.5, 1.1.0 Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Fix For: 1.0.6, 1.1.0 Even though the flag Synchronize user status is checked on the SyncTask, the status (enabled / disabled) on the synchronizing external resources does not make any suspend() / reactivate() to take place on Syncope, for existing users. For non-existing users, however, everything is working as expected. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (SYNCOPE-294) User data not refreshed before edit
[ https://issues.apache.org/jira/browse/SYNCOPE-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimiliano Perrone closed SYNCOPE-294. Release 1.0.6 User data not refreshed before edit --- Key: SYNCOPE-294 URL: https://issues.apache.org/jira/browse/SYNCOPE-294 Project: Syncope Issue Type: Bug Components: console Affects Versions: 1.0.5 Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Priority: Minor Fix For: 1.0.6, 1.1.0 As reported in ML [1] the user data are not refreshed before loading into edit modal page. Does the same apply to other entities, mainly roles? [1] http://syncope-dev.1063484.n5.nabble.com/Console-update-issue-tt5712329.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (SYNCOPE-311) View user details during approval
[ https://issues.apache.org/jira/browse/SYNCOPE-311?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimiliano Perrone closed SYNCOPE-311. Release 1.0.6 View user details during approval - Key: SYNCOPE-311 URL: https://issues.apache.org/jira/browse/SYNCOPE-311 Project: Syncope Issue Type: Improvement Components: console Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Fix For: 1.0.6, 1.1.0 Currently there is no possibility for admins to take a look at (if allowed) details of user under approval. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (SYNCOPE-299) Add row to display selector in resources
[ https://issues.apache.org/jira/browse/SYNCOPE-299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimiliano Perrone closed SYNCOPE-299. Release 1.0.6 Add row to display selector in resources -- Key: SYNCOPE-299 URL: https://issues.apache.org/jira/browse/SYNCOPE-299 Project: Syncope Issue Type: Improvement Components: console Affects Versions: 1.0.5 Reporter: Denis Signoretto Assignee: Colm O hEigeartaigh Priority: Minor Fix For: 1.0.6, 1.1.0 Allow resources list to display more than 10 resources per page (add the Rows to display pager) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (SYNCOPE-325) Stacktrace when accessing the Configuration page on JBoss
[ https://issues.apache.org/jira/browse/SYNCOPE-325?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimiliano Perrone closed SYNCOPE-325. Release 1.0.6 Stacktrace when accessing the Configuration page on JBoss - Key: SYNCOPE-325 URL: https://issues.apache.org/jira/browse/SYNCOPE-325 Project: Syncope Issue Type: Bug Components: console Affects Versions: 1.0.5, 1.1.0 Environment: JBoss AS 7.1.1 Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Fix For: 1.0.6, 1.1.0 When deploying to JBoss AS 7.1.1 and accessing the Configuration page on the admin console, a stacktrace is given. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (SYNCOPE-307) Virtual Attributes don't propagated in case of update during synchronization
[ https://issues.apache.org/jira/browse/SYNCOPE-307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimiliano Perrone closed SYNCOPE-307. Release 1.0.6 Virtual Attributes don't propagated in case of update during synchronization Key: SYNCOPE-307 URL: https://issues.apache.org/jira/browse/SYNCOPE-307 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.0.6, 1.1.0 Reporter: fabio martelli Assignee: fabio martelli Fix For: 1.0.6, 1.1.0 UC: * Suppose two resources A and B; * Suppose to synchronize from A; * Suppose to have virtual attributes mapped just on B; * Suppose to retrieve a user to be updated locally and to be created new on B (thanks to an ad-hoc user template). User will be updated locally and created on B but its virtual attribute values won't be propagated on B. The bug is into the virtual attribute management during sync and propagation: in the UC provided above, the 'populate' method of the class AttributableOperations will never provide virtual attributes to be used by SyncJob to create the update propagation task. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (SYNCOPE-308) When trying to update an user in status 'rejected', an error 500 is returned
[ https://issues.apache.org/jira/browse/SYNCOPE-308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Massimiliano Perrone closed SYNCOPE-308. Release 1.0.6 When trying to update an user in status 'rejected', an error 500 is returned Key: SYNCOPE-308 URL: https://issues.apache.org/jira/browse/SYNCOPE-308 Project: Syncope Issue Type: Bug Components: core Affects Versions: 1.0.5, 1.1.0 Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Fix For: 1.0.6, 1.1.0 This happens with the default workflow definition. How to reproduce from the admin console: 1. as admin, create an user with role 9 2. under TODO, claim approval 3. reject 4. try to edit such user under Users The problem here is that 500 is returned; the expected result is instead that the response is delegated to the underlying workflow definition. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Syncope-1_0_X - Build # 154 - Failure
The Apache Jenkins build system has built Syncope-1_0_X (build #154) Status: Failure Check console output at https://builds.apache.org/job/Syncope-1_0_X/154/ to view the results.
Re: BasicAuth realm String
Hi On 27/02/13 07:49, Francesco Chicchiriccò wrote: On 26/02/2013 23:03, Colm O hEigeartaigh wrote: Hi all, The core's RestServiceExceptionMapper defines the following: private static final String BASIC_REALM_UNAUTHORIZED = Basic realm=\Spring Security Application\; I propose to change this to a more neutral realm, as this appears when authenticating to access the new CXF-based REST API as well. +1 Any objections or suggestions? What about Apache Syncope authentication? I guess using the name of the framework might be problematic when using Syncope within some custom deployments; I'd vote for getting the realm name customized via a property, and defaulted to a more neutral name as suggested (say Identity Provision or Management, etc) or may be just omitted during the challenge by default, Thanks, Sergey Regards.
[jira] [Commented] (SYNCOPE-324) Return User instead of Boolean from REST username + password query
[
https://issues.apache.org/jira/browse/SYNCOPE-324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13588224#comment-13588224
]
Jan Bernhardt commented on SYNCOPE-324:
---
+1 Sounds like a real good idea.
I'll update Test-Cases and Console and see, if we run into any issues with
Francescos approach.
Return User instead of Boolean from REST username + password query
--
Key: SYNCOPE-324
URL: https://issues.apache.org/jira/browse/SYNCOPE-324
Project: Syncope
Issue Type: Improvement
Reporter: Colm O hEigeartaigh
Fix For: 1.1.0
The REST API GET /users?username={username}pwd={password} currently returns
a boolean. This task is to return the User instead, as per the mailing list
discussion here:
http://syncope-dev.1063484.n5.nabble.com/API-query-td5712965.html
If authentication is successful we should return 200 OK, if authentication
fails we should return 404 NOT FOUND.
Caching should be disabled for this URL.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (SYNCOPE-324) Return User instead of Boolean from REST username + password query
[
https://issues.apache.org/jira/browse/SYNCOPE-324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Bernhardt updated SYNCOPE-324:
--
Assignee: Jan Bernhardt
Return User instead of Boolean from REST username + password query
--
Key: SYNCOPE-324
URL: https://issues.apache.org/jira/browse/SYNCOPE-324
Project: Syncope
Issue Type: Improvement
Reporter: Colm O hEigeartaigh
Assignee: Jan Bernhardt
Fix For: 1.1.0
The REST API GET /users?username={username}pwd={password} currently returns
a boolean. This task is to return the User instead, as per the mailing list
discussion here:
http://syncope-dev.1063484.n5.nabble.com/API-query-td5712965.html
If authentication is successful we should return 200 OK, if authentication
fails we should return 404 NOT FOUND.
Caching should be disabled for this URL.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Reopened] (SYNCOPE-312) Introducing UserWorkflowService
[ https://issues.apache.org/jira/browse/SYNCOPE-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jan Bernhardt reopened SYNCOPE-312: --- Documentation needs to be updated: https://cwiki.apache.org/confluence/display/SYNCOPE/REST+API+upgrade Introducing UserWorkflowService --- Key: SYNCOPE-312 URL: https://issues.apache.org/jira/browse/SYNCOPE-312 Project: Syncope Issue Type: Bug Components: common Reporter: Jan Bernhardt Assignee: Christian Schneider Priority: Minor Labels: refactoring Fix For: 1.1.0 As agreed on dev mailinglist [1] task of this Issue is to create a UserWorkflowService Interface and move workflow related methods from UserService to UserWorkflowService. [1] http://syncope-dev.1063484.n5.nabble.com/DISCUSS-User-Service-td5712640.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (SYNCOPE-324) Return User instead of Boolean from REST username + password query
[
https://issues.apache.org/jira/browse/SYNCOPE-324?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jan Bernhardt resolved SYNCOPE-324.
---
Resolution: Fixed
Code Documentation updated.
Code in Console will be updated in 1.2.x release, after switching to CXF
Return User instead of Boolean from REST username + password query
--
Key: SYNCOPE-324
URL: https://issues.apache.org/jira/browse/SYNCOPE-324
Project: Syncope
Issue Type: Improvement
Reporter: Colm O hEigeartaigh
Assignee: Jan Bernhardt
Fix For: 1.1.0
The REST API GET /users?username={username}pwd={password} currently returns
a boolean. This task is to return the User instead, as per the mailing list
discussion here:
http://syncope-dev.1063484.n5.nabble.com/API-query-td5712965.html
If authentication is successful we should return 200 OK, if authentication
fails we should return 404 NOT FOUND.
Caching should be disabled for this URL.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Resolved] (SYNCOPE-312) Introducing UserWorkflowService
[ https://issues.apache.org/jira/browse/SYNCOPE-312?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schneider resolved SYNCOPE-312. - Resolution: Fixed Documentation should now reflect the UserWorkflowService Introducing UserWorkflowService --- Key: SYNCOPE-312 URL: https://issues.apache.org/jira/browse/SYNCOPE-312 Project: Syncope Issue Type: Bug Components: common Reporter: Jan Bernhardt Assignee: Christian Schneider Priority: Minor Labels: refactoring Fix For: 1.1.0 As agreed on dev mailinglist [1] task of this Issue is to create a UserWorkflowService Interface and move workflow related methods from UserService to UserWorkflowService. [1] http://syncope-dev.1063484.n5.nabble.com/DISCUSS-User-Service-td5712640.html -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[VOTE] Apache Syncope 1.0.6
Hi All, I've created a 1.0.6 release, with the following artifacts up for a vote: SVN source tag (r1450752): https://svn.apache.org/repos/asf/syncope/tags/syncope-1.0.6/ List of changes: https://svn.apache.org/repos/asf/syncope/tags/syncope-1.0.6/CHANGES Maven staging repo: https://repository.apache.org/content/repositories/orgapachesyncope-310/ Source release (checksums and signatures are available at the same location): https://repository.apache.org/content/repositories/orgapachesyncope-310/org/apache/syncope/syncope-root/1.0.6/syncope-root-1.0.6-source-release.zip Staging site: http://syncope.apache.org/1.0.6/ PGP release keys (signed using C481E45C): http://www.apache.org/dist/syncope/KEYS Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why)
[DISCUSS] Apache Syncope 1.0.6
Discussion thread for vote on 1.0.6 release, with SVN source tag (r1450752). For more information on the release process, check outhttp://www.apache.org/dev/release.html Some of the things to check before voting are: - does mvn apache-rat:check pass on the source - can you build the contents of source release zip and SVN tag - do all of the staged jars/wars/zips contain the required LICENSE and NOTICE files - are all of the staged jars/wars/zips signed and the signature verifiable - is the signing key in the project's KEYS file and on a public server (i.e.http://www.apache.org/dist/syncope/) -- Massimiliano Perrone Tel +39 393 9121310 Tirasa S.r.l. Viale D'Annunzio 267 - 65127 Pescara Tel +39 0859116307 / FAX +39 085973 http://www.tirasa.net Apache Syncope PMC Member http://people.apache.org/~massi/ L'apprendere molte cose non insegna l'intelligenza (Eraclito)
Re: Tomcat error message
Hi Francesco, how went your presentation at ApacheCon about Syncope an CXF? We are curious here... My talk went well (I hope!). I will put the slides online shortly. Essentially my talk gave a introduction to Syncope, a demo where Syncope was deployed in Tomcat with internal storage persisted to MySQL, with users synced in from an Apache Derby instance, and users + roles from an Apache DS instance. I talked about the forthcoming 1.1 release, the new REST API, and the switch to use CXF, as well as the possibilities that may offer us in the future. The feedback seemed reasonably positive, so hopefully it might drive a few more people to the project. Anyway, what you report above is the same of Jesse Van Bekkum's message in user ML [1]. I will try to spend some time today for investigating about this. Thanks! Colm. On Tue, Feb 26, 2013 at 11:46 PM, Francesco Chicchiriccò ilgro...@apache.org wrote: On 26/02/2013 22:54, Colm O hEigeartaigh wrote: Hi all, I'm seeing the following error message in the Tomcat logs when stopping Syncope (1.1.0): SEVERE: The web application [/syncope] appears to have started a thread named [Abandoned connection cleanup thread] but has failed to stop it. This is very likely to create a memory leak. Any ideas? Hi Colm, how went your presentation at ApacheCon about Syncope an CXF? We are curious here... Anyway, what you report above is the same of Jesse Van Bekkum's message in user ML [1]. I will try to spend some time today for investigating about this. Regards. [1] http://markmail.org/message/**3rznykqdwsuh6nhchttp://markmail.org/message/3rznykqdwsuh6nhc -- Francesco Chicchiriccò ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member http://people.apache.org/~**ilgrosso/http://people.apache.org/~ilgrosso/ -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
Re: BasicAuth realm String
Hi Sergey, I guess using the name of the framework might be problematic when using Syncope within some custom deployments; I'd vote for getting the realm name customized via a property, and defaulted to a more neutral name as suggested (say Identity Provision or Management, etc) or may be just omitted during the challenge by default, I will just change it to Apache Syncope authentication for now. The ability to make it customisable via a property seems reasonable, could log a JIRA for it? Colm. On Wed, Feb 27, 2013 at 2:14 AM, Sergey Beryozkin sberyoz...@gmail.comwrote: Hi On 27/02/13 07:49, Francesco Chicchiriccň wrote: On 26/02/2013 23:03, Colm O hEigeartaigh wrote: Hi all, The core's RestServiceExceptionMapper defines the following: private static final String BASIC_REALM_UNAUTHORIZED = Basic realm=\Spring Security Application\; I propose to change this to a more neutral realm, as this appears when authenticating to access the new CXF-based REST API as well. +1 Any objections or suggestions? What about Apache Syncope authentication? I guess using the name of the framework might be problematic when using Syncope within some custom deployments; I'd vote for getting the realm name customized via a property, and defaulted to a more neutral name as suggested (say Identity Provision or Management, etc) or may be just omitted during the challenge by default, Thanks, Sergey Regards. -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
[jira] [Resolved] (SYNCOPE-318) No way to see Connector help message for multi-valued property
[ https://issues.apache.org/jira/browse/SYNCOPE-318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] fabio martelli resolved SYNCOPE-318. Resolution: Fixed No way to see Connector help message for multi-valued property -- Key: SYNCOPE-318 URL: https://issues.apache.org/jira/browse/SYNCOPE-318 Project: Syncope Issue Type: Bug Components: console Reporter: Colm O hEigeartaigh Assignee: fabio martelli Fix For: 1.1.0 When configuring a Connector in Syncope, it is possible to hover the mouse pointer over the textfield to see the corresponding help message associated with the property. However, when the property is a multi-valued field, no help message appears. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: [VOTE] Apache Syncope 1.0.6
Il giorno 27/feb/2013, alle ore 15.00, Massimiliano Perrone ha scritto: Hi All, I've created a 1.0.6 release, with the following artifacts up for a vote: SVN source tag (r1450752): https://svn.apache.org/repos/asf/syncope/tags/syncope-1.0.6/ List of changes: https://svn.apache.org/repos/asf/syncope/tags/syncope-1.0.6/CHANGES Maven staging repo: https://repository.apache.org/content/repositories/orgapachesyncope-310/ Source release (checksums and signatures are available at the same location): https://repository.apache.org/content/repositories/orgapachesyncope-310/org/apache/syncope/syncope-root/1.0.6/syncope-root-1.0.6-source-release.zip Staging site: http://syncope.apache.org/1.0.6/ PGP release keys (signed using C481E45C): http://www.apache.org/dist/syncope/KEYS Vote will be open for 72 hours. +1 for me
Re: [VOTE] Apache Syncope 1.0.6
Il 27/02/2013 15:00, Massimiliano Perrone ha scritto: Hi All, I've created a 1.0.6 release, with the following artifacts up for a vote: SVN source tag (r1450752): https://svn.apache.org/repos/asf/syncope/tags/syncope-1.0.6/ List of changes: https://svn.apache.org/repos/asf/syncope/tags/syncope-1.0.6/CHANGES Maven staging repo: https://repository.apache.org/content/repositories/orgapachesyncope-310/ Source release (checksums and signatures are available at the same location): https://repository.apache.org/content/repositories/orgapachesyncope-310/org/apache/syncope/syncope-root/1.0.6/syncope-root-1.0.6-source-release.zip Staging site: http://syncope.apache.org/1.0.6/ PGP release keys (signed using C481E45C): http://www.apache.org/dist/syncope/KEYS Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) +1 -- Massimiliano Perrone Tel +39 393 9121310 Tirasa S.r.l. Viale D'Annunzio 267 - 65127 Pescara Tel +39 0859116307 / FAX +39 085973 http://www.tirasa.net Apache Syncope PMC Member http://people.apache.org/~massi/ L'apprendere molte cose non insegna l'intelligenza (Eraclito)
Error with REST users/username=X
As per the discussions on SYNCOPE-324, I'm reading a user (from the new
API) via:
users?username=X
I am authenticating using the User's username/password and not the admin
user/password. I get an exception in the logs:
org.apache.syncope.core.rest.controller.UnauthorizedRoleException: Missing
entitlement for role(s) [100]
at
org.apache.syncope.core.rest.data.UserDataBinder.getUserFromUsername(UserDataBinder.java:132)
~[UserDataBinder.class:na]
Syncope is set up with a single Role with no entitlements, and a single
User with that role, that I am authenticating as. In
UserDataBinder.getUserFromUsername we have:
SetLong roleIds = user.getRoleIds();
SetLong adminRoleIds =
EntitlementUtil.getRoleIds(EntitlementUtil.getOwnedEntitlementNames());
roleIds.removeAll(adminRoleIds);
if (!roleIds.isEmpty()) {
throw new UnauthorizedRoleException(roleIds);
}
In this case, adminRoleIds is empty and so the exception is thrown. Any
ideas?
Colm.
--
Colm O hEigeartaigh
Talend Community Coder
http://coders.talend.com
Re: Error with REST users/username=X
On 27/02/2013 16:10, Colm O hEigeartaigh wrote:
As per the discussions on SYNCOPE-324, I'm reading a user (from the new
API) via:
users?username=X
I am authenticating using the User's username/password and not the admin
user/password. I get an exception in the logs:
org.apache.syncope.core.rest.controller.UnauthorizedRoleException: Missing
entitlement for role(s) [100]
at
org.apache.syncope.core.rest.data.UserDataBinder.getUserFromUsername(UserDataBinder.java:132)
~[UserDataBinder.class:na]
Syncope is set up with a single Role with no entitlements, and a single
User with that role, that I am authenticating as. In
UserDataBinder.getUserFromUsername we have:
SetLong roleIds = user.getRoleIds();
SetLong adminRoleIds =
EntitlementUtil.getRoleIds(EntitlementUtil.getOwnedEntitlementNames());
roleIds.removeAll(adminRoleIds);
if (!roleIds.isEmpty()) {
throw new UnauthorizedRoleException(roleIds);
}
In this case, adminRoleIds is empty and so the exception is thrown. Any
ideas?
Hi Colm,
for reading own roles, the same approach as per RoleController#selfRead
should be implemented.
Regards.
--
Francesco Chicchiriccò
ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member
http://people.apache.org/~ilgrosso/
[jira] [Commented] (SYNCOPE-278) Verify export / import
[ https://issues.apache.org/jira/browse/SYNCOPE-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13588415#comment-13588415 ] Hudson commented on SYNCOPE-278: Integrated in Syncope-trunk #118 (See [https://builds.apache.org/job/Syncope-trunk/118/]) SYNCOPE-278 - fix for a mysql db export (Revision 1450761) Result = FAILURE fmartelli : Files : * /syncope/trunk/core/src/main/java/org/apache/syncope/core/init/JobInstanceLoader.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/util/ImportExport.java * /syncope/trunk/core/src/main/java/org/apache/syncope/core/util/multiparent/MultiParentNodeOp.java Verify export / import -- Key: SYNCOPE-278 URL: https://issues.apache.org/jira/browse/SYNCOPE-278 Project: Syncope Issue Type: Task Reporter: Francesco Chicchiriccò Assignee: fabio martelli Fix For: 1.1.0 Verify how exporting / importing db content is working after latest modifications from SYNCOPE-241, against all supported DBMS. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
Syncope-trunk - Build # 118 - Failure
The Apache Jenkins build system has built Syncope-trunk (build #118) Status: Failure Check console output at https://builds.apache.org/job/Syncope-trunk/118/ to view the results.
Re: [VOTE] Apache Syncope 1.0.6
On 27/02/2013 15:00, Massimiliano Perrone wrote: Hi All, I've created a 1.0.6 release, with the following artifacts up for a vote: SVN source tag (r1450752): https://svn.apache.org/repos/asf/syncope/tags/syncope-1.0.6/ List of changes: https://svn.apache.org/repos/asf/syncope/tags/syncope-1.0.6/CHANGES Maven staging repo: https://repository.apache.org/content/repositories/orgapachesyncope-310/ Source release (checksums and signatures are available at the same location): https://repository.apache.org/content/repositories/orgapachesyncope-310/org/apache/syncope/syncope-root/1.0.6/syncope-root-1.0.6-source-release.zip Staging site: http://syncope.apache.org/1.0.6/ PGP release keys (signed using C481E45C): http://www.apache.org/dist/syncope/KEYS Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) +1 Regards. -- Francesco Chicchiriccò ASF Member, Apache Syncope PMC chair, Apache Cocoon PMC Member http://people.apache.org/~ilgrosso/
Syncope-trunk - Build # 119 - Fixed
The Apache Jenkins build system has built Syncope-trunk (build #119) Status: Fixed Check console output at https://builds.apache.org/job/Syncope-trunk/119/ to view the results.
[jira] [Created] (SYNCOPE-327) Error messages during Tomcat shutdown
Francesco Chicchiriccò created SYNCOPE-327: -- Summary: Error messages during Tomcat shutdown Key: SYNCOPE-327 URL: https://issues.apache.org/jira/browse/SYNCOPE-327 Project: Syncope Issue Type: Bug Components: build-tools, core Affects Versions: 1.0.6, 1.1.0 Reporter: Francesco Chicchiriccò Fix For: 1.1.0 As reported in user ML [1], during shutdown of Tomcat instance with Syncope is deployed, some error messages are logged, like as: SEVERE: The web application [/syncope] appears to have started a thread named [pool-7-thread-1] but has failed to stop it. This is very likely to create a memory leak. SEVERE: The web application [/syncope] appears to have started a thread named [H2 Close Delay SYNCOPEDB] but has failed to stop it. This is very likely to create a memory leak. SEVERE: The web application [/syncope] appears to have started a thread named [H2 Close Delay SYNCOPEDB] but has failed to stop it. This is very likely to create a memory leak. SEVERE: The web application [/syncope] created a ThreadLocal with key of type [org.apache.syncope.core.persistence.beans.AbstractBaseBean$1] (value [org.apache.syncope.core.persistence.beans.AbstractBaseBean$1@70ef798d]) and a value of type [java.text.SimpleDateFormat] (value [java.text.SimpleDateFormat@8a9df5fb]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak. SEVERE: The web application [/syncope] created a ThreadLocal with key of type [org.apache.syncope.core.persistence.beans.AbstractBaseBean$1] (value [org.apache.syncope.core.persistence.beans.AbstractBaseBean$1@70ef798d]) and a value of type [java.text.SimpleDateFormat] (value [java.text.SimpleDateFormat@f67a0200]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak. [1] http://markmail.org/message/3rznykqdwsuh6nhc -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (SYNCOPE-126) Database import / export and related tasks
[ https://issues.apache.org/jira/browse/SYNCOPE-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13588505#comment-13588505 ] Marco Di Sabatino Di Diodoro commented on SYNCOPE-126: -- Case Insensitive Table And Column Names In MySQL While you should always uphold the case-sensitive tablenames, it can be troublesome when migrating from a host that had this option enabled (table column names become case insensitive), to a host that doesn't have this option -- so you suddenly find yourself stuck with case sensitive table and column names. To solve this, edit your /etc/my.cnf file and add the following line into mysqld: lower_case_table_names=1 Database import / export and related tasks -- Key: SYNCOPE-126 URL: https://issues.apache.org/jira/browse/SYNCOPE-126 Project: Syncope Issue Type: Task Components: documentation Reporter: Francesco Chicchiriccò Fix For: 1.1.0 Provide some documentation about how to export / import database content, in particular about sequence tables and their initialization for import. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (SYNCOPE-327) Error messages during Tomcat shutdown
[ https://issues.apache.org/jira/browse/SYNCOPE-327?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13588726#comment-13588726 ] Hudson commented on SYNCOPE-327: Integrated in Syncope-trunk #120 (See [https://builds.apache.org/job/Syncope-trunk/120/]) [SYNCOPE-327] Fixing messages related to JDBC (Revision 1450847) Result = SUCCESS ilgrosso : Files : * /syncope/trunk/build-tools/pom.xml * /syncope/trunk/build-tools/src/main/java/org/apache/syncope/buildtools/H2StartStopListener.java * /syncope/trunk/core/src/test/resources/persistence.properties * /syncope/trunk/standalone/pom.xml Error messages during Tomcat shutdown - Key: SYNCOPE-327 URL: https://issues.apache.org/jira/browse/SYNCOPE-327 Project: Syncope Issue Type: Bug Components: build-tools, core Affects Versions: 1.0.6, 1.1.0 Reporter: Francesco Chicchiriccò Assignee: Francesco Chicchiriccò Fix For: 1.1.0 As reported in user ML [1], during shutdown of Tomcat instance with Syncope is deployed, some error messages are logged, like as: SEVERE: The web application [/syncope] appears to have started a thread named [pool-7-thread-1] but has failed to stop it. This is very likely to create a memory leak. SEVERE: The web application [/syncope] appears to have started a thread named [H2 Close Delay SYNCOPEDB] but has failed to stop it. This is very likely to create a memory leak. SEVERE: The web application [/syncope] appears to have started a thread named [H2 Close Delay SYNCOPEDB] but has failed to stop it. This is very likely to create a memory leak. SEVERE: The web application [/syncope] created a ThreadLocal with key of type [org.apache.syncope.core.persistence.beans.AbstractBaseBean$1] (value [org.apache.syncope.core.persistence.beans.AbstractBaseBean$1@70ef798d]) and a value of type [java.text.SimpleDateFormat] (value [java.text.SimpleDateFormat@8a9df5fb]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak. SEVERE: The web application [/syncope] created a ThreadLocal with key of type [org.apache.syncope.core.persistence.beans.AbstractBaseBean$1] (value [org.apache.syncope.core.persistence.beans.AbstractBaseBean$1@70ef798d]) and a value of type [java.text.SimpleDateFormat] (value [java.text.SimpleDateFormat@f67a0200]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak. [1] http://markmail.org/message/3rznykqdwsuh6nhc -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
