[jira] [Updated] (SYNCOPE-499) Deletion of Role used as parent role in role template generate exception editing role template
[ https://issues.apache.org/jira/browse/SYNCOPE-499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andrea Patricelli updated SYNCOPE-499: -- Affects Version/s: 1.2.0 > Deletion of Role used as parent role in role template generate exception > editing role template > -- > > Key: SYNCOPE-499 > URL: https://issues.apache.org/jira/browse/SYNCOPE-499 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 1.1.7, 1.2.0 > Environment: Apache Syncope 1.1.7 standalone distribution on Windows > 7 64bit and Oracle Java7 SE >Reporter: Denis Signoretto > > Steps to reproduce: > 1) Create a role > 2) Create a Synchronization Task and assign the previously created role as > parent role in the role template > 3) Delete previously created role > 4) Try edit role template > 5) Exception > Grave: Servlet.service() for servlet [syncope-core-rest] in context with path > [/syncope] threw exception [Request processing failed; nested exception is > org.apache.syncope.core.persistence.dao.NotFoundException: Role 152] with > root cause > org.apache.syncope.core.persistence.dao.NotFoundException: Role 152 > at > org.apache.syncope.core.rest.data.RoleDataBinder.getRoleFromId(RoleDataBinder.java:73) > at > org.apache.syncope.core.rest.data.RoleDataBinder$$FastClassBySpringCGLIB$$75f19568.invoke() > at > org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204) > at > org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:700) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Updated] (SYNCOPE-499) Deletion of Role used as parent role in role template generate exception editing role template
[ https://issues.apache.org/jira/browse/SYNCOPE-499?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francesco Chicchiriccò updated SYNCOPE-499: --- Fix Version/s: 1.2.0 1.1.8 > Deletion of Role used as parent role in role template generate exception > editing role template > -- > > Key: SYNCOPE-499 > URL: https://issues.apache.org/jira/browse/SYNCOPE-499 > Project: Syncope > Issue Type: Bug > Components: console >Affects Versions: 1.1.7, 1.2.0 > Environment: Apache Syncope 1.1.7 standalone distribution on Windows > 7 64bit and Oracle Java7 SE >Reporter: Denis Signoretto > Fix For: 1.1.8, 1.2.0 > > > Steps to reproduce: > 1) Create a role > 2) Create a Synchronization Task and assign the previously created role as > parent role in the role template > 3) Delete previously created role > 4) Try edit role template > 5) Exception > Grave: Servlet.service() for servlet [syncope-core-rest] in context with path > [/syncope] threw exception [Request processing failed; nested exception is > org.apache.syncope.core.persistence.dao.NotFoundException: Role 152] with > root cause > org.apache.syncope.core.persistence.dao.NotFoundException: Role 152 > at > org.apache.syncope.core.rest.data.RoleDataBinder.getRoleFromId(RoleDataBinder.java:73) > at > org.apache.syncope.core.rest.data.RoleDataBinder$$FastClassBySpringCGLIB$$75f19568.invoke() > at > org.springframework.cglib.proxy.MethodProxy.invoke(MethodProxy.java:204) > at > org.springframework.aop.framework.CglibAopProxy$CglibMethodInvocation.invokeJoinpoint(CglibAopProxy.java:700) -- This message was sent by Atlassian JIRA (v6.2#6252)
[jira] [Commented] (SYNCOPE-498) Connector SpinnerFieldPanel required values
[ https://issues.apache.org/jira/browse/SYNCOPE-498?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14017607#comment-14017607 ] Colm O hEigeartaigh commented on SYNCOPE-498: - Fix confirmed, thanks! Colm. > Connector SpinnerFieldPanel required values > --- > > Key: SYNCOPE-498 > URL: https://issues.apache.org/jira/browse/SYNCOPE-498 > Project: Syncope > Issue Type: Bug > Components: console >Reporter: Colm O hEigeartaigh >Assignee: Francesco Chicchiriccò >Priority: Minor > Fix For: 1.2.0 > > > With the latest Syncope trunk code, I noticed that if I create a new LDAP > Connector (1.3.6) it appears to be requiring me to enter a Block Size + > Change Log Block Size, even though these parameters are optional and both > default to 100. You can reproduce by just creating an LDAP Connector + > clicking on save. At the top of the screen you can see: >'Host' is required. > 'TCP Port' is required. > 'Base Contexts' is required. > 'Block Size' is required. > 'Change Log Block Size' is required. > The issue seems to be related to the new component "SpinnerFieldPanel" used > to represents numeric connector configuration properties. -- This message was sent by Atlassian JIRA (v6.2#6252)
1.2 REST API
Am I correct in assuming that the REST API for 1.2 exposes the CXF-based REST service under "/rest", and that the old API previously available under "/rest" is removed? I think it would probably be a good idea to redirect "/cxf" queries to "/rest" so as not to break REST-based 1.1 clients, WDYT? Colm. -- Colm O hEigeartaigh Talend Community Coder http://coders.talend.com
Re: 1.2 REST API
On 04/06/2014 13:09, Colm O hEigeartaigh wrote: Am I correct in assuming that the REST API for 1.2 exposes the CXF-based REST service under "/rest", and that the old API previously available under "/rest" is removed? Correct. I think it would probably be a good idea to redirect "/cxf" queries to "/rest" so as not to break REST-based 1.1 clients, WDYT? I don't see any problem with this redirect - I am actually wondering how to implement it - but AFAIR there are some differences between CXF 1.1 and 1.2 APIs. Regards. -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Involved at The Apache Software Foundation: member, Syncope PMC chair, Cocoon PMC, Olingo PMC http://people.apache.org/~ilgrosso/
Re: 1.2 REST API
On 04/06/14 12:13, Francesco Chicchiriccò wrote: On 04/06/2014 13:09, Colm O hEigeartaigh wrote: Am I correct in assuming that the REST API for 1.2 exposes the CXF-based REST service under "/rest", and that the old API previously available under "/rest" is removed? Correct. I think it would probably be a good idea to redirect "/cxf" queries to "/rest" so as not to break REST-based 1.1 clients, WDYT? I don't see any problem with this redirect - I am actually wondering how to implement it - but AFAIR there are some differences between CXF 1.1 and 1.2 APIs. The simplest option is to have a "/cxf" method that will call if it is at all possible in a given case on "/rest" handler. Or have PreMatching ContainerRequestFilter that will change the request URI if it ends with "/cxf". Client side redirect with Request.seeOther is also possible. Cheers, Sergey Regards.
[jira] [Commented] (SYNCOPE-496) Upgrade jboss-it profile to Wildfly 8
[
https://issues.apache.org/jira/browse/SYNCOPE-496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14017754#comment-14017754
]
ASF subversion and git services commented on SYNCOPE-496:
-
Commit 1600276 from [~ilgrosso] in branch 'syncope/trunk'
[ https://svn.apache.org/r1600276 ]
[SYNCOPE-496] Maven build profile updated - required ConnId SOAP connector
upgrade
> Upgrade jboss-it profile to Wildfly 8
> -
>
> Key: SYNCOPE-496
> URL: https://issues.apache.org/jira/browse/SYNCOPE-496
> Project: Syncope
> Issue Type: Task
> Components: core
>Affects Versions: 1.2.0
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
> Fix For: 1.2.0
>
>
> Currently the {{jboss-it}} build profile works with an unofficial JBoss AS
> 7.2.0 version.
> Since Widlfly (the new name of the free variant of JBoss AS) was released,
> this profile needs to be upgraded.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[jira] [Resolved] (SYNCOPE-496) Upgrade jboss-it profile to Wildfly 8
[
https://issues.apache.org/jira/browse/SYNCOPE-496?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Francesco Chicchiriccò resolved SYNCOPE-496.
Resolution: Fixed
> Upgrade jboss-it profile to Wildfly 8
> -
>
> Key: SYNCOPE-496
> URL: https://issues.apache.org/jira/browse/SYNCOPE-496
> Project: Syncope
> Issue Type: Task
> Components: core
>Affects Versions: 1.2.0
>Reporter: Francesco Chicchiriccò
>Assignee: Francesco Chicchiriccò
> Fix For: 1.2.0
>
>
> Currently the {{jboss-it}} build profile works with an unofficial JBoss AS
> 7.2.0 version.
> Since Widlfly (the new name of the free variant of JBoss AS) was released,
> this profile needs to be upgraded.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
[PROPOSAL] Some roadmap ideas
Hi guys, I'm happy as I should have some time to work again on Syncope next week (and the following weeks ;)). I have some ideas that I would like to share and discuss with you. Please, correct me if I'm wrong, if the ideas are stupid, or already done ;) 1/ Provide a Karaf LoginModule for Syncope and a Karaf feature We already discussed of that in the past. It doesn't change the Syncope codebase itself, it's just an addition on the Karaf side. The first thing is to provide a SyncopeLoginModule in Karaf allowing to delegate the user backend to Syncope. Currently, Karaf provides PropertiesLoginModule (the username/password are stored in the simple properties file), LDAPLoginModule, JDBCLoginModule, and OSGiLoginModule. Thanks to the SyncopeLoginModule, the users just delegate the Karaf container JAAS realm backend to Syncope, who manages its own backend (LDAP, etc). On the other hand, I will provide a Karaf feature to be able to easily install Syncope directly in Karaf. 2/ OAuth2 Service Provider feature More and more companies want to provide an "internal" oauth2 service provider (instead of using "public" one like amazon, bitbucket, etc). What do you think to add an optional feature to Syncope to turn Syncope as an OAuth2 Service Provider ? 3/ CXF authentication ready to use feature Right now, we can use Syncope with CXF by implementing an interceptor delegating to the Syncope REST API. It's not really straight forward for the user as it requires to write some kind of plumbing code. I think it could be helpful to provide a ready to use "CXF feature" providing the interceptor that we can configure (the location of the Syncope instance, etc). Maybe it makes more sense to add this on the CXF part more than on the Syncope side, but, anyway, it could be very helpful for the users. WDYT ? Thanks, Regards JB -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com
