Re: Proposal: using ctor-level dependency injection
On 19/02/21 11:41, Misagh Moayyed wrote: > Hello all, > > I want to discuss and propose a design change in the way Syncope components, > specially *Logic classes are constructed. For a concrete example, this > component [1] might be a good baseline. > > Components such as [1] do two things that seem less than ideal: > > 1) The class is directly annotated with a @Component > 2) It uses field-injections by annotating fields with @Autowire and such > > I submit that this approach generally proves challenging, specially when it > comes to constructing a context for integration tests and dealing with > classpath scanning. There is lot of literature on why this (field injections) > might not be an ideal approach; The "test context and component scanning" is > one practical example that I myself ran into; Purists might also argue that > business-level components and logic classes should not be tied to the upper > framework per se (though I don't actually find myself in this camp all too > often!). > > A better alternative perhaps would be: > > - Avoid field-injections and use ctor-level injections (this is the general > recommendation from Spring) > - Do not use autowire/component/etc directly in business-level classes > - ...which means do not rely as much (if ever) on classpath/context scanning > - ...and instead, create and instantiate the bean directory in @Configuration > classes, conditionally and with direct control > - ...or use a middle-ground for now, with something like this [2] > > The work feels largely cosmetic perhaps; I think it will pay off in the > future specially if it's something that is advocated by Spring and family. > > WDYT? Hi Misagh, thanks for bringing up this discussion. Moving (especially, but not only) Logic classes from the current "@Component + @Autowired" setup to something more in line with [2] would be beneficial not only for cosmetics but also to simplify override or extensions for deployments. At least for Logic, I suspect [3] would be the central place at least for IdRepo, then we'll need to setup similar classes form IdM and AM, respectively. Globally, I'd say not a difficult but labor intensive task to accomplish. A big +1 from my side. Regards. > [1] > https://github.com/apache/syncope/blob/master/core/am/logic/src/main/java/org/apache/syncope/core/logic/OIDCJWKSLogic.java > [2] > https://docs.spring.io/spring-boot/docs/2.0.x/reference/html/using-boot-spring-beans-and-dependency-injection.html [3] https://github.com/apache/syncope/blob/master/core/idrepo/logic/src/main/java/org/apache/syncope/core/logic/LogicContext.java -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
[DISCUSS] Google Summer of Code 2021
Hi all, given the approaching timeline for GSOC 2021 [1], I went ahead, created a proposal [2] and subscribed ment...@community.apache.org I invite anyone else to do the same, I think this is a very good mean to explore new integrations / features and also attract new blood for supporting future development. Regards. [1] https://community.apache.org/gsoc.html [2] https://issues.apache.org/jira/browse/SYNCOPE-1617 -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
Re: JDK 16 is in Rampdown Phase One
Hi Rory, I am glad to say we did restore the JDK 16 build with a dedicated Maven profile: see latest run https://travis-ci.com/github/apache/syncope/jobs/463955669 Regards. On 21/12/20 11:40, Rory O'Donnell wrote: > Thanks Francesco - looks like JEP 396 has had some impact. > > Rgds,Rory > > On 21/12/2020 09:49, Francesco Chicchiriccò wrote: >> Hi Rory, >> FYI it seems that this very last update is causing troubles to some of our >> dependencies; as a result, we cannot build anymore Syncope with latest JDK >> 16 releases. >> >> New issues we have opened (or just found and watching) on this topic: >> >> * https://github.com/rzwitserloot/lombok/issues/2681 >> * https://github.com/spring-projects/spring-boot/pull/24453 >> * https://gitlab.ow2.org/asm/asm/-/issues/317926 >> * https://issues.apache.org/jira/browse/OPENJPA-2846 >> >> Regards. >> >> On 2020/12/13 16:40:53, "Rory O'Donnell" wrote: >> > Hi Francesco, >> > >> > *Per the JDK 16 schedule , we are in Rampdown Phase One* *[1] . >> > * >> > >> > *Please advise if you find any issues while testing the latest Early >> > Access builds.* >> > >> > * Schedule for JDK 16 >> > o *2020/12/10 Rampdown Phase One* >> > o 2021/01/14 Rampdown Phase Two >> > o 2021/02/04 Initial Release Candidate >> > o 2021/02/18 Final Release Candidate >> > o 2021/03/16 General Availability >> > * Release Notes [2] >> > >> > OpenJDK 16 Early Access build 28**is now available at >> > http://jdk.java.net/16 >> > >> > * Features - the overall feature set is frozen. No further JEPs will >> > be targeted to this release. >> > * Significant Integrations in b28: >> > o *Integrated JEP 396: **Strongly Encapsulate JDK Internals by >> > Default ** >> > * >> > + Strongly encapsulate all internal elements of the JDK by >> > default, except for critical internal APIs >> > such as >> > |sun.misc.Unsafe|. >> > + Allow end users to choose the relaxed strong encapsulation >> > that has been the default since JDK 9. >> > o Integrated JEP 397: Sealed Classes (Second Preview) >> > with this release. >> > + Enhance the Java programming language with sealed classes >> > and interfaces >> > . >> > + Refines JEP 360 which >> > was delivered in JDK 15 as a preview feature. >> > >> > * These early-access , open-source builds are provided under the GNU >> > General Public License, version 2, with the Classpath Exception >> > . >> > * Changes in recent builds that maybe of interest: >> > o Build 28 >> > + JDK-8256299: JEP 396: Strongly Encapsulate JDK Internals by >> > Default >> > + JDK-8166596: TLS support for the EdDSA signature algorithm >> > + JDK-8256718: Old tracing flags are now obsolete and must be >> > replaced with unified logging >> > o Build 27 >> > + JDK-8159746: (proxy) Support for default methods >> > + JDK-8254631: Better support ALPN byte wire values in SunJSSE >> > >> > Project Loom Early-Access: *Build 16-loom+9-316 >> > * (2020/11/30) - based on JDK-16+25 >> > >> > >> > * These early-access builds are provided under the GNU General Public >> > License, version 2, with the Classpath Exception >> > >> > * These builds are intended for developers looking to "kick the tyres" >> > and provide feedback on using the API or by sending bug reports. >> > * Please send feedback via e-mail to loom-...@openjdk.java.net >> > . To send e-mail to this address >> > you must first subscribe to the mailing list >> > . >> > >> > Rgds, Rory >> > >> > [1] >> > https://mail.openjdk.java.net/pipermail/jdk-dev/2020-December/004991.html >> > [2] https://jdk.java.net/16/release-notes -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
Re: JDK 16 is in Rampdown Phase One
Hi Rory, FYI it seems that this very last update is causing troubles to some of our dependencies; as a result, we cannot build anymore Syncope with latest JDK 16 releases. New issues we have opened (or just found and watching) on this topic: * https://github.com/rzwitserloot/lombok/issues/2681 * https://github.com/spring-projects/spring-boot/pull/24453 * https://gitlab.ow2.org/asm/asm/-/issues/317926 * https://issues.apache.org/jira/browse/OPENJPA-2846 Regards. On 2020/12/13 16:40:53, "Rory O'Donnell" wrote: > Hi Francesco, > > *Per the JDK 16 schedule , we are in Rampdown Phase One* *[1] . > * > > *Please advise if you find any issues while testing the latest Early > Access builds.* > > * Schedule for JDK 16 > o *2020/12/10 Rampdown Phase One* > o 2021/01/14 Rampdown Phase Two > o 2021/02/04 Initial Release Candidate > o 2021/02/18 Final Release Candidate > o 2021/03/16 General Availability > * Release Notes [2] > > OpenJDK 16 Early Access build 28**is now available at > http://jdk.java.net/16 > > * Features - the overall feature set is frozen. No further JEPs will > be targeted to this release. > * Significant Integrations in b28: > o *Integrated JEP 396: **Strongly Encapsulate JDK Internals by > Default ** > * > + Strongly encapsulate all internal elements of the JDK by > default, except for critical internal APIs > such as > |sun.misc.Unsafe|. > + Allow end users to choose the relaxed strong encapsulation > that has been the default since JDK 9. > o Integrated JEP 397: Sealed Classes (Second Preview) > with this release. > + Enhance the Java programming language with sealed classes > and interfaces > . > + Refines JEP 360 which > was delivered in JDK 15 as a preview feature. > > * These early-access , open-source builds are provided under the GNU > General Public License, version 2, with the Classpath Exception > . > * Changes in recent builds that maybe of interest: > o Build 28 > + JDK-8256299: JEP 396: Strongly Encapsulate JDK Internals by > Default > + JDK-8166596: TLS support for the EdDSA signature algorithm > + JDK-8256718: Old tracing flags are now obsolete and must be > replaced with unified logging > o Build 27 > + JDK-8159746: (proxy) Support for default methods > + JDK-8254631: Better support ALPN byte wire values in SunJSSE > > Project Loom Early-Access: *Build 16-loom+9-316 > * (2020/11/30) - based on JDK-16+25 > > > * These early-access builds are provided under the GNU General Public > License, version 2, with the Classpath Exception > > * These builds are intended for developers looking to "kick the tyres" > and provide feedback on using the API or by sending bug reports. > * Please send feedback via e-mail to loom-...@openjdk.java.net > . To send e-mail to this address > you must first subscribe to the mailing list > . > > Rgds, Rory > > [1] > https://mail.openjdk.java.net/pipermail/jdk-dev/2020-December/004991.html > [2] https://jdk.java.net/16/release-notes > > -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
[ANN] Apache Syncope 2.1.8
The Apache Syncope team is pleased to announce the release of Syncope 2.1.8 Apache Syncope is an Open Source system for managing digital identities in enterprise environments, implemented in Java EE technology . The release will be available within 24h from: https://syncope.apache.org/downloads Read the full change log available here: https://s.apache.org/syncope218 Upgrading from 2.1.7? There are some notes about this process: https://s.apache.org/s29ad We welcome your help and feedback. For more information on how to report problems, and to get involved, visit the project website at http://syncope.apache.org/ The Apache Syncope Team
[RESULT] [VOTE] Apache Syncope 2.1.8
Hi all, after 72 hours, the vote for Syncope 2.1.8 [1] *passes* with 5 PMC + 1 non-PMC votes. +1 (PMC / binding) * Jean-Baptiste Onofré * Andrea Patricelli * Fabio Martelli * Marco Di Sabatino * Francesco Chicchiriccò +1 (non binding) * Misagh Moayyed 0 -1 Thanks to everyone participating. I will now copy this release to Syncope' dist directory, promote the artifacts to the central Maven repository and publish to DockerHub. Best regards. [1] https://lists.apache.org/thread.html/rc183c228801648bdb61d5e5eff5b0b95bd7e2a085a76dd4314d24c1f%40%3Cdev.syncope.apache.org%3E -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
[VOTE] Apache Syncope 2.1.8
I've created a 2.1.8 release, with the following artifacts up for a vote: GIT source tag (29738bc13cfbb7b26829c2b1bfb7df9649349984): https://gitbox.apache.org/repos/asf?p=syncope.git;a=tag;h=800f7ea List of changes: https://gitbox.apache.org/repos/asf?p=syncope.git;a=blob;f=CHANGES;hb=800f7ea Staging artifacts: https://dist.apache.org/repos/dist/dev/syncope/2.1.8/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachesyncope-1066/ Staging site: http://syncope.apache.org/2.1.8/index.html PGP release keys (signed using 273DF287): http://www.apache.org/dist/syncope/KEYS Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Here's my +1 Regards. -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
Rolling new release: 2.1.8
Hi all, given the fact that we have some important fixes available for 2.1.8 [1], I would like to start soon the release process, with purpose of delivering a nice Christmas present to our users. Do you see any problem? Regards. [1] https://issues.apache.org/jira/issues/?jql=statusCategory%20%3D%20done%20AND%20project%20%3D%2012313120%20AND%20fixVersion%20%3D%2012348788%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
Re: JDK 16 EA build 18 is now available
Hi Rory, it took just a few days but we've finally enabled our tests on JDK 16ea: https://travis-ci.org/github/apache/syncope/jobs/735006126 Regards. On 2020/10/02 09:13:01, "Rory O'Donnell" wrote: > Hi Francesco, > > OpenJDK 16 Early Access build 18**is now available at http://jdk.java.net/16 > > * These early-access , open-source builds are provided under the > o GNU General Public License, version 2, with the Classpath > Exception . > > * Features: > o JEPs proposed to target JDK 16 > + JEP 376: ZGC: Concurrent Thread-Stack Processing > > + JEP 386: Alpine Linux Port > + JEP 388: Windows/AArch64 Port > > o JEPs targeted to JDK 16, so far: > + JEP 338: Vector API (Incubator) > > + JEP 347: Enable C++14 Language Features > > + JEP 357: Migrate from Mercurial to Git > > + JEP 369: Migrate to GitHub > + JEP 387: Elastic Metaspace > > * Release Notes are available at http://jdk.java.net/16/release-notes > > ** > > * Changes in recent builds that maybe of interest: > o Build 17 > + JDK-8247281: Object monitors no longer keep strong > references to their associated object > + JDK-8202473: A type variable with multiple bounds does not > correctly place type annotation > # Reported by ByteBuddy > + JDK-8234808: jdb quoted option parsing broken > # Reported by Apache Tomcat > o Build 16 > + JDK-8172366: SUN, SunRsaSign, and SunEC Providers Supports > SHA-3 Based Signature Algorithms > + JDK-8244706: GZIPOutputStream now sets the GZIP OS Header > Field to the correct default value > > * Quality Report for September 2020 was published here [1]. Thanks to > everyone who contributed by creating features or enhancements, > logging bugs, or downloading and testing the early-access builds. > > > *__* > Rgds,Rory > > [1] > https://wiki.openjdk.java.net/display/quality/Quality+Outreach+report+September+2020 > > -- > Rgds, Rory O'Donnell > Quality Engineering Manager > Oracle EMEA, Dublin, Ireland -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
[CVE-2020-11977] Apache Syncope: Remote Code Execution via Flowable workflow definition
Description: When the Flowable extension is enabled, an administrator with workflow entitlements can use Shell Service Tasks to perform malicious operations, including but not limited to file read, file write, and code execution. Severity: Low Vendor: The Apache Software Foundation Affects: 2.1.X releases prior to 2.1.7 Solution: 2.1.X users: upgrade to 2.1.7 Credit: This issue was discovered by ch0wn of Orz Lab.
[ANN] Apache Syncope 2.0.16
The Apache Syncope team is pleased to announce the release of Syncope 2.0.16 Apache Syncope is an Open Source system for managing digital identities in enterprise environments, implemented in Java EE technology . The release will be available within 24h from: https://syncope.apache.org/downloads Read the full change log available here: https://s.apache.org/syncope2016 Upgrading from 2.0.15? There are some notes about this process: https://s.apache.org/60s6n We welcome your help and feedback. For more information on how to report problems, and to get involved, visit the project website at http://syncope.apache.org/ The Apache Syncope Team
[ANN] Apache Syncope 2.1.7
The Apache Syncope team is pleased to announce the release of Syncope 2.1.7 Apache Syncope is an Open Source system for managing digital identities in enterprise environments, implemented in Java EE technology . The release will be available within 24h from: https://syncope.apache.org/downloads Read the full change log available here: https://s.apache.org/syncope217 Upgrading from 2.1.6? There are some notes about this process: https://s.apache.org/4mip8 We welcome your help and feedback. For more information on how to report problems, and to get involved, visit the project website at http://syncope.apache.org/ The Apache Syncope Team
[RESULT] [VOTE] Apache Syncope 2.0.16
Hi all, after 72 hours, the vote for Syncope 2.0.16 [1] *passes* with 6 PMC + 1 non-PMC votes. +1 (PMC / binding) * Fabio Martelli * Marco Di Sabatino * Jean-Baptiste Onofré * Andrea Patricelli * Matteo Alessandroni * Francesco Chicchiriccò +1 (non binding) * Lorenzo Di Cola 0 -1 Thanks to everyone participating. I will now copy this release to Syncope' dist directory, promote the artifacts to the central Maven repository and publish to DockerHub. Best regards. [1] https://lists.apache.org/thread.html/ra6d71153169631be033e5b0fba571b372708bd65fd218094c28323ce%40%3Cdev.syncope.apache.org%3E -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
[RESULT] [VOTE] Apache Syncope 2.1.7
Hi all, after 72 hours, the vote for Syncope 2.1.7 [1] *passes* with 6 PMC + 1 non-PMC votes. +1 (PMC / binding) * Fabio Martelli * Marco Di Sabatino * Jean-Baptiste Onofré * Andrea Patricelli * Matteo Alessandroni * Francesco Chicchiriccò +1 (non binding) * Lorenzo Di Cola 0 -1 Thanks to everyone participating. I will now copy this release to Syncope' dist directory, promote the artifacts to the central Maven repository and publish to DockerHub. Best regards. [1] https://lists.apache.org/thread.html/r8499038d957fc028bea1b1081cab0d501711b31bcaebad2084c56f8b%40%3Cdev.syncope.apache.org%3E -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
[VOTE] Apache Syncope 2.0.16
I've created a 2.0.16 release, with the following artifacts up for a vote: GIT source tag (d4e9faa33274b9e74e45720bc2a564732c29fa3e): https://gitbox.apache.org/repos/asf?p=syncope.git;a=tag;h=d4e9faa33274b9e74e45720bc2a564732c29fa3e List of changes: https://gitbox.apache.org/repos/asf?p=syncope.git;a=blob;f=CHANGES;hb=d4e9faa33274b9e74e45720bc2a564732c29fa3e Staging artifacts: https://dist.apache.org/repos/dist/dev/syncope/2.0.16/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachesyncope-1065/ Staging site (yes, same as for 2.1.7, not a typo): http://syncope.apache.org/2.1.7/index.html PGP release keys (signed using 273DF287): http://www.apache.org/dist/syncope/KEYS Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Here's my +1 Regards. -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
[VOTE] Apache Syncope 2.1.7
I've created a 2.1.7 release, with the following artifacts up for a vote: GIT source tag (29738bc13cfbb7b26829c2b1bfb7df9649349984): https://gitbox.apache.org/repos/asf?p=syncope.git;a=tag;h=29738bc13cfbb7b26829c2b1bfb7df9649349984 List of changes: https://gitbox.apache.org/repos/asf?p=syncope.git;a=blob;f=CHANGES;hb=29738bc13cfbb7b26829c2b1bfb7df9649349984 Staging artifacts: https://dist.apache.org/repos/dist/dev/syncope/2.1.7/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachesyncope-1064/ Staging site: http://syncope.apache.org/2.1.7/index.html PGP release keys (signed using 273DF287): http://www.apache.org/dist/syncope/KEYS Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Here's my +1 Regards. -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
Re: Migration to new ci-builds.a.o
FYI all seems to be working: https://ci-builds.apache.org./job/Syncope/ Regards. On 21/07/20 09:15, Francesco Chicchiriccò wrote: > Hi all, > the news stroke me by surprise but according to the mailing list thread [1], > we have to migrate all our Jenkins jobs to the new ci-builds.a.o server(s). > > I have created a ticket for establishing Apache Syncope folder [2] and will > try to migrate as many jobs as I can, but I would very likely need an > assistance with the release / publishing jobs, please let me know if someone > could help me with that. > > Thanks! > > [1] > https://lists.apache.org/thread.html/re974eed417a1bc294694701d5c91b4bf92689fcf32a4c91f169be87d%40%3Cbuilds.apache.org%3E > [2] https://issues.apache.org/jira/browse/INFRA-20567 -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
Migration to new ci-builds.a.o
Hi all, the news stroke me by surprise but according to the mailing list thread [1], we have to migrate all our Jenkins jobs to the new ci-builds.a.o server(s). I have created a ticket for establishing Apache Syncope folder [2] and will try to migrate as many jobs as I can, but I would very likely need an assistance with the release / publishing jobs, please let me know if someone could help me with that. Thanks! [1] https://lists.apache.org/thread.html/re974eed417a1bc294694701d5c91b4bf92689fcf32a4c91f169be87d%40%3Cbuilds.apache.org%3E [2] https://issues.apache.org/jira/browse/INFRA-20567 Regards. -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
Re: 2.1.x XML regression?
On 26/05/20 11:07, Colm O hEigeartaigh wrote:
> Hi all,
>
> I'm just migrating some test-cases from Syncope 2.0.13 to 2.1.6. I've
> noticed what seems like a regression. I'm creating a group called "boss" in
> Syncope. With 2.0.X I can query the REST API as follows:
>
> curl -H "Accept: application/xml" -u "admin:password"
> http://localhost:9080/syncope/rest/groups -
> v
>
> and I see:
>
> standalone="yes"?>http://syncope.apache.org/2.0;>1http://www.w3.org/2001/XMLSchema-instance;
> xsi:type="syncope2:groupTO">2020-05-26T09:57:32.237+01:00admin2020-05-26T09:57:32.237+01:00adminorg.apache.syncope.common.lib.to.GroupTO374fdc23-9aad-455d-8fdc-239aada55d34/GROUP00boss0011
>
> However, with 2.1.6 I only see:
>
> standalone="yes"?>http://syncope.apache.org/2.1
> ">111
>
> With JSON in 2.1.6 it's OK:
>
> {"prev":null,"next":null,"page":1,"size":1,"totalCount":1,"result":[{"@class":"org.apache.syncope.common.lib.to.GroupTO","@class":"org.apache.syncope.common.lib.to.GroupTO","key":"5cc6e67e-5321-46c4-86e6-7e532176c4ba","type":"GROUP","realm":"/","name":"boss","creator":"admin","creationDate":"2020-05-26T09:03:23.911+","lastModifier":"admin","lastChangeDate":"2020-05-26T09:03:23.911+","status":null,"userOwner":null,"groupOwner":null,"udynMembershipCond":null,"staticUserMembershipCount":0,"dynamicUserMembershipCount":0,"staticAnyObjectMembershipCount":0,"dynamicAnyObjectMembershipCount":0,"adynMembershipConds":{},"dynRealms":[],"auxClasses":[],"plainAttrs":[],"derAttrs":[],"virAttrs":[],"resources":[],"typeExtensions":[]}]}
>
> Should I create a JIRA for this, or am I making a mistake somewhere?
Hi Colm,
I committed the fix yesterday on 2_1_X for
https://issues.apache.org/jira/browse/SYNCOPE-1565
If you run the curl command as above against 2.1.7-SNAPSHOT it will work as
expected, as you can see for example by
curl -H "Accept: application/xml" -u "admin:password"
https://syncope-vm.apache.org/syncope/rest/groups
Regards.
--
Francesco Chicchiriccò
Tirasa - Open Source Excellence
http://www.tirasa.net/
Member at The Apache Software Foundation
Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail
http://home.apache.org/~ilgrosso/
Re: [Suggestions] Looking for a first-time issue or a feature
On 19/05/20 20:37, Supun Wanniarachchi wrote: > Hi All, > > I'm interested in working with Identity management and previously worked > with [SYNCOPE-152]. But I haven't worked with the project during the last > two years. I would like to continue contributing to the Syncope project. It > would be great if you could provide more details about good first-time > issues or any feature I can start contributing. > > Your suggestions would be highly appreciated. Hi Supun, glad to see you back! I'd say you have quite few options available: 1. complete Netbeans IDE support - see https://issues.apache.org/jira/browse/SYNCOPE-1403 2. work on increasing test coverage and code quality - essentially, continue the work started by the following PRs, but on different submodules: https://github.com/apache/syncope/pull/148 https://github.com/apache/syncope/pull/155 https://github.com/apache/syncope/pull/156 https://github.com/apache/syncope/pull/160 3. transform Admin Console IT Cases into Unit Tests - with target of speeding up the overall build time 4. join the effort for Syncope 3.0.0 - see https://cwiki.apache.org/confluence/display/SYNCOPE/%5BDISCUSS%5D+Syncope+3.0 This will require further clarifications and scope seizing. WDYT? If others have more ideas, please bring. Regards. -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
Re: [DISCUSS] Troubles with release:prepare
On 04/05/20 15:40, Francesco Chicchiriccò wrote: > On 04/05/20 14:50, Francesco Chicchiriccò wrote: >> Thanks Misagh for your reply. >> >> In my case I've run the command on the same exact platform (e.g. my own >> laptop) as I did other times including the last one before this one, e.g. >> 2.1.5 / 2.0.14. >> >> To ensure the SCM section was not causing the issue, anyway, I made this >> change on a branch of my own fork: >> >> https://github.com/ilgrosso/syncope/commit/009b3f8c760cdad1defaa0a8056f1afd221884cd >> >> Same exact error: release:prepare generated source-release zip for >> 2.1.7-SNAPSHOT, not for 2.1.7.ilgrosso as it was instructed to. >> >> I can spot the problem because a simple >> >> diff pom.xml pom.xml.releaseBackup >> >> returns no diff, meaning that pom.xml was not changed. >> >> I am going to pose the question to Maven user@ list. > FTR: > > https://lists.apache.org/thread.html/a4e00db99a094ff1e06ab19774a00413604cc22a2d8701c76c1ef9f0%40%3Cusers.maven.apache.org%3E > > As you can read there, my further investigation pointed the skipTests profile > guilty, let's see if we can get some support there. Update: some response there made me double-check if we had any local setting for maven-release-plugin, defined in ASF pom: it turns out so, hence I made some checks and finally applied the required change to all active branches. Next release process should go smoother :-) Regards. > On 04/05/20 12:23, Misagh Moayyed wrote: >>> I have run into this before, but only when: >>> >>> 1. Running a command-prompt on windows. >>> 2. Running a bash on windows, using the likes mingw or babun >>> >>> In my case, this was caused by a number of things: >>> >>> 1. Bad ssh-agent that could not communicate correctly with git. >>> 2. Somehow, the release plugin thought I was not running commands from the >>> project working directory. >>> 3. Very old versions of git. >>> 4. Weird shell issues. >>> >>> I could never truly figure out if the issue was windows-specific with >>> maven, or some other combination of things. >>> >>> --Misagh >>> >>> - Original Message - >>>> From: "Francesco Chicchiriccò" >>>> To: "dev" >>>> Sent: Sunday, May 3, 2020 4:26:01 PM >>>> Subject: Re: [DISCUSS] Troubles with release:prepare >>>> On 03/05/20 11:20, Jean-Baptiste Onofre wrote: >>>>> Hi Francesco, >>>>> >>>>> Is scm section up to date ? >>>> Yes, it is based on gitbox.apache.org and has not actually changed since >>>> 2.1.5 / >>>> 2.0.14, e.g. last time that release:prepare worked as usual. >>>> >>>> Regards. >>>> >>>>>> Le 3 mai 2020 à 09:50, Francesco Chicchiriccò a >>>>>> écrit : >>>>>> >>>>>> Hi all, >>>>>> during the recent release process for 2.0.15 and 2.1.6 I have been >>>>>> following the >>>>>> steps in [1] as usual. >>>>>> >>>>>> Unfortunately, when I arrived to launch the release:prepare step, I >>>>>> could not >>>>>> move forward as the Maven Release plugin, after asking for version to >>>>>> release >>>>>> and next development version to set, was not effectively advancing the >>>>>> POM >>>>>> files. >>>>>> >>>>>> The execution of >>>>>> >>>>>> mvn -P apache-release release:prepare -Darguments="-P all,docker >>>>>> -DbuildNumber=syncope-2.1.6" >>>>>> >>>>>> left the source files set to 2.1.6-SNAPSHOT and thus produced all >>>>>> artifacts with >>>>>> such version, not 2.1.6. (Same happened with 2.0.15). >>>>>> >>>>>> After struggling for some time, I finally came to decision to manually >>>>>> replicate >>>>>> the various steps normally performed by release:prepare [2]: >>>>>> fortunately, this >>>>>> approach was effective, and I could also continue following [1], >>>>>> including the >>>>>> release:perform step. >>>>>> >>>>>> I took some notes of the manual process in [3]. >>>>>> >>>>>> Now I was wondering: what could possibly be the reason of the bad >>>>>> functioning of >>>>>> release:prepare? I even tried with older Release plugin and Maven >>>>>> versions: no >>>>>> luck. >>>>>> >>>>>> As last resort we can always adjust [1] with content from [3], but I'd >>>>>> rather >>>>>> give release:prepare a chance. >>>>>> >>>>>> WDYT? >>>>>> Regards. >>>>>> >>>>>> [1] http://syncope.apache.org/release-process >>>>>> [2] >>>>>> http://maven.apache.org/maven-release/maven-release-plugin/examples/prepare-release.html >>>>>> [3] https://gist.github.com/ilgrosso/b2abd6674290d6fe144704dffbeda418 -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
Re: [DISCUSS] Troubles with release:prepare
On 04/05/20 14:50, Francesco Chicchiriccò wrote: > Thanks Misagh for your reply. > > In my case I've run the command on the same exact platform (e.g. my own > laptop) as I did other times including the last one before this one, e.g. > 2.1.5 / 2.0.14. > > To ensure the SCM section was not causing the issue, anyway, I made this > change on a branch of my own fork: > > https://github.com/ilgrosso/syncope/commit/009b3f8c760cdad1defaa0a8056f1afd221884cd > > Same exact error: release:prepare generated source-release zip for > 2.1.7-SNAPSHOT, not for 2.1.7.ilgrosso as it was instructed to. > > I can spot the problem because a simple > > diff pom.xml pom.xml.releaseBackup > > returns no diff, meaning that pom.xml was not changed. > > I am going to pose the question to Maven user@ list. FTR: https://lists.apache.org/thread.html/a4e00db99a094ff1e06ab19774a00413604cc22a2d8701c76c1ef9f0%40%3Cusers.maven.apache.org%3E As you can read there, my further investigation pointed the skipTests profile guilty, let's see if we can get some support there. Regards. > On 04/05/20 12:23, Misagh Moayyed wrote: >> I have run into this before, but only when: >> >> 1. Running a command-prompt on windows. >> 2. Running a bash on windows, using the likes mingw or babun >> >> In my case, this was caused by a number of things: >> >> 1. Bad ssh-agent that could not communicate correctly with git. >> 2. Somehow, the release plugin thought I was not running commands from the >> project working directory. >> 3. Very old versions of git. >> 4. Weird shell issues. >> >> I could never truly figure out if the issue was windows-specific with maven, >> or some other combination of things. >> >> --Misagh >> >> - Original Message - >>> From: "Francesco Chicchiriccò" >>> To: "dev" >>> Sent: Sunday, May 3, 2020 4:26:01 PM >>> Subject: Re: [DISCUSS] Troubles with release:prepare >>> On 03/05/20 11:20, Jean-Baptiste Onofre wrote: >>>> Hi Francesco, >>>> >>>> Is scm section up to date ? >>> Yes, it is based on gitbox.apache.org and has not actually changed since >>> 2.1.5 / >>> 2.0.14, e.g. last time that release:prepare worked as usual. >>> >>> Regards. >>> >>>>> Le 3 mai 2020 à 09:50, Francesco Chicchiriccò a >>>>> écrit : >>>>> >>>>> Hi all, >>>>> during the recent release process for 2.0.15 and 2.1.6 I have been >>>>> following the >>>>> steps in [1] as usual. >>>>> >>>>> Unfortunately, when I arrived to launch the release:prepare step, I could >>>>> not >>>>> move forward as the Maven Release plugin, after asking for version to >>>>> release >>>>> and next development version to set, was not effectively advancing the POM >>>>> files. >>>>> >>>>> The execution of >>>>> >>>>> mvn -P apache-release release:prepare -Darguments="-P all,docker >>>>> -DbuildNumber=syncope-2.1.6" >>>>> >>>>> left the source files set to 2.1.6-SNAPSHOT and thus produced all >>>>> artifacts with >>>>> such version, not 2.1.6. (Same happened with 2.0.15). >>>>> >>>>> After struggling for some time, I finally came to decision to manually >>>>> replicate >>>>> the various steps normally performed by release:prepare [2]: fortunately, >>>>> this >>>>> approach was effective, and I could also continue following [1], >>>>> including the >>>>> release:perform step. >>>>> >>>>> I took some notes of the manual process in [3]. >>>>> >>>>> Now I was wondering: what could possibly be the reason of the bad >>>>> functioning of >>>>> release:prepare? I even tried with older Release plugin and Maven >>>>> versions: no >>>>> luck. >>>>> >>>>> As last resort we can always adjust [1] with content from [3], but I'd >>>>> rather >>>>> give release:prepare a chance. >>>>> >>>>> WDYT? >>>>> Regards. >>>>> >>>>> [1] http://syncope.apache.org/release-process >>>>> [2] >>>>> http://maven.apache.org/maven-release/maven-release-plugin/examples/prepare-release.html >>>>> [3] https://gist.github.com/ilgrosso/b2abd6674290d6fe144704dffbeda418 -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
Re: [DISCUSS] Troubles with release:prepare
Thanks Misagh for your reply. In my case I've run the command on the same exact platform (e.g. my own laptop) as I did other times including the last one before this one, e.g. 2.1.5 / 2.0.14. To ensure the SCM section was not causing the issue, anyway, I made this change on a branch of my own fork: https://github.com/ilgrosso/syncope/commit/009b3f8c760cdad1defaa0a8056f1afd221884cd Same exact error: release:prepare generated source-release zip for 2.1.7-SNAPSHOT, not for 2.1.7.ilgrosso as it was instructed to. I can spot the problem because a simple diff pom.xml pom.xml.releaseBackup returns no diff, meaning that pom.xml was not changed. I am going to pose the question to Maven user@ list. Regards. On 04/05/20 12:23, Misagh Moayyed wrote: > I have run into this before, but only when: > > 1. Running a command-prompt on windows. > 2. Running a bash on windows, using the likes mingw or babun > > In my case, this was caused by a number of things: > > 1. Bad ssh-agent that could not communicate correctly with git. > 2. Somehow, the release plugin thought I was not running commands from the > project working directory. > 3. Very old versions of git. > 4. Weird shell issues. > > I could never truly figure out if the issue was windows-specific with maven, > or some other combination of things. > > --Misagh > > - Original Message - >> From: "Francesco Chicchiriccò" >> To: "dev" >> Sent: Sunday, May 3, 2020 4:26:01 PM >> Subject: Re: [DISCUSS] Troubles with release:prepare >> On 03/05/20 11:20, Jean-Baptiste Onofre wrote: >>> Hi Francesco, >>> >>> Is scm section up to date ? >> Yes, it is based on gitbox.apache.org and has not actually changed since >> 2.1.5 / >> 2.0.14, e.g. last time that release:prepare worked as usual. >> >> Regards. >> >>>> Le 3 mai 2020 à 09:50, Francesco Chicchiriccò a >>>> écrit : >>>> >>>> Hi all, >>>> during the recent release process for 2.0.15 and 2.1.6 I have been >>>> following the >>>> steps in [1] as usual. >>>> >>>> Unfortunately, when I arrived to launch the release:prepare step, I could >>>> not >>>> move forward as the Maven Release plugin, after asking for version to >>>> release >>>> and next development version to set, was not effectively advancing the POM >>>> files. >>>> >>>> The execution of >>>> >>>> mvn -P apache-release release:prepare -Darguments="-P all,docker >>>> -DbuildNumber=syncope-2.1.6" >>>> >>>> left the source files set to 2.1.6-SNAPSHOT and thus produced all >>>> artifacts with >>>> such version, not 2.1.6. (Same happened with 2.0.15). >>>> >>>> After struggling for some time, I finally came to decision to manually >>>> replicate >>>> the various steps normally performed by release:prepare [2]: fortunately, >>>> this >>>> approach was effective, and I could also continue following [1], including >>>> the >>>> release:perform step. >>>> >>>> I took some notes of the manual process in [3]. >>>> >>>> Now I was wondering: what could possibly be the reason of the bad >>>> functioning of >>>> release:prepare? I even tried with older Release plugin and Maven >>>> versions: no >>>> luck. >>>> >>>> As last resort we can always adjust [1] with content from [3], but I'd >>>> rather >>>> give release:prepare a chance. >>>> >>>> WDYT? >>>> Regards. >>>> >>>> [1] http://syncope.apache.org/release-process >>>> [2] >>>> http://maven.apache.org/maven-release/maven-release-plugin/examples/prepare-release.html >>>> [3] https://gist.github.com/ilgrosso/b2abd6674290d6fe144704dffbeda418 -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
Re: [DISCUSS] Troubles with release:prepare
On 03/05/20 11:20, Jean-Baptiste Onofre wrote: > Hi Francesco, > > Is scm section up to date ? Yes, it is based on gitbox.apache.org and has not actually changed since 2.1.5 / 2.0.14, e.g. last time that release:prepare worked as usual. Regards. >> Le 3 mai 2020 à 09:50, Francesco Chicchiriccò a écrit : >> >> Hi all, >> during the recent release process for 2.0.15 and 2.1.6 I have been following >> the steps in [1] as usual. >> >> Unfortunately, when I arrived to launch the release:prepare step, I could >> not move forward as the Maven Release plugin, after asking for version to >> release and next development version to set, was not effectively advancing >> the POM files. >> >> The execution of >> >> mvn -P apache-release release:prepare -Darguments="-P all,docker >> -DbuildNumber=syncope-2.1.6" >> >> left the source files set to 2.1.6-SNAPSHOT and thus produced all artifacts >> with such version, not 2.1.6. (Same happened with 2.0.15). >> >> After struggling for some time, I finally came to decision to manually >> replicate the various steps normally performed by release:prepare [2]: >> fortunately, this approach was effective, and I could also continue >> following [1], including the release:perform step. >> >> I took some notes of the manual process in [3]. >> >> Now I was wondering: what could possibly be the reason of the bad >> functioning of release:prepare? I even tried with older Release plugin and >> Maven versions: no luck. >> >> As last resort we can always adjust [1] with content from [3], but I'd >> rather give release:prepare a chance. >> >> WDYT? >> Regards. >> >> [1] http://syncope.apache.org/release-process >> [2] >> http://maven.apache.org/maven-release/maven-release-plugin/examples/prepare-release.html >> [3] https://gist.github.com/ilgrosso/b2abd6674290d6fe144704dffbeda418 -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
[DISCUSS] Troubles with release:prepare
Hi all, during the recent release process for 2.0.15 and 2.1.6 I have been following the steps in [1] as usual. Unfortunately, when I arrived to launch the release:prepare step, I could not move forward as the Maven Release plugin, after asking for version to release and next development version to set, was not effectively advancing the POM files. The execution of mvn -P apache-release release:prepare -Darguments="-P all,docker -DbuildNumber=syncope-2.1.6" left the source files set to 2.1.6-SNAPSHOT and thus produced all artifacts with such version, not 2.1.6. (Same happened with 2.0.15). After struggling for some time, I finally came to decision to manually replicate the various steps normally performed by release:prepare [2]: fortunately, this approach was effective, and I could also continue following [1], including the release:perform step. I took some notes of the manual process in [3]. Now I was wondering: what could possibly be the reason of the bad functioning of release:prepare? I even tried with older Release plugin and Maven versions: no luck. As last resort we can always adjust [1] with content from [3], but I'd rather give release:prepare a chance. WDYT? Regards. [1] http://syncope.apache.org/release-process [2] http://maven.apache.org/maven-release/maven-release-plugin/examples/prepare-release.html [3] https://gist.github.com/ilgrosso/b2abd6674290d6fe144704dffbeda418 -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
[CVE-2020-1961] Server-Side Template Injection on mail templates
Description: Vulnerability to Server-Side Template Injection on Mail templates enabling attackers to inject arbitrary JEXL expressions, leading to Remote Code Execution (RCE) was discovered. Severity: Important Vendor: The Apache Software Foundation Affects: 2.0.X releases prior to 2.0.15 2.1.X releases prior to 2.1.6 Solution: 2.0.X users: upgrade to 2.0.15 2.1.X users: upgrade to 2.1.6 Credit: This issue was discovered by GitHub Security Labs team member Alvaro Muñoz - https://github.com/pwntester. References: https://syncope.apache.org/security
[CVE-2020-1959] Multiple Remote Code Execution Vulnerabilities
Description: A Server-Side Template Injection was identified in Syncope enabling attackers to inject arbitrary Java EL expressions, leading to an unauthenticated Remote Code Execution (RCE) vulnerability. Apache Syncope uses Java Bean Validation (JSR 380) custom constraint validators. When building custom constraint violation error messages, they support different types of interpolation, including Java EL expressions. Therefore, if an attacker can inject arbitrary data in the error message template being passed, they will be able to run arbitrary Java code. Severity: Important Vendor: The Apache Software Foundation Affects: 2.1.X releases prior to 2.1.6 Solution: Upgrade to 2.1.6 Credit: This issue was discovered by GitHub Security Labs team member Alvaro Muñoz - https//github.com/pwntester. References: https://syncope.apache.org/security
[CVE-2019-17557] Enduser UI XSS
Description: It was found that the EndUser UI login page reflects the successMessage parameters. By this mean, a user accessing the Enduser UI could execute javascript code from URL query string. Severity: Medium Vendor: The Apache Software Foundation Affects: 2.0.X releases prior to 2.0.15 2.1.X releases prior to 2.1.6 Solution: 2.0.X users: upgrade to 2.0.15 2.1.X users: upgrade to 2.1.6 Credit: This issue was independently discovered by CNCERT songmingxuan and GitHub Security Lab team member Alvaro Muñoz - https://github.com/pwntester References: https://syncope.apache.org/security
[ANN] Apache Syncope 2.0.15
The Apache Syncope team is pleased to announce the release of Syncope 2.0.15 Apache Syncope is an Open Source system for managing digital identities in enterprise environments, implemented in Java EE technology . The release will be available within 24h from: https://syncope.apache.org/downloads Read the full change log available here: https://s.apache.org/syncope2015 Upgrading from 2.0.14? There are some notes about this process: https://s.apache.org/fra2f We welcome your help and feedback. For more information on how to report problems, and to get involved, visit the project website at http://syncope.apache.org/ The Apache Syncope Team
[ANN] Apache Syncope 2.1.6
The Apache Syncope team is pleased to announce the release of Syncope 2.1.6 Apache Syncope is an Open Source system for managing digital identities in enterprise environments, implemented in Java EE technology . The release will be available within 24h from: https://syncope.apache.org/downloads Read the full change log available here: https://s.apache.org/syncope216 Upgrading from 2.1.5? There are some notes about this process: https://s.apache.org/5esvf We welcome your help and feedback. For more information on how to report problems, and to get involved, visit the project website at http://syncope.apache.org/ The Apache Syncope Team
Re: [VOTE] Apache Syncope 2.0.15
Hi all, after 72 hours, the vote for Syncope 2.0.15 [1] *passes* with 6 PMC + 1 non-PMC votes. +1 (PMC / binding) * Fabio Martelli * Andrea Patricelli * Matteo Alessandroni * Marco Di Sabatino * Colm O hEigeartaigh * Francesco Chicchiriccò +1 (non binding) * Lorenzo Di Cola 0 -1 Thanks to everyone participating. I will now copy this release to Syncope' dist directory, promote the artifacts to the central Maven repository and publish to DockerHub. Best regards. [1] https://lists.apache.org/thread.html/rf880d11857ea2956654382997b3bb535eb6e22c4bc032c98ed0f7354%40%3Cdev.syncope.apache.org%3E -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
[RESULT] [VOTE] Apache Syncope 2.1.6
Hi all, after 72 hours, the vote for Syncope 2.1.6 [1] *passes* with 6 PMC + 1 non-PMC votes. +1 (PMC / binding) * Fabio Martelli * Jean-Baptiste Onofré * Andrea Patricelli * Matteo Alessandroni * Colm O hEigeartaigh * Francesco Chicchiriccò +1 (non binding) * Lorenzo Di Cola 0 -1 Thanks to everyone participating. I will now copy this release to Syncope' dist directory, promote the artifacts to the central Maven repository and publish to DockerHub. Best regards. [1] https://lists.apache.org/thread.html/r0f9bc463c2302faba89325f83647557ec78153342a23c98cf5fb8c9d%40%3Cdev.syncope.apache.org%3E -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
Re: OpenJDK 15 EA build 21 is now available
On 01/05/20 13:25, Rory O'Donnell wrote: > Thanks Francesco, > > I'll update the wiki, assuming all is green ? Yes, please: https://travis-ci.org/github/apache/syncope/builds/681905597 Regards. > On 01/05/2020 12:16, Francesco Chicchiriccò wrote: >> Hi Rory, >> thanks for update. >> >> FYI we are testing an update on our Travis CI setup so that tests are >> executed against JDK 11, 14 and 15EA (rather than 11, 13 and 14): >> >> https://travis-ci.org/github/apache/syncope/builds/681883192 >> >> Regards. >> >> On 01/05/20 11:04, Rory O'Donnell wrote: >>> Hi Francesco, >>> >>> OpenJDK 15 EA build 21 is now available at http://jdk.java.net/15 * >>> * >>> >>> * These early-access , open-source builds are provided under the >>> o GNU General Public License, version 2, with the Classpath >>> Exception <http://openjdk.java.net/legal/gplv2+ce.html>. >>> * Features >>> o Integrated in JDK 15 >>> + JEP 371: <http://openjdk.java.net/jeps/371> Hidden Classes >>> + JEP 372 <https://openjdk.java.net/jeps/372>: Remove the >>> Nashorn JavaScript Engine >>> + JEP 377 <https://openjdk.java.net/jeps/377>: ZGC: A Scalable >>> Low-Latency Garbage Collector >>> + JEP 378 <https://openjdk.java.net/jeps/378>: Text Blocks >>> o JEPs targeted to JDK 15 >>> + JEP 379 <https://openjdk.java.net/jeps/379>: Shenandoah: A >>> Low-Pause-Time Garbage Collector >>> * Changes in recent builds that maybe of interest: >>> o build 21 >>> + JDK-8242848 >>> <https://bugs.openjdk.java.net/browse/JDK-8242848>: Improve >>> performance of InflaterOutputStream.write() >>> + JDK-8243574 >>> <https://bugs.openjdk.java.net/browse/JDK-8243574>: >>> java.lang.invoke.InvokerBytecodeGenerator.ClassData should >>> be package-private >>> # Reported by JaCoCo >>> o build 20 >>> + JDK-8237890 >>> <https://bugs.openjdk.java.net/browse/JDK-8237890>: >>> DatagramPacket::getSocketAddress doesn't specify what >>> happens if address or port are not set [1] >>> + JDK-8228991 >>> <https://bugs.openjdk.java.net/browse/JDK-8228991>: Obsolete >>> -XX:UseAdaptiveGCBoundary [1] >>> + JDK-8242141 >>> <https://bugs.openjdk.java.net/browse/JDK-8242141>: New >>> System Properties to configure the TLS signature schemes [1] >>> + JDK-8172404 >>> <https://bugs.openjdk.java.net/browse/JDK-8172404>: Tools >>> should warn if weak algorithms are used before restricting them >>> + JDK-8238195 >>> <https://bugs.openjdk.java.net/browse/JDK-8238195>: >>> Lookup::defineClass should link the class to match the >>> specification >>> + JDK-8238358 >>> <https://bugs.openjdk.java.net/browse/JDK-8238358>: >>> Implementation of JEP 371: Hidden Classes >>> + JDK-8241749 >>> <https://bugs.openjdk.java.net/browse/JDK-8241749>: Remove >>> the Nashorn JavaScript Engine >>> + JDK-8242260 >>> <https://bugs.openjdk.java.net/browse/JDK-8242260>: Add >>> forRemoval=true to already deprecated ContentSigner >>> + JDK- >>> <https://bugs.openjdk.java.net/browse/JDK-8242008>8242008 >>> <https://bugs.openjdk.java.net/browse/JDK-8242008>: >>> SSLSession inconsistencies >>> # Reported by Netty >>> o build 19 >>> + JDK-8239594 >>> <https://bugs.openjdk.java.net/browse/JDK-8239594>: The >>> java.net.HttpClient does not override the protocols >>> specified in the SSLContext default parameters [1] >>> + JDK-8172680 >>> <https://bugs.openjdk.java.net/browse/JDK-8172680>: SunJCE >>> provider now supports SHA-3 based Hmac algorithms >>> + JDK-8237474 >>> <https://bugs.openjdk.java.net/browse/JDK-8237474>
Re: OpenJDK 15 EA build 21 is now available
Hi Rory, thanks for update. FYI we are testing an update on our Travis CI setup so that tests are executed against JDK 11, 14 and 15EA (rather than 11, 13 and 14): https://travis-ci.org/github/apache/syncope/builds/681883192 Regards. On 01/05/20 11:04, Rory O'Donnell wrote: > Hi Francesco, > > OpenJDK 15 EA build 21 is now available at http://jdk.java.net/15 * > * > > * These early-access , open-source builds are provided under the > o GNU General Public License, version 2, with the Classpath > Exception <http://openjdk.java.net/legal/gplv2+ce.html>. > * Features > o Integrated in JDK 15 > + JEP 371: <http://openjdk.java.net/jeps/371> Hidden Classes > + JEP 372 <https://openjdk.java.net/jeps/372>: Remove the > Nashorn JavaScript Engine > + JEP 377 <https://openjdk.java.net/jeps/377>: ZGC: A Scalable > Low-Latency Garbage Collector > + JEP 378 <https://openjdk.java.net/jeps/378>: Text Blocks > o JEPs targeted to JDK 15 > + JEP 379 <https://openjdk.java.net/jeps/379>: Shenandoah: A > Low-Pause-Time Garbage Collector > * Changes in recent builds that maybe of interest: > o build 21 > + JDK-8242848 > <https://bugs.openjdk.java.net/browse/JDK-8242848>: Improve > performance of InflaterOutputStream.write() > + JDK-8243574 > <https://bugs.openjdk.java.net/browse/JDK-8243574>: > java.lang.invoke.InvokerBytecodeGenerator.ClassData should > be package-private > # Reported by JaCoCo > o build 20 > + JDK-8237890 > <https://bugs.openjdk.java.net/browse/JDK-8237890>: > DatagramPacket::getSocketAddress doesn't specify what > happens if address or port are not set [1] > + JDK-8228991 > <https://bugs.openjdk.java.net/browse/JDK-8228991>: Obsolete > -XX:UseAdaptiveGCBoundary [1] > + JDK-8242141 > <https://bugs.openjdk.java.net/browse/JDK-8242141>: New > System Properties to configure the TLS signature schemes [1] > + JDK-8172404 > <https://bugs.openjdk.java.net/browse/JDK-8172404>: Tools > should warn if weak algorithms are used before restricting them > + JDK-8238195 > <https://bugs.openjdk.java.net/browse/JDK-8238195>: > Lookup::defineClass should link the class to match the > specification > + JDK-8238358 > <https://bugs.openjdk.java.net/browse/JDK-8238358>: > Implementation of JEP 371: Hidden Classes > + JDK-8241749 > <https://bugs.openjdk.java.net/browse/JDK-8241749>: Remove > the Nashorn JavaScript Engine > + JDK-8242260 > <https://bugs.openjdk.java.net/browse/JDK-8242260>: Add > forRemoval=true to already deprecated ContentSigner > + JDK- > <https://bugs.openjdk.java.net/browse/JDK-8242008>8242008 > <https://bugs.openjdk.java.net/browse/JDK-8242008>: > SSLSession inconsistencies > # Reported by Netty > o build 19 > + JDK-8239594 > <https://bugs.openjdk.java.net/browse/JDK-8239594>: The > java.net.HttpClient does not override the protocols > specified in the SSLContext default parameters [1] > + JDK-8172680 > <https://bugs.openjdk.java.net/browse/JDK-8172680>: SunJCE > provider now supports SHA-3 based Hmac algorithms > + JDK-8237474 > <https://bugs.openjdk.java.net/browse/JDK-8237474>: Default > SSLEngine should create in server role > + JDK-8240877 > <https://bugs.openjdk.java.net/browse/JDK-8240877>: NPE at > javax.swing.text.html.FormView.appendBuffer with null option > values > # reported by JOSM > > Project Loom Early-Access Builds - Build 15-loom+5-125 (2020/4/17) > > * > > These builds are intended for developers looking to "kick the tyres" > and provide feedback on using the API or by sending bug reports. > Warning: This build is based on an incomplete version of JDK 15 > <http://openjdk.java.net/projects/jdk/15/>. > > * These early-access , open-source builds are provided under the > o GNU General Public License, version 2, with the Classpath > Exception <http://openjdk.java.net/legal/gplv2+ce.html>. > * Please send feedback via e-mail to loom-...@openjdk.java.net > <mai
[VOTE] Apache Syncope 2.0.15
I've created a 2.0.15 release, with the following artifacts up for a vote: GIT source tag (2c668d5): https://gitbox.apache.org/repos/asf?p=syncope.git;a=tag;h=2c668d5 List of changes: https://gitbox.apache.org/repos/asf?p=syncope.git;a=blob;f=CHANGES;h=a09206954f5db6800555b7c2932f229026d926d4;hb=2c668d5 Staging artifacts: https://dist.apache.org/repos/dist/dev/syncope/2.0.15/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachesyncope-1063/ Staging site (yes, same as for 2.1.6, not a typo): http://syncope.apache.org/2.1.6/index.html PGP release keys (signed using 273DF287): http://www.apache.org/dist/syncope/KEYS Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Here's my +1 Regards. -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
[VOTE] Apache Syncope 2.1.6
I've created a 2.1.6 release, with the following artifacts up for a vote: GIT source tag (95f09c0): https://gitbox.apache.org/repos/asf?p=syncope.git;a=tag;h=95f09c0 List of changes: https://gitbox.apache.org/repos/asf?p=syncope.git;a=blob;f=CHANGES;h=3b84fab4fff0fa4c49ba9c30c5ee9530788c2249;hb=95f09c0 Staging artifacts: https://dist.apache.org/repos/dist/dev/syncope/2.1.6/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachesyncope-1062/ Staging site: http://syncope.apache.org/2.1.6/index.html PGP release keys (signed using 273DF287): http://www.apache.org/dist/syncope/KEYS Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Here's my +1 Regards. -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
Re: Jquery version on 2.1.x/2.0.x
On 23/04/20 15:31, Misagh Moayyed wrote: > In the same vein, I'd like to update the master branch to use jQuery 3.5.0. > While optional for now, this will soon (1-2 days) become a requirement for > the WA module to function correctly. Local testing shows that the upgrade is > innocuous. If the REST service docs showing at http://localhost:9080/syncope/ works still fine with jQuery 3.5.0, then +1 for me to go ahead and upgrade on master. Console and Enduser do use jQuery via Wicket, so no issues from those. Regards. > - Original Message - >> From: "Colm O hEigeartaigh" >> To: "dev" >> Sent: Thursday, April 23, 2020 12:10:28 PM >> Subject: Re: Jquery version on 2.1.x/2.0.x >> That's great, thanks! >> >> Colm. >> >> On Thu, Apr 23, 2020 at 8:35 AM Francesco Chicchiriccò >> wrote: >> >>> On 23/04/20 08:58, Francesco Chicchiriccò wrote: >>>> On 23/04/20 08:51, Colm O hEigeartaigh wrote: >>>>> Is it possible to update the JQuery version on 2.1.x/2.0.x to the same >>>>> version as on master? (3.4.1). It seems the existing version is >>> vulnerable >>>>> to https://nvd.nist.gov/vuln/detail/CVE-2019-11358 >>>> Hi Colm, >>>> I don't see issue. Let me do some local tests to confirm and I'll revert >>> here. >>>> Regards. >>> Found no issues, proceeded with upgrade: >>> >>> * 2_0_X: >>> https://github.com/apache/syncope/commit/8ec6c23498aa058860024a2940b8d3104b4be7d6 >>> * 2_1_X: >>> https://github.com/apache/syncope/commit/40bb5d7fe3790a5a66743d8473de0976bb2780b7 >>> >>> Regards. >>> >>> -- >>> Francesco Chicchiriccò >>> >>> Tirasa - Open Source Excellence >>> http://www.tirasa.net/ >>> >>> Member at The Apache Software Foundation >>> Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail >>> http://home.apache.org/~ilgrosso/ >>> -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
Re: Time to cut 2.1.6 / 2.0.15?
FYI I had to push an additional commit both on 2_0_X and 2_1_X to complete FOP upgrade, but now tests seem to be fine again. Regards. On 23/04/20 12:40, Colm O hEigeartaigh wrote: > Awesome, thanks :-) > > Colm. > > On Thu, Apr 23, 2020 at 11:00 AM Francesco Chicchiriccò > wrote: > >> On 23/04/20 11:41, Francesco Chicchiriccò wrote: >>> On 23/04/20 11:27, Colm O hEigeartaigh wrote: >>>> Hi Francesco, >>>> >>>> +1, but could we look at updating a few more security vulnerabilities? >>>> >>>> - CVE-2018-8036 could be fixed by updating XML Graphics 2.3 -> 2.4 >>> This can be done both for 2_0_X and 2_1_X as FOP 2.4 retains Java 7 >>> compatibility, as 2_0_X does. >>>> - CVE-2018-10237 could be fixed by updating Guava >= 2.24.x >>> According to >>> >>> https://guava.dev/ >>> >>> we need to use the Android flavor on 2_0_X, because of Java 7 compatibility. >>> Under this condition, we can upgrade all branches to latest Guava 29.0 >>> (which should only required by Swagger UI if I am not mistaking). >>> >>> I'll do the checks and push upgrades. >> Upgrades committed: >> >> 2_0_X: >> https://github.com/apache/syncope/commit/2f4b898bb71383dcaa59481ebf1c90c46a54ae22 >> 2_1_X >> <https://github.com/apache/syncope/commit/2f4b898bb71383dcaa59481ebf1c90c46a54ae222_1_X>: >> >> https://github.com/apache/syncope/commit/d2f742d2ed23ab1f9f925a02d0d3be4308b2a102 >> master: >> https://github.com/apache/syncope/commit/a48cbe79fb9babef64a4890ee3c55c3c5b81 >> >> Regards. >> >>>> On Thu, Apr 23, 2020 at 8:47 AM Francesco Chicchiriccò >>>> wrote: >>>> >>>> Hi all, >>>> resuming this thread after one week: shall we proceed with releases? >>>> >>>> Regards. >>>> >>>> On 16/04/20 14:17, Andrea Patricelli wrote: >>>> >>>> Hi all, >>>> >>>> we are going to develop last improvement that consists in a custom layout >>>> for linked account wizard. Thus we would like to wait for this last >>>> improvement before the release. >>>> >>>> Best regards, >>>> Andrea >>>> >>>> Il 14/04/20 11:58, Francesco Chicchiriccò ha scritto: >>>> >>>> Hi there, >>>> I think it's about time to start preparing Syncope 2.1.6 / 2.0.15 (several >>>> fixes and improvement, time passed since previous releases, ..). >>>> >>>> If you have any pending change or fix, please either finalize as soon as >>>> possible or let's postpone. >>>> WDYT? >>>> -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
Re: Time to cut 2.1.6 / 2.0.15?
On 23/04/20 11:41, Francesco Chicchiriccò wrote: > On 23/04/20 11:27, Colm O hEigeartaigh wrote: >> Hi Francesco, >> >> +1, but could we look at updating a few more security vulnerabilities? >> >> - CVE-2018-8036 could be fixed by updating XML Graphics 2.3 -> 2.4 > This can be done both for 2_0_X and 2_1_X as FOP 2.4 retains Java 7 > compatibility, as 2_0_X does. > >> - CVE-2018-10237 could be fixed by updating Guava >= 2.24.x > According to > > https://guava.dev/ > > we need to use the Android flavor on 2_0_X, because of Java 7 compatibility. > > Under this condition, we can upgrade all branches to latest Guava 29.0 (which > should only required by Swagger UI if I am not mistaking). > > I'll do the checks and push upgrades. Upgrades committed: 2_0_X: https://github.com/apache/syncope/commit/2f4b898bb71383dcaa59481ebf1c90c46a54ae22 2_1_X: https://github.com/apache/syncope/commit/d2f742d2ed23ab1f9f925a02d0d3be4308b2a102 master: https://github.com/apache/syncope/commit/ffffa48cbe79fb9babef64a4890ee3c55c3c5b81 Regards. >> On Thu, Apr 23, 2020 at 8:47 AM Francesco Chicchiriccò >> wrote: >> >>> Hi all, >>> resuming this thread after one week: shall we proceed with releases? >>> >>> Regards. >>> >>> On 16/04/20 14:17, Andrea Patricelli wrote: >>>> Hi all, >>>> >>>> we are going to develop last improvement that consists in a custom layout >>>> for linked account wizard. Thus we would like to wait for this last >>>> improvement before the release. >>>> >>>> Best regards, >>>> Andrea >>>> >>>> Il 14/04/20 11:58, Francesco Chicchiriccò ha scritto: >>>>> Hi there, >>>>> I think it's about time to start preparing Syncope 2.1.6 / 2.0.15 >>>>> (several fixes and improvement, time passed since previous releases, ..). >>>>> >>>>> If you have any pending change or fix, please either finalize as soon as >>>>> possible or let's postpone. >>>>> WDYT? >>>>> -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
Re: Time to cut 2.1.6 / 2.0.15?
On 23/04/20 11:27, Colm O hEigeartaigh wrote: > Hi Francesco, > > +1, but could we look at updating a few more security vulnerabilities? > > - CVE-2018-8036 could be fixed by updating XML Graphics 2.3 -> 2.4 This can be done both for 2_0_X and 2_1_X as FOP 2.4 retains Java 7 compatibility, as 2_0_X does. > - CVE-2018-10237 could be fixed by updating Guava >= 2.24.x According to https://guava.dev/ we need to use the Android flavor on 2_0_X, because of Java 7 compatibility. Under this condition, we can upgrade all branches to latest Guava 29.0 (which should only required by Swagger UI if I am not mistaking). I'll do the checks and push upgrades. Regards. > On Thu, Apr 23, 2020 at 8:47 AM Francesco Chicchiriccò > wrote: > >> Hi all, >> resuming this thread after one week: shall we proceed with releases? >> >> Regards. >> >> On 16/04/20 14:17, Andrea Patricelli wrote: >>> Hi all, >>> >>> we are going to develop last improvement that consists in a custom layout >>> for linked account wizard. Thus we would like to wait for this last >>> improvement before the release. >>> >>> Best regards, >>> Andrea >>> >>> Il 14/04/20 11:58, Francesco Chicchiriccò ha scritto: >>>> Hi there, >>>> I think it's about time to start preparing Syncope 2.1.6 / 2.0.15 (several >>>> fixes and improvement, time passed since previous releases, ..). >>>> >>>> If you have any pending change or fix, please either finalize as soon as >>>> possible or let's postpone. >>>> WDYT? >>>> -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
Re: Time to cut 2.1.6 / 2.0.15?
Hi all, resuming this thread after one week: shall we proceed with releases? Regards. On 16/04/20 14:17, Andrea Patricelli wrote: > Hi all, > > we are going to develop last improvement that consists in a custom layout for > linked account wizard. Thus we would like to wait for this last improvement > before the release. > > Best regards, > Andrea > > Il 14/04/20 11:58, Francesco Chicchiriccò ha scritto: >> Hi there, >> I think it's about time to start preparing Syncope 2.1.6 / 2.0.15 (several >> fixes and improvement, time passed since previous releases, ..). >> >> If you have any pending change or fix, please either finalize as soon as >> possible or let's postpone. >> >> WDYT? >> -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
Re: Jquery version on 2.1.x/2.0.x
On 23/04/20 08:58, Francesco Chicchiriccò wrote: > On 23/04/20 08:51, Colm O hEigeartaigh wrote: >> Is it possible to update the JQuery version on 2.1.x/2.0.x to the same >> version as on master? (3.4.1). It seems the existing version is vulnerable >> to https://nvd.nist.gov/vuln/detail/CVE-2019-11358 > Hi Colm, > I don't see issue. Let me do some local tests to confirm and I'll revert here. > > Regards. Found no issues, proceeded with upgrade: * 2_0_X: https://github.com/apache/syncope/commit/8ec6c23498aa058860024a2940b8d3104b4be7d6 * 2_1_X: https://github.com/apache/syncope/commit/40bb5d7fe3790a5a66743d8473de0976bb2780b7 Regards. -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
Re: Jquery version on 2.1.x/2.0.x
On 23/04/20 08:51, Colm O hEigeartaigh wrote: > Is it possible to update the JQuery version on 2.1.x/2.0.x to the same > version as on master? (3.4.1). It seems the existing version is vulnerable > to https://nvd.nist.gov/vuln/detail/CVE-2019-11358 Hi Colm, I don't see issue. Let me do some local tests to confirm and I'll revert here. Regards. -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
Time to cut 2.1.6 / 2.0.15?
Hi there, I think it's about time to start preparing Syncope 2.1.6 / 2.0.15 (several fixes and improvement, time passed since previous releases, ..). If you have any pending change or fix, please either finalize as soon as possible or let's postpone. WDYT? -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
Re: CONFIRM unsubscribe from dev@syncope.apache.org
mndUcPFZOsewDmg/75jszjc6hoe7wreBkJi0u8kvm6F0RpIlGk5WpCa7bljEc6Erm9 > GLON/DoYn1MSpdMZdwucairqvMK1YWg/7wI/xjgq6br5FBoLegVE8bd3Iy4SVWKUIRURBF7q > Ft3rVRUJdcmqHvCWpxDJ1VKPRDHf5szVkWXFJI0xiU6KuICWidZ9Hg3WXUsm3SePD7FtokiK > 0Y9SBzHpd9EZe8KRIHekl5gVS2Xe83GC5GvPHEXE0usYUNRDArOXqIkGUCWHZ7gzueMBcWqW > x+uxeS7bQfZZO/7ew7lIDf4gYA== > Message-ID: <200be22b-0b56-194d-83e0-892c1ec68...@apache.org> > Date: Mon, 17 Feb 2020 08:36:49 +0100 > User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 > Thunderbird/68.4.1 > MIME-Version: 1.0 > Content-Type: text/plain; charset=utf-8 > Content-Transfer-Encoding: 8bit > Content-Language: en-US > -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
Re: Few suggestions on XML content export
Hi all, FYI, on the same topic: https://issues.apache.org/jira/browse/SYNCOPE-1540 Regards. On 17/01/20 08:11, Francesco Chicchiriccò wrote: > On 16/01/20 17:37, Misagh Moayyed wrote: >> Hey Team, >> >> Wanted to share a couple of ideas with you to see if they may be worth >> following up with JIRAs and PRs: > Hi Misagh, thanks for sharing your ideas! > >> - While working on Syncope, often times I end up making a change in the >> admin console (i.e. adding a configuration parameter), and then I >> export/download the configuration XML, pick out the new changes from the >> saved XML file to put into my own version of the MasterContent.xml. This >> works great with one small issue and that is, I have to download and the >> save file. It would be more comfortable if Syncope offered a way to just >> view the XML configuration with an export option separately. > Nice one, and quite simple to implement, I would say... > >> - Similarly, it would be even better if I the admin console allowed one to >> view the XML configuration of an individual item. For example, I would be >> interested in seeing the XML representation of the new configuration >> parameter I added in the admin console, or it might be a user object, group, >> etc. > This is more complex, as it requires some logic to bind high-level objects > (as "Configuration Parameters") down to actual database tables - in this case > it would be CPlainAttr and its relationships, e.g. SyncopeSchema, > PlainSchema, CPlainAttr, CPlainAttrValue and CPlainAttrUniqueValue. > > Such logic can leverage OpenJPA's metadata information of course - still, not > trivial. > > Regards. -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
Re: Few suggestions on XML content export
On 16/01/20 17:37, Misagh Moayyed wrote: > Hey Team, > > Wanted to share a couple of ideas with you to see if they may be worth > following up with JIRAs and PRs: Hi Misagh, thanks for sharing your ideas! > - While working on Syncope, often times I end up making a change in the admin > console (i.e. adding a configuration parameter), and then I export/download > the configuration XML, pick out the new changes from the saved XML file to > put into my own version of the MasterContent.xml. This works great with one > small issue and that is, I have to download and the save file. It would be > more comfortable if Syncope offered a way to just view the XML configuration > with an export option separately. Nice one, and quite simple to implement, I would say... > - Similarly, it would be even better if I the admin console allowed one to > view the XML configuration of an individual item. For example, I would be > interested in seeing the XML representation of the new configuration > parameter I added in the admin console, or it might be a user object, group, > etc. This is more complex, as it requires some logic to bind high-level objects (as "Configuration Parameters") down to actual database tables - in this case it would be CPlainAttr and its relationships, e.g. SyncopeSchema, PlainSchema, CPlainAttr, CPlainAttrValue and CPlainAttrUniqueValue. Such logic can leverage OpenJPA's metadata information of course - still, not trivial. Regards. -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
Re: Changes in equals and hashCode contract
On 24/12/19 13:41, Dmitriy Brashevets wrote: > > Hi Dev Team. > > > > In Syncope 2_0_X branch all models that extend the > /org.apache.syncope.common.lib.AbstractBaseBean /previously used > > /org.apache.commons.lang3.builder.EqualsBuilder#reflectionEquals() > /and/org.apache.commons.lang3.builder.HashCodeBuilder#reflectionHashCode() / > in the contract of Object#equals and Object#hashCode methods. > > > > Starting from 2_1_X the equals and hashCode contract has changed and is > declared explicitly in each model. > > > > I see that it was removed to fix the performance: > https://issues.apache.org/jira/browse/SYNCOPE-1392 > <https://issues.apache.org/jira/browse/SYNCOPE-1392>. > > Do you have any charts or diagrams that can demonstrate how the performance > was improved? > > > > We widely use the *syncope-client-lib* in our code and models from this > library. And I’m afraid of that we can potentially have issues in our app, > because the contract has changed. > Hi Dmitriy, you can find a whole set of articles / comments / questions / commits on the Internet about performance troubles with reflection-based builders from Apache Commons Lang. Still, we don't have any comparison for the specific change of removing such builders in favor to their non-reflective counterparts. If your code is just depending on syncope-client-lib, then no changes are expected on your side, as all required methods were changed upstream. If your code is instead extending classes from syncope-client-lib, then you'll have to provide equals() / hashcode() (and possibly toString() as well) methods to your classes, according to the parent-child pattern as shown by [1][2], for example. Hope this clarifies. Regards. [1] https://github.com/apache/syncope/blob/2_1_X/common/lib/src/main/java/org/apache/syncope/common/lib/patch/GroupPatch.java#L124-L133 [2] https://github.com/apache/syncope/blob/2_1_X/common/lib/src/main/java/org/apache/syncope/common/lib/patch/GroupPatch.java#L147-L155 -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
Re: [PROPOSAL] Joining the OpenJDK Quality Outreach initiative
Here we go: https://wiki.openjdk.java.net/display/quality/Quality+Outreach - On 18-dec-19, at 10:53, Francesco Chicchiriccò ilgro...@apache.org wrote: > Hi all, > as I haven't received any negative feedback, I am moving forward with this > initiative. > > Keep you posted. > Regards. > > On 16/12/19 13:09, Francesco Chicchiriccò wrote: >> Hi all, >> we have the chance to join the OpenJDK Quality Outreach initiative [1]. >> >> They try to encourage popular open source projects to test their releases on >> latest OpenJDK Early Access builds (i.e. JDK 14 -ea, atm), by providing them >> with regular information describing new builds, their features, and making >> sure >> that their bug reports and feedback land in the right hands. So in that >> sense, >> being able to expand the set of projects testing against the latest JDK Early >> Access builds across many domains >> can help detect issues that would otherwise be only detected once a release >> is >> shipped. >> >> As you can see from [1], there are several ASF projects listed there, so I >> believe there is nothing preventing us to do so. >> >> Since our master branch builds are based on OpenJDK 11, I think the only >> requirement left would be to set up a CI job against OpenJDK 14-EA, which is >> definitely something we can afford. >> >> WDYT? >> Regards. >> >> [1] https://wiki.openjdk.java.net/display/quality/Quality+Outreach -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
Re: [PROPOSAL] Joining the OpenJDK Quality Outreach initiative
Hi all, as I haven't received any negative feedback, I am moving forward with this initiative. Keep you posted. Regards. On 16/12/19 13:09, Francesco Chicchiriccò wrote: > Hi all, > we have the chance to join the OpenJDK Quality Outreach initiative [1]. > > They try to encourage popular open source projects to test their releases on > latest OpenJDK Early Access builds (i.e. JDK 14 -ea, atm), by providing them > with regular information describing new builds, their features, and making > sure that their bug reports and feedback land in the right hands. So in that > sense, being able to expand the set of projects testing against the latest > JDK Early Access builds across many domains > can help detect issues that would otherwise be only detected once a release > is shipped. > > As you can see from [1], there are several ASF projects listed there, so I > believe there is nothing preventing us to do so. > > Since our master branch builds are based on OpenJDK 11, I think the only > requirement left would be to set up a CI job against OpenJDK 14-EA, which is > definitely something we can afford. > > WDYT? > Regards. > > [1] https://wiki.openjdk.java.net/display/quality/Quality+Outreach -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
[PROPOSAL] Joining the OpenJDK Quality Outreach initiative
Hi all, we have the chance to join the OpenJDK Quality Outreach initiative [1]. They try to encourage popular open source projects to test their releases on latest OpenJDK Early Access builds (i.e. JDK 14 -ea, atm), by providing them with regular information describing new builds, their features, and making sure that their bug reports and feedback land in the right hands. So in that sense, being able to expand the set of projects testing against the latest JDK Early Access builds across many domains can help detect issues that would otherwise be only detected once a release is shipped. As you can see from [1], there are several ASF projects listed there, so I believe there is nothing preventing us to do so. Since our master branch builds are based on OpenJDK 11, I think the only requirement left would be to set up a CI job against OpenJDK 14-EA, which is definitely something we can afford. WDYT? Regards. [1] https://wiki.openjdk.java.net/display/quality/Quality+Outreach -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
Re: Automating Syncope's dependency updates
Hi Misagh, it seems we have some consensus here, please go ahead and open an issue on https://issues.apache.org/jira/browse/INFRA about this topic, thanks. Regards. On 11/12/19 15:13, Francesco Chicchiriccò wrote: > Hi Misagh, > renovatebot looks interesting and worth at least to explore the possibility > to add it at project's (rather than committer's level). > > +1 to go ahead and ask Infra team about it. > Regards. > > On 11/12/19 15:00, Misagh Moayyed wrote: >> Hey Team, >> >> I suspect most know about this sort of thing, but I thought to share this >> with you: >> https://github.com/renovatebot/renovate >> >> I think this is a useful tool to allow a Github project such as Syncope to >> automatically receive dependency updates and become self sufficient. It will >> attempt to parse the project's dependencies/pom and will then begin to issue >> pull requests with relevant updates. Its schedule, update policy and >> inclusion/exclusion rules can all be controlled via a .renovate JSON file. >> >> It can run in two ways: >> >> 1- As a GitHub app, which would be installed for the Apache org on Github >> and enabled for select repositories, such as Syncope. This option requires >> coordination/permission from Apache infra, and updates are then automatic. >> >> 2- As a CLI tool, where a committer's personal access token is passed as a >> command-line argument, and the tool can run as part of CI. This option >> probably does not require anything from Apache infra [?], and updates can be >> cancelled as part of the CI job that runs the tool. >> >> I am not sure what the CLA policy would be for bots; the second option >> probably [?] covers this, as PRs are issued on behalf of the committer whose >> AT is used. Either way, it seems like we need clarification from Apache >> infra. >> >> This is an example of a pull request by the bot: >> https://github.com/Jasig/uPortal/pull/1849 >> >> This is an example of the bot's JSON configuration file: >> https://github.com/Jasig/uPortal/blob/master/renovate.json >> >> How do you feel about this? Is this a good option to pursue and follow up? >> >> The bot also has the ability to rebase PRs, and can also take over the >> merging process automatically if CI passes or other rules allow. (At some >> point in the future, I think it will also gain the ability to travel back in >> time and kill Sarah Connor [1], but that has yet to be fully verified.) >> >> --Misagh >> >> [1] https://www.wikiwand.com/en/Sarah_Connor_(Terminator) -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
Re: Automating Syncope's dependency updates
Hi Misagh, renovatebot looks interesting and worth at least to explore the possibility to add it at project's (rather than committer's level). +1 to go ahead and ask Infra team about it. Regards. On 11/12/19 15:00, Misagh Moayyed wrote: > Hey Team, > > I suspect most know about this sort of thing, but I thought to share this > with you: > https://github.com/renovatebot/renovate > > I think this is a useful tool to allow a Github project such as Syncope to > automatically receive dependency updates and become self sufficient. It will > attempt to parse the project's dependencies/pom and will then begin to issue > pull requests with relevant updates. Its schedule, update policy and > inclusion/exclusion rules can all be controlled via a .renovate JSON file. > > It can run in two ways: > > 1- As a GitHub app, which would be installed for the Apache org on Github and > enabled for select repositories, such as Syncope. This option requires > coordination/permission from Apache infra, and updates are then automatic. > > 2- As a CLI tool, where a committer's personal access token is passed as a > command-line argument, and the tool can run as part of CI. This option > probably does not require anything from Apache infra [?], and updates can be > cancelled as part of the CI job that runs the tool. > > I am not sure what the CLA policy would be for bots; the second option > probably [?] covers this, as PRs are issued on behalf of the committer whose > AT is used. Either way, it seems like we need clarification from Apache infra. > > This is an example of a pull request by the bot: > https://github.com/Jasig/uPortal/pull/1849 > > This is an example of the bot's JSON configuration file: > https://github.com/Jasig/uPortal/blob/master/renovate.json > > How do you feel about this? Is this a good option to pursue and follow up? > > The bot also has the ability to rebase PRs, and can also take over the > merging process automatically if CI passes or other rules allow. (At some > point in the future, I think it will also gain the ability to travel back in > time and kill Sarah Connor [1], but that has yet to be fully verified.) > > --Misagh > > [1] https://www.wikiwand.com/en/Sarah_Connor_(Terminator) -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
Re: AWS Promotional Credits for Open Source Projects
On 15/10/19 10:51, Misagh Moayyed wrote: > https://aws.amazon.com/blogs/opensource/aws-promotional-credits-open-source-projects > > Might this be useful for Syncope? Not sure; anyway, I think it should be Infra anyway to apply on our behalf. Regards. -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
Re: Github auto-linking to external resources
On 15/10/19 11:32, Misagh Moayyed wrote: > I sent an email to Apache infra to request turning on auto-linking to > external resources for Syncope on Github. They pointed out this JIRA: > https://issues.apache.org/jira/browse/INFRA-19276 > > Figured I'd share, if you'd like to vote for the issue or watch for updates. > > This is quite cool, though does have room for improvements to allow detection > patterns against PR titles, branches, etc. Nonetheless, here's a > demonstration: > https://twitter.com/github/status/1183789660142747648 Thanks Misagh, definitely a cool feature! INFRA-19276 already voted and watched ;-) -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
Re: [DISCUSS] How to replace ianal-maven-plugin?
On 14/10/19 13:15, Misagh Moayyed wrote: > I think the license-maven-plugin does have the ability to generate license > headers or remove/update them. Is that not the behavior we are looking for, > or do I misunderstand? As I was saying in the original email, the job that ianal-maven-plugin does is to ensure that each artifact we generate contains both LICENSE and NOTICE files, in the appropriate places; otherwise, fail the build. We are not talking about generate / remove / update license headers. Regards. > - Original Message - >> From: "Francesco Chicchiriccò" >> To: "dev" >> Sent: Friday, October 4, 2019 11:59:40 AM >> Subject: Re: [DISCUSS] How to replace ianal-maven-plugin? >> On 04/10/19 09:55, Misagh Moayyed wrote: >>>> We can only think to replace its features with something else; the job that >>>> ianal-maven-plugin does is to ensure that each artifact we generate >>>> contains >>>> both LICENSE and NOTICE files, in the appropriate places; otherwise, fail >>>> the >>>> build. >>>> >>>> Any idea about how to obtain the same feature with other plugin(s)? >>> I have used the following in the past: >>> >>> - https://github.com/Jasig/maven-notice-plugin (...which I more or less >>> maintain >>> with others) >>> - https://github.com/mycila/license-maven-plugin >>> >>> I am not sure if they are really that much better than the current plugin, >>> but >>> it's worth trying them out with Syncope. >> Are you sure that such two plugins do the job that ianal-maven-plugin does? >> As >> far as I can see, the former generates NOTICE files, while the latter does >> more >> or less the same job that Apache RAT does. -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
Re: new committer Misagh Moayyed
Welcome aboard Misagh! Your references and experience in Apereo CAS will be a great addition to Apache Syncope :-) On 11/10/19 09:25, Andrea Patricelli wrote: > The Project Management Committee (PMC) for Apache Syncope > has invited Misagh Moayyed to become a committer and we are pleased > to announce that he has accepted. > > Being a committer enables easier contribution to the > project since there is no need to go via the patch > submission process. This should enable better productivity. > Being a PMC member enables assistance with the management > and to guide the direction of the project. > > Best regards -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
Re: [DISCUSS] How to replace ianal-maven-plugin?
On 04/10/19 09:55, Misagh Moayyed wrote: >> We can only think to replace its features with something else; the job that >> ianal-maven-plugin does is to ensure that each artifact we generate contains >> both LICENSE and NOTICE files, in the appropriate places; otherwise, fail the >> build. >> >> Any idea about how to obtain the same feature with other plugin(s)? > > I have used the following in the past: > > - https://github.com/Jasig/maven-notice-plugin (...which I more or less > maintain with others) > - https://github.com/mycila/license-maven-plugin > > I am not sure if they are really that much better than the current plugin, > but it's worth trying them out with Syncope. Are you sure that such two plugins do the job that ianal-maven-plugin does? As far as I can see, the former generates NOTICE files, while the latter does more or less the same job that Apache RAT does. -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
[DISCUSS] How to replace ianal-maven-plugin?
Hi there, when doing concurrent builds with Maven, the following warning is reported multiple times: 09:18:22 [WARNING] * 09:18:22 [WARNING] * Your build is requesting parallel execution, but project * 09:18:22 [WARNING] * contains the following plugin(s) that have goals not marked * 09:18:22 [WARNING] * as @threadSafe to support parallel building. * 09:18:22 [WARNING] * While this /may/ work fine, please look for plugin updates * 09:18:22 [WARNING] * and/or request plugins be made thread-safe. * 09:18:22 [WARNING] * If reporting an issue, report it against the plugin in * 09:18:22 [WARNING] * question, not against maven-core * 09:18:22 [WARNING] * 09:18:22 [WARNING] The following plugins are not marked @threadSafe in Apache Syncope: 09:18:22 [WARNING] org.apache.rat:apache-rat-plugin:0.12 09:18:22 [WARNING] org.codehaus.mojo:ianal-maven-plugin:1.0-alpha-1 09:18:22 [WARNING] Enable debug to see more precisely which goals are not marked @threadSafe. 09:18:22 [WARNING] * After upgrading Apache RAT to 0.13 (just pushed to 2_0_X, 2_1_X and master branches), the warning above is related to ianal-maven-plugin only. The problem is that such plugin seems to be unmaintained since a long while, though several open source projects - including many here at ASF - are using it; hence, upgrading is simply not possible. We can only think to replace its features with something else; the job that ianal-maven-plugin does is to ensure that each artifact we generate contains both LICENSE and NOTICE files, in the appropriate places; otherwise, fail the build. Any idea about how to obtain the same feature with other plugin(s)? Regards. -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
Re: Running Syncope from source?
On 26/09/19 09:30, Misagh Moayyed wrote: > Thanks very much. This was quite helpful. You are welcome glad it was it. > - Original Message - >> From: "Francesco Chicchiriccò" >> To: "dev" >> Sent: Sunday, September 22, 2019 8:40:30 AM >> Subject: Re: Running Syncope from source? >> On 20-set-19, alle 11:03, Misagh Moayyed misagh.moay...@tirasa.net wrote: >> >>>> First run >>>> >>>> mvn -PskipTests,all >>>> >>>> from root folder. >>>> >>>> Then if you want to run only Syncope Core, with JPDA debug on >>>> localhost:8000: >>>> >>>> cd fit/core-refererence >>>> mvn -Pdebug,all (or -P debug if you don't want extensions) >>>> >>>> If you want to run Syncope Core and Console, with JPDA debug on >>>> localhost:8000: >>>> >>>> cd fit/console-reference >>>> mvn -Pdebug >>>> >>>> If you want to run Syncope Core, Console and Enduser, with JPDA debug on >>>> localhost:8000: >>>> >>>> cd fit/enduser-reference >>>> mvn -Pdebug >>> >>> Thank you. >>> >>> Let's say I want to run Syncope Core and Console. I can issue the required >>> commands and then set up a debugger over port 8000. All good. What I am not >>> sure about is, how do I bring up the web UI for Syncope's console to login >>> and >>> click around? (i.e. Something like http://localhost:8080/syncope-console). >> Yep, but only because the Tomcat listening port is 9080, not 8080. >> >> When starting as indicated above, the components and URLs available match the >> ones available when starting standalone or projects generated from archetype, >> e.g. >> >> http://syncope.apache.org/docs/2.1/getting-started.html#paths-and-components >> >>> Running commands from the "fit" folder structure seems to suggest that I >>> want >>> to run integration tests, where in fact, I want to be able to bring up the >>> Web >>> UI for relevant components and step into running code. >> The point is that having a full-blown Syncope environment is not easy, as >> several components have to be available - see above; since we have a setup >> for >> running integration tests which does that, we have also added the debug / >> hotswap profiles with exact purpose to "bring up the Web UI for relevant >> components and step into running code" - mainly in order to spot and squash >> bugs. >> >> Regards. -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
Re: [DISCUSS] Enabling Apache Maven wrapper
On 25/09/19 18:27, Misagh Moayyed wrote: > This is fair; no problem. Based on your list, I certainly agree that #3 and > #4 are complications best not dealt with :) Sorry for this: as a community, we cut our teeth in the ASF Incubator, striving to define a release process fully compliant with ASF legal requirements and practical enough for devs. If you are interested, there is something to read at: * https://www.apache.org/dev/#licenses * https://www.apache.org/dev/#releases Will you close the PR #122 at this point? Regards. > - Original Message - >> From: "Francesco Chicchiriccò" >> To: "dev" >> Sent: Wednesday, September 25, 2019 1:50:24 PM >> Subject: Re: [DISCUSS] Enabling Apache Maven wrapper >> On 25/09/19 10:05, Misagh Moayyed wrote: >>> Hello all, >>> >>> I have proposed a pull request [1] to enable the maven wrapper plugin for >>> Syncope. This is a plugin that allows one to build and run Syncope from >>> source >>> without having to install Maven locally. It's able to download and configure >>> the appropriate maven version automatically, and then proceeds as if it was >>> locally installed and available. >>> >>> There are a number of advantages to using the wrapper: >>> >>> - Contributors to Syncope do not have to have Maven downloaded/installed >>> locally, though nothing would prevent them from doing so. >>> - This should also prevent conflicts by allowing usage a specific install of >>> maven for Syncope, in case one might need different maven versions on their >>> system for different projects, etc. >>> - The wrapper makes sure the correct version of maven is downloaded and >>> installed, removing potential confusing around "If I do install maven >>> locally, >>> what version of Maven do I need?" >>> - The maven version is controlled by the project for CI tests, and not by >>> the CI >>> system itself, which is useful in case CI decides to change/update versions >>> or >>> goes outdated for any reason. >>> - The maintenance and overhead of the change is very minimal where future >>> changes to the maven version are controlled with a simple properties file. >>> >>> How do others feel about this change? >> Hi Misagh, >> thanks for bringing this to discussion. >> >> Honestly, I don't see much value added by this: >> >> 1. Syncope does not simply require "a specific Maven version"; rather, we run >> the maven-enforcer-plugin as part of the build, which checks Maven version is >>> = 3.50 and JDK version >> 2. We've never had troubles with CIs due to Maven version >> >> 3. Apache RAT analysis has failed on your PR [3], and I suspect this is >> because >> of non-compliant [4] or missing [5] license headers - I am wondering whether >> these can be changed, or we are not allowed simply because we are importing >> source files from a different entity than ASF >> >> 4. We would be adding binary files [6] to our source tree; this would imply >> changing our root LICENSE / NOTICE files + adjusting the source package >> management during release process >> >> 5. I haven't made an extensive search, but I could not find any usage of >> Maven >> wrapper in any of the ASF projects I am involved in >> >> 6. Why limit to Maven? Why not bundling JDK? Or operating >> system? >> >> Summarizing: I don't find enough reasons to be -1 against such proposed >> change, >> but I would rather avoid the amount of troubles it brings (especially for >> releases), as I see the trade-off with benefits extremely low. >> >> Regards. >> >>> [1] https://github.com/apache/syncope/pull/122 >> [2] https://github.com/apache/syncope/blob/master/pom.xml#L2123-L2145 >> [3] https://travis-ci.org/apache/syncope/jobs/588979502 >> [4] >> https://github.com/apache/syncope/pull/122/files#diff-59a310fc0b8358d0c91a717f18f7cfedR1-R15 >> [5] >> https://github.com/apache/syncope/pull/122/files#diff-de2bfeb3d4c0f4a0b3af8d261a26a21aR1 >> [6] >> https://github.com/apache/syncope/pull/122/files#diff-2e0bce82bce59a26bc532fbc92db892e -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
Re: [DISCUSS] Enabling Apache Maven wrapper
On 25/09/19 10:05, Misagh Moayyed wrote: > Hello all, > > I have proposed a pull request [1] to enable the maven wrapper plugin for > Syncope. This is a plugin that allows one to build and run Syncope from > source without having to install Maven locally. It's able to download and > configure the appropriate maven version automatically, and then proceeds as > if it was locally installed and available. > > There are a number of advantages to using the wrapper: > > - Contributors to Syncope do not have to have Maven downloaded/installed > locally, though nothing would prevent them from doing so. > - This should also prevent conflicts by allowing usage a specific install of > maven for Syncope, in case one might need different maven versions on their > system for different projects, etc. > - The wrapper makes sure the correct version of maven is downloaded and > installed, removing potential confusing around "If I do install maven > locally, what version of Maven do I need?" > - The maven version is controlled by the project for CI tests, and not by the > CI system itself, which is useful in case CI decides to change/update > versions or goes outdated for any reason. > - The maintenance and overhead of the change is very minimal where future > changes to the maven version are controlled with a simple properties file. > > How do others feel about this change? Hi Misagh, thanks for bringing this to discussion. Honestly, I don't see much value added by this: 1. Syncope does not simply require "a specific Maven version"; rather, we run the maven-enforcer-plugin as part of the build, which checks Maven version is >= 3.50 and JDK version 2. We've never had troubles with CIs due to Maven version 3. Apache RAT analysis has failed on your PR [3], and I suspect this is because of non-compliant [4] or missing [5] license headers - I am wondering whether these can be changed, or we are not allowed simply because we are importing source files from a different entity than ASF 4. We would be adding binary files [6] to our source tree; this would imply changing our root LICENSE / NOTICE files + adjusting the source package management during release process 5. I haven't made an extensive search, but I could not find any usage of Maven wrapper in any of the ASF projects I am involved in 6. Why limit to Maven? Why not bundling JDK? Or operating system? Summarizing: I don't find enough reasons to be -1 against such proposed change, but I would rather avoid the amount of troubles it brings (especially for releases), as I see the trade-off with benefits extremely low. Regards. > [1] https://github.com/apache/syncope/pull/122 [2] https://github.com/apache/syncope/blob/master/pom.xml#L2123-L2145 [3] https://travis-ci.org/apache/syncope/jobs/588979502 [4] https://github.com/apache/syncope/pull/122/files#diff-59a310fc0b8358d0c91a717f18f7cfedR1-R15 [5] https://github.com/apache/syncope/pull/122/files#diff-de2bfeb3d4c0f4a0b3af8d261a26a21aR1 [6] https://github.com/apache/syncope/pull/122/files#diff-2e0bce82bce59a26bc532fbc92db892e -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
Re: Running Syncope from source?
On 20-set-19, alle 11:03, Misagh Moayyed misagh.moay...@tirasa.net wrote: >> First run >> >> mvn -PskipTests,all >> >> from root folder. >> >> Then if you want to run only Syncope Core, with JPDA debug on localhost:8000: >> >> cd fit/core-refererence >> mvn -Pdebug,all (or -P debug if you don't want extensions) >> >> If you want to run Syncope Core and Console, with JPDA debug on >> localhost:8000: >> >> cd fit/console-reference >> mvn -Pdebug >> >> If you want to run Syncope Core, Console and Enduser, with JPDA debug on >> localhost:8000: >> >> cd fit/enduser-reference >> mvn -Pdebug > > > Thank you. > > Let's say I want to run Syncope Core and Console. I can issue the required > commands and then set up a debugger over port 8000. All good. What I am not > sure about is, how do I bring up the web UI for Syncope's console to login and > click around? (i.e. Something like http://localhost:8080/syncope-console). Yep, but only because the Tomcat listening port is 9080, not 8080. When starting as indicated above, the components and URLs available match the ones available when starting standalone or projects generated from archetype, e.g. http://syncope.apache.org/docs/2.1/getting-started.html#paths-and-components > Running commands from the "fit" folder structure seems to suggest that I want > to run integration tests, where in fact, I want to be able to bring up the Web > UI for relevant components and step into running code. The point is that having a full-blown Syncope environment is not easy, as several components have to be available - see above; since we have a setup for running integration tests which does that, we have also added the debug / hotswap profiles with exact purpose to "bring up the Web UI for relevant components and step into running code" - mainly in order to spot and squash bugs. Regards. -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
Re: [DISCUSS] Object versioning
base >>> * User should have the possibility to see a diff of what has changed >>> like per connectors and resources configurations. >>> * User should have the possibility to restore a certain value (or the >>> whole object?) >>> * User should be able to see, at least (in a first release), an >>> history of what has changed on data (e.g. name: foo -> bar) and who >>> did the change and when. >>> * User should be able to query by changed data like users who are >>> subject to "name" change in a certain period (not so useful, maybe). >>> >>> There are some usefu l open source libraries that support objects >>> versioning like JaVers [2] or [3], but I'm not sure if this last one >>> fits all the needs above. If you have any other proposal please don't >>> hesitate to attach it in this thread. >>> >>> WDYT? >>> >>> Have a nice day, >>> Andrea >>> >>> [1] https://issues.apache.org/jira/browse/SYNCOPE-1145 >>> >>> [2] https://javers.org/ >>> >>> [3] >>> https://docs.spring.io/spring-data/jpa/docs/current/reference/html/#jpa.auditing >>> -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
[ANN] Apache Syncope 2.0.14
The Apache Syncope team is pleased to announce the release of Syncope 2.0.14 Apache Syncope is an Open Source system for managing digital identities in enterprise environments, implemented in Java EE technology . The release will be available within 24h from: https://syncope.apache.org/downloads Read the full change log available here: https://s.apache.org/syncope2014 Upgrading from 2.0.13? There are some notes about this process: https://s.apache.org/kz33c We welcome your help and feedback. For more information on how to report problems, and to get involved, visit the project website at http://syncope.apache.org/ The Apache Syncope Team
Re: [DISCUSS] Remove deb packages for Syncope 3.'0
FYI: https://issues.apache.org/jira/browse/SYNCOPE-1495 On 14/09/19 07:01, Francesco Chicchiriccò wrote: > Hi all, > I would like to propose to remove the deb packages from master branch / 3.0, > for some reasons: > > 1. it's difficult to produce packages compatible at the same time with > Debian, Ubuntu and other derivatives: for example, ATM Debian stable has a > tomcat9 package while Ubuntu LTS is still on tomcat8 > > 2. in branches 2_0_X and 2_1_X deb packages are used to build Docker images > but on master this has changed: since all is now based on Spring Boot, Docker > images were changed as consequence > > 3. there are new components on master (SRA, Keymaster, WA, .. [1]) that would > deserve new deb packages, but I don't think the effort is worthwhile, > especially given the reason above > > 4. deb packages were originally meant as a fast and straightforward way to > get Syncope properly deployed, but I think that nowadays Docker images (with > Docker Compose and Kubernetes samples) serve better such purpose, on more > platforms > > If there are no objections, I'll proceed with removal next week. > > Regards. > > [1] > https://cwiki.apache.org/confluence/display/SYNCOPE/%5BDISCUSS%5D+Syncope+3.0 > -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
[RESULT] [VOTE] Apache Syncope 2.0.14
Hi all, after 72 hours, the vote for Syncope 2.0.14 [1] *passes* with 6 PMC + 1 non-PMC votes. +1 (PMC / binding) * Jean-Baptiste Onofré * Marco Di Sabatino * Fabio Martelli * Andrea Patricelli * Matteo Alessandroni * Francesco Chicchiriccò +1 (non binding) * Lorenzo Di Cola 0 -1 Thanks to everyone participating. I will now copy this release to Syncope' dist directory, promote the artifacts to the central Maven repository and publish to DockerHub. Best regards. [1] https://lists.apache.org/thread.html/8bcd27d3740d663f45932826284ef33eef6ebf1c7a1b11e06172ba51@%3Cdev.syncope.apache.org%3E -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
[RESULT] [VOTE] Apache Syncope 2.1.5
Hi all, after 72 hours, the vote for Syncope 2.1.5 [1] *passes* with 6 PMC + 1 non-PMC votes. +1 (PMC / binding) * Jean-Baptiste Onofré * Marco Di Sabatino * Fabio Martelli * Andrea Patricelli * Matteo Alessandroni * Francesco Chicchiriccò +1 (non binding) * Lorenzo Di Cola 0 -1 Thanks to everyone participating. I will now copy this release to Syncope' dist directory, promote the artifacts to the central Maven repository and publish to DockerHub. Best regards. [1] https://lists.apache.org/thread.html/3bc354bcedf9e6a7195730d6995e0c001ec93f723213a2a17156a35b@%3Cdev.syncope.apache.org%3E -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
[DISCUSS] Remove deb packages for Syncope 3.'0
Hi all, I would like to propose to remove the deb packages from master branch / 3.0, for some reasons: 1. it's difficult to produce packages compatible at the same time with Debian, Ubuntu and other derivatives: for example, ATM Debian stable has a tomcat9 package while Ubuntu LTS is still on tomcat8 2. in branches 2_0_X and 2_1_X deb packages are used to build Docker images but on master this has changed: since all is now based on Spring Boot, Docker images were changed as consequence 3. there are new components on master (SRA, Keymaster, WA, .. [1]) that would deserve new deb packages, but I don't think the effort is worthwhile, especially given the reason above 4. deb packages were originally meant as a fast and straightforward way to get Syncope properly deployed, but I think that nowadays Docker images (with Docker Compose and Kubernetes samples) serve better such purpose, on more platforms If there are no objections, I'll proceed with removal next week. Regards. [1] https://cwiki.apache.org/confluence/display/SYNCOPE/%5BDISCUSS%5D+Syncope+3.0 -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
[VOTE] Apache Syncope 2.0.14
I've created a 2.0.14 release, with the following artifacts up for a vote: GIT source tag (69e2f5e): https://gitbox.apache.org/repos/asf?p=syncope.git;a=tag;h=69e2f5e List of changes: https://gitbox.apache.org/repos/asf?p=syncope.git;a=blob;f=CHANGES;h=7dc51c6bc15408ff852f7107160ef21fe556a141;hb=69e2f5e Staging artifacts: https://dist.apache.org/repos/dist/dev/syncope/2.0.14/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachesyncope-1061/ Staging site (yes, same as for 2.1.5, not a typo): http://syncope.apache.org/2.1.5/index.html PGP release keys (signed using 273DF287): http://www.apache.org/dist/syncope/KEYS Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Here's my +1 Regards. -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
[VOTE] Apache Syncope 2.1.5
I've created a 2.1.5 release, with the following artifacts up for a vote: GIT source tag (51e08a2): https://gitbox.apache.org/repos/asf?p=syncope.git;a=tag;h=51e08a2 List of changes: https://gitbox.apache.org/repos/asf?p=syncope.git;a=blob;f=CHANGES;h=3b84fab4fff0fa4c49ba9c30c5ee9530788c2249;hb=51e08a2 Staging artifacts: https://dist.apache.org/repos/dist/dev/syncope/2.1.5/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachesyncope-1060/ Staging site: http://syncope.apache.org/2.1.5/index.html PGP release keys (signed using 273DF287): http://www.apache.org/dist/syncope/KEYS Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Here's my +1 Regards. -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
Re: I am having trouble setting up my build system for Syncope and need some help on deployment.
Hi, FYI customizing Docker is indeed possible up to a certain extent, but it requires some Docker skills, of course. Moreover, building the Maven project generated from archetype and deploying to an external Java EE container, with a real database is ordinary stuff. If you still have troubles with that, I'd suggest to try again. Regards. On 11/09/19 13:43, Dalrymple, Philip wrote: > Thanks, I have another fire to put out today (well two as a matter of fact) > > I do need to work with the source as I need to add two functions that are > missing > (and maybe another) but the reason that I went to that now is that I could not > get enough customization in the docker build (it did work) and could not get > the Maven from archetype to start in tomcat. I may take another shot at that. > > just F.Y.I. > > 1) a simple command line too to generate at least a BCRYPT admin/root password > (needed because for production it is a very bad idea to have a default > password and > the ASE-1 hash is not a good one anymore) > > 2) support in the password I think it is rules to check each > password for Entropy > (at least an estimate using zxcvbn) I was thinking of adding this as an > option to the > default password rules. > > In addition I may look at getting Argon2 as another hash into Syncope. > > > -- > This email, and any files transmitted with it, are confidential > and intended solely for the use of the individual or entity to > whom they are addressed. If you have received this email in error, > please advise postmas...@mdtsoft.com <mailto:postmas...@mdtsoft.com>. > > 3480 Preston Ridge Road > Suite 450 > Alpharetta, GA 30005 > > Philip W. Dalrymple III > MDT Software - Automation Management Company > +1 678 297 1001 > Fax +1 678 297 1003 > > > From: Francesco Chicchiriccò > Sent: Wednesday, September 11, 2019 3:54 > To: dev@syncope.apache.org > Subject: Re: I am having trouble setting up my build system for Syncope and > need some help on deployment. > > Hi Philip, > first of all, I am glad that Syncope "looks like just what we need for > Identity management". > > I noticed that you are quite struggling, let's see if I can help. > > 1. you don't need to build Syncope from source, even if you need to > customize / extend it for your own deployment (e.g. adding your own > code): generating a Maven project from archetype [1] is exactly for that > purpose; moreover, all tutorials / documentation / deployment > instructions you will find are meant for this setup, not for build from > sources > > 2. nevertheless, if you plan to contribute fixes and / or features, > setting up your local build environment is anyway a good idea, but take > also into account that: > > * Syncope 2.1 is the current stable release, actively maintained and > released from the 2_1_X git branch, requires JDK 8 > * Syncope 3.0 is next major release, currently under high development > and subjected to changes; currently in the master git branch, requires > JDK 11 > > Having said that, in case of contributions, I'd say it would be easier > to start with 2_1_X / JDK 8 > > 3. To deploy into an external Tomcat, just keep following Andrea's > advice [2]; again, please note how this is meant for a Maven project > generated from archetype > > HTH > Regards. > > [1] http://syncope.apache.org/docs/2.1/getting-started.html#create-project > [2] > https://lists.apache.org/thread.html/589a13b641be2a3d29f2524c88216dc32eeb711e3ecf75e5574b1e7b@%3Cuser.syncope.apache.org%3E > > On 10/09/19 15:54, Dalrymple, Philip wrote: >> I am new to Syncope but it looks like just what we need for Identity >> management. I will have to >> make a couple of changes but first I thought to get a system up and running >> without any changes. >> So I first tried the docker deployment, I was able to get this up but any >> tweaking was real hard >> (as the notes said it would be) so I shifted to the Maven method noted in >> the getting started guide, >> this did not go well so, given that I wanted to make some changes to the >> code anyway I next >> build a new VM (Centos 7) and got java 12 and the latest Maven and the >> latest Tomcat up and >> running on it. I forked the GitHub repo and then made a working copy on my >> Getlab server so >> that the pull requests will be clean (I will Meld any code changes back to >> the forked repo from >> my working that will be good in the default project). >> >> I did find three things that I did need. >> >> 1) the options for Maven changed with version of Java after 8 (in the up &g
Plan to release 2.0.14 / 2.1.5 soon
Hi there, since we have already 16 issues done for 2.0.14 [1] and 21 for 2.1.5 [2], I'd propose to postpone the remaining to later versions and to start the release process [3] for both in the next days. Any objection / showstopper ? Regards. [1] https://issues.apache.org/jira/projects/SYNCOPE/versions/12345389 [2] https://issues.apache.org/jira/projects/SYNCOPE/versions/12345390 [3] http://syncope.apache.org/release-process -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
Re: I am having trouble setting up my build system for Syncope and need some help on deployment.
Hi Philip, first of all, I am glad that Syncope "looks like just what we need for Identity management". I noticed that you are quite struggling, let's see if I can help. 1. you don't need to build Syncope from source, even if you need to customize / extend it for your own deployment (e.g. adding your own code): generating a Maven project from archetype [1] is exactly for that purpose; moreover, all tutorials / documentation / deployment instructions you will find are meant for this setup, not for build from sources 2. nevertheless, if you plan to contribute fixes and / or features, setting up your local build environment is anyway a good idea, but take also into account that: * Syncope 2.1 is the current stable release, actively maintained and released from the 2_1_X git branch, requires JDK 8 * Syncope 3.0 is next major release, currently under high development and subjected to changes; currently in the master git branch, requires JDK 11 Having said that, in case of contributions, I'd say it would be easier to start with 2_1_X / JDK 8 3. To deploy into an external Tomcat, just keep following Andrea's advice [2]; again, please note how this is meant for a Maven project generated from archetype HTH Regards. [1] http://syncope.apache.org/docs/2.1/getting-started.html#create-project [2] https://lists.apache.org/thread.html/589a13b641be2a3d29f2524c88216dc32eeb711e3ecf75e5574b1e7b@%3Cuser.syncope.apache.org%3E On 10/09/19 15:54, Dalrymple, Philip wrote: > I am new to Syncope but it looks like just what we need for Identity > management. I will have to > make a couple of changes but first I thought to get a system up and running > without any changes. > So I first tried the docker deployment, I was able to get this up but any > tweaking was real hard > (as the notes said it would be) so I shifted to the Maven method noted in the > getting started guide, > this did not go well so, given that I wanted to make some changes to the code > anyway I next > build a new VM (Centos 7) and got java 12 and the latest Maven and the latest > Tomcat up and > running on it. I forked the GitHub repo and then made a working copy on my > Getlab server so > that the pull requests will be clean (I will Meld any code changes back to > the forked repo from > my working that will be good in the default project). > > I did find three things that I did need. > > 1) the options for Maven changed with version of Java after 8 (in the up > stream building.xml) > > 2) the patch program is needed to build one of the sub modules (again in up > stream building.xml) > > 3) docker is needed for the PostgreSQL test (and I assume to docker one but I > have not tried that yet) > AND even on unix (where it is in general not needed) you have to set > DOCKER_HOST to unix://localhost > If it makes sense I will update builing.xml with that note, I have not > yet. > > After these changes I was able to build but could not do so following the > instructions in building.xml. I had to > first do: > mvn -PskipTests,all > then: > mvn -PskipTests,install > > then I could do a > > mvn clean install > > as much as I wanted without error. (I have been making small changes to > the code and testing). > > I am not sure what might be wrong with my build setup, how can I trouble > shoot this? > > Second. Once I have a good source build what is the best way to deploy it to > a tomcat > running on this (and another) system? -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
Re: Reorganizing Travis CI with build stages
On 09/09/19 16:07, Misagh Moayyed wrote: >> thanks for bringing this item to discussion: improving our CI power is >> definitely more than welcome. >> >> I would say there are several requirements one might want to handle: > All sounds excellent. Once the proper structure is in, it would be quite easy > to add jobs to cover all additional test cases. I'll need some help to figure > out how to run the IT tests for different systems and specifically separate > them per job to minimize time, but those would be trivial to include and > massage once the basics start working. > > ...and to answer Andrea's question: yes absolutely! integrations tests can > totally be added for all sorts of systems. The IT tests that CAS runs mostly > pull down docker images and run tests against predefined addresses and ports > to connect to an external system. Syncope can more or less follow the same > approach, or we could also take advantage of the test-containers project to > simplify the setup; that would be a good experiment. (No such thing as > test-containers existed at the time CAS started doing this) > >> I am not sure about [3] - we should ask ASF Infra to issue such a >> request, in case, as they are the actual owner of the GitHub repo. > That's totally possible and in fact, it might simpler than that. One could > just send an email to Travis CI, asking them to increase the timeout. They > are super quick to respond, and all related changes are done on their end; > nothing to modify as far as the GH repo goes for Syncope. Still, ASF Infra > might be better to submit that email...and we might not even need it, if > individual jobs can run under the current 50-minute timeout. > > I'll create a JIRA to track this with possible sub-tasks and will get to > work. This will take a number of tries, so apologies beforehand for the > noise. Thanks for this Misagh. Maybe, in order to minimize the "noise" and possibly to allow you to run faster, what do you think of experimenting with Travis CI on your own fork? You'd only have to change the notification address as throw-away change. WDYT? -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
Re: Reorganizing Travis CI with build stages
On 09/09/19 11:37, Misagh Moayyed wrote: > Hello all, > > In discussing git workflows with Francesco, I have learned that the Travis CI > process is not actually running a comprehensive set of tests and checks (such > as checkstyle, etc) that would be valuable for pull requests and > contributors, possibly because such jobs take a long time, more than what is > allowed by Travis CI. I'd like to propose to reorganize the CI build process > to take advantage of the build stages feature [1]. This [2] demonstrates an > example where a given build is broken down into multiple stages, each of > which has numerous jobs. > > A key thing to note in this configuration, as I understand, is that a given > CI build can have an *unlimited* number of stages, each with an unlimited > number of jobs. While each job cannot exceed a certain timeout value [3], the > collective overall build stage can go on forever in theory. Also, stages do > depend on each other such that failures in one would halt the build. A > typical example would be: "Run the build, and if everything compiles, run > tests, then publish snapshots, etc". > > I think this is quite valuable for contributors who, specially, work on > multiple JIRAs at the same time. A sample workflow is to add a change, do > some sanity tests and then push to let CI run the full build suite. While > it's busy kicking off the build, one could switch to the next JIRA to repeat > the same process, and as such hop back and forth between branches and JIRAs > to parallelize work activity. Ultimately, the CI is the canonical reference > for all changes and this would avoid the problem of "but it works on my > machine" and of course, saves quite a bit of time. (A full build for me takes > about 20-30 minutes, if the stars align). > > How do folks feel about this proposal? Hi Misagh, thanks for bringing this item to discussion: improving our CI power is definitely more than welcome. I would say there are several requirements one might want to handle: 1. run the straight "mvn clean install" one normally performs on his / her laptop, which involves RAT checks, Checkstyle, modernizer, etc, all unit and integration tests 1a. run integration tests with different content types [5] 2. run the Admin UI tests [4], currently not run by default under fit/core-reference 3. run the Enduser UI tests ([4] for master), currently not run by default under fit/core-reference 4. run integration tests under the other supported Java EE containers (besides Tomcat) [6] 5. run integration tests with the other supported DBMSes (besides H2) [7] 6. run integration tests with Elasticsearch - not documented but available 7. run SAML 2.0 / OpenID Connect 1.0 login tests - not documented but available (only master) I am not saying we should cover all above in one shot, just reporting the full requirements; I would be happy even with only (1), a great progress anyway compared to the current situation. I am not sure about [3] - we should ask ASF Infra to issue such a request, in case, as they are the actual owner of the GitHub repo. Regards. > [1] https://docs.travis-ci.com/user/build-stages/ > [2] https://travis-ci.org/apereo/cas/builds/581042662 > [3] The good folks at Travis CI in the past have been kind enough to increase > the timeout from 50 minutes to 180 minutes and they might be willing to make > the same change for syncope. Larger tasks need to be broken down to separate > jobs, of course. > [4] http://syncope.apache.org/building#All_integration_tests > [5] http://syncope.apache.org/building#Other_Content-Type_values > [6] http://syncope.apache.org/building#Java_EE_containers > [7] http://syncope.apache.org/building#DBMSes -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
Re: [SYNCOPE-163] PR #103 design notes
On 03/09/19 09:05, Misagh Moayyed wrote: > Hi Marco, > > I have begun to learn and study SYNCOPE-163 for which there is this pending > PR by you: > https://github.com/apache/syncope/pull/103 > > Would you mind putting together a few notes/paragraphs on the high level > design, abstractions and intention of each component on the wiki? Or if there > is one already, could you point me to it please? Any sort of documentation > that you can spare on the design would be most welcome, as time allows. Hi Misagh, welcome to Apache Syncope. Marco, I created https://cwiki.apache.org/confluence/display/SYNCOPE/Authentication+features which should be the right place where to put your thoughts about the authentication features to implement in Syncope 3.0. Thanks! Regards. -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
Re: Travis-CI reports not reaching dev@ list
On 09/08/19 09:58, sebb wrote: Should be set now. I've temporarily added myself as a moderator in case there are issues. It seems it already worked, cool: https://lists.apache.org/thread.html/b599c5d9c583c6f58de7f51c47fb91903f54928281c2f3a4652bcce2@%3Cdev.syncope.apache.org%3E Thanks! On Fri, 9 Aug 2019 at 08:42, Francesco Chicchiriccò wrote: On 09/08/19 00:00, sebb wrote: It looks like the Travis-CI reports are not making it to the dev@ list. This is perhaps because each one has to be moderated, which is a pain. If so, and the project would like to receive the reports, I am currently testing a solution which avoids the need to moderate each one. See: https://issues.apache.org/jira/browse/INFRA-18843 If you would like Syncope to be included in the test, please let me know. Thanks! Hi Sebb, this would be great, thanks. Regards. -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
Re: Travis-CI reports not reaching dev@ list
On 09/08/19 00:00, sebb wrote: It looks like the Travis-CI reports are not making it to the dev@ list. This is perhaps because each one has to be moderated, which is a pain. If so, and the project would like to receive the reports, I am currently testing a solution which avoids the need to moderate each one. See: https://issues.apache.org/jira/browse/INFRA-18843 If you would like Syncope to be included in the test, please let me know. Thanks! Hi Sebb, this would be great, thanks. Regards. -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
Demo URLs updated
Hi all, I just wanted to follow-up some upgrade activities performed by infra, which resulted in updating our demo URLs, now based at https://syncope-vm.apache.org/ See http://syncope.apache.org/demo for full reference. Regards. -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
Re: Want to contribute
On 07/05/19 18:49, Atul More wrote: Hi, As per the provided guideline, I need to submit the signed CLA. To whom I need to send those documents? If you follow the links from [1], you'll land to http://www.apache.org/licenses/#clas then http://www.apache.org/licenses/contributor-agreements.html#clas The one you are required to submit is ICLA (e.g. as individual); on that page there is a paragraph "HOW-TO: SUBMITTING LICENSE AGREEMENTS AND GRANTS" where it is stated: When submitting by email, please fill the form with a pdf viewer, then print, sign, scan all pages into a single pdf file, and attach the pdf file to an email to secret...@apache.org. HTH Regards. On Thu, May 2, 2019 at 10:44 PM Atul More wrote: Hi, Sure, I will start look into it. On Thu, May 2, 2019 at 3:32 PM Francesco Chicchiriccò wrote: On 01/05/19 17:52, Atul More wrote: Hi, I am interested to work on Syncope project especially on development side. I have total 13+ years of experience in Java/Spring and related technologies. Also experience with IAM/GRC domain(basic). Just want to understand, how can I do that? From where to start? Hi Atul, welcome to Apache Syncope! I'd suggest you take first a look at [1] and to submit your ICLA, since you intend to contribute. Then, you can get yourself acquainted with using Syncope [2][3], the build process [4] and finally start looking at issues on JIRA [5]. Some ideas for first-time contributions can be: * SYNCOPE-1332 - to review the whole code on master branch in order to see if there are language features from Java 11 we are not currently using * SYNCOPE-1403 - to enhance the Netbeans IDE plugin in order to use the actual classpath when building Groovy classes * SYNCOPE-1218 - to enhance the Admin Console with capability to persist the Topology layout across sessions (and users, possibly) * SYNCOPE-1465 - to augment the information stored about Task and Report execution * SYNCOPE-1466 - to augment the metadata stored about Users, Groups and Any Objects Feel free to ask, should you need any guidance. Regards. [1] http://syncope.apache.org/contributing [2] http://syncope.apache.org/docs/getting-started.html [3] http://syncope.apache.org/docs/reference-guide.html [4] http://syncope.apache.org/building [5] https://issues.apache.org/jira/projects/SYNCOPE/issues/ -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
Re: Want to contribute
On 01/05/19 17:52, Atul More wrote: Hi, I am interested to work on Syncope project especially on development side. I have total 13+ years of experience in Java/Spring and related technologies. Also experience with IAM/GRC domain(basic). Just want to understand, how can I do that? From where to start? Hi Atul, welcome to Apache Syncope! I'd suggest you take first a look at [1] and to submit your ICLA, since you intend to contribute. Then, you can get yourself acquainted with using Syncope [2][3], the build process [4] and finally start looking at issues on JIRA [5]. Some ideas for first-time contributions can be: * SYNCOPE-1332 - to review the whole code on master branch in order to see if there are language features from Java 11 we are not currently using * SYNCOPE-1403 - to enhance the Netbeans IDE plugin in order to use the actual classpath when building Groovy classes * SYNCOPE-1218 - to enhance the Admin Console with capability to persist the Topology layout across sessions (and users, possibly) * SYNCOPE-1465 - to augment the information stored about Task and Report execution * SYNCOPE-1466 - to augment the metadata stored about Users, Groups and Any Objects Feel free to ask, should you need any guidance. Regards. [1] http://syncope.apache.org/contributing [2] http://syncope.apache.org/docs/getting-started.html [3] http://syncope.apache.org/docs/reference-guide.html [4] http://syncope.apache.org/building [5] https://issues.apache.org/jira/projects/SYNCOPE/issues/ -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
[ANN] Apache Syncope 2.0.13
The Apache Syncope team is pleased to announce the release of Syncope 2.0.13 Apache Syncope is an Open Source system for managing digital identities in enterprise environments, implemented in Java EE technology . The release will be available within 24h from: http://syncope.apache.org/downloads.html Read the full change log available here: https://s.apache.org/syncope2013 Upgrading from 2.0.12? There are some notes about this process: https://s.apache.org/8U9F We welcome your help and feedback. For more information on how to report problems, and to get involved, visit the project website at http://syncope.apache.org/ The Apache Syncope Team
[ANN] Apache Syncope 2.1.4
The Apache Syncope team is pleased to announce the release of Syncope 2.1.4 Apache Syncope is an Open Source system for managing digital identities in enterprise environments, implemented in Java EE technology . The release will be available within 24h from: http://syncope.apache.org/downloads.html Read the full change log available here: https://s.apache.org/syncope214 Upgrading from 2.1.3? There are some notes about this process: https://s.apache.org/wvOo We welcome your help and feedback. For more information on how to report problems, and to get involved, visit the project website at http://syncope.apache.org/ The Apache Syncope Team
[RESULT] [VOTE] Apache Syncope 2.0.13
Hi all, after 72 hours, the vote for Syncope 2.0.13 [1] *passes* with 6 PMC + 1 non-PMC votes. +1 (PMC / binding) * Fabio Martelli * Andrea Patricelli * Matteo Alessandroni * Jean-Baptiste Onofré * Marco Di Sabatino * Francesco Chicchiriccò +1 (non binding) * Lorenzo Di Cola 0 -1 Thanks to everyone participating. I will now copy this release to Syncope' dist directory, promote the artifacts to the central Maven repository and publish to DockerHub. Best regards. [1] https://lists.apache.org/thread.html/70686f9211afed1bffa88a3c0e3850f7b936240eefe6323efd3773c4@%3Cdev.syncope.apache.org%3E -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
[RESULT] [VOTE] Apache Syncope 2.1.4
Hi all, after 72 hours, the vote for Syncope 2.1.4 [1] *passes* with 6 PMC + 2 non-PMC votes. +1 (PMC / binding) * Fabio Martelli * Marco Di Sabatino * Andrea Patricelli * Matteo Alessandroni * Jean-Baptiste Onofré * Francesco Chicchiriccò +1 (non binding) * Dima Ayash * Lorenzo Di Cola 0 -1 Thanks to everyone participating. I will now copy this release to Syncope' dist directory, promote the artifacts to the central Maven repository and publish to DockerHub. Best regards. [1] https://lists.apache.org/thread.html/abaee465696b7d5e2b2fea6d438bfad4876b3bc569ce9926d7d63f35@%3Cdev.syncope.apache.org%3E -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
[VOTE] Apache Syncope 2.0.13
I've created a 2.0.13 release, with the following artifacts up for a vote: GIT source tag (3dc84c4): https://gitbox.apache.org/repos/asf?p=syncope.git;a=tag;h=3dc84c4 List of changes: https://gitbox.apache.org/repos/asf?p=syncope.git;a=blob;f=CHANGES;h=87754582fba4d1ed082c784053b5ad921b5b7bdb;hb=3dc84c4 Staging artifacts: https://dist.apache.org/repos/dist/dev/syncope/2.0.13/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachesyncope-1059/ Staging site (yes, same as for 2.1.4, not a typo): http://syncope.apache.org/2.1.4/index.html PGP release keys (signed using 273DF287): http://www.apache.org/dist/syncope/KEYS Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Here's my +1 Regards. -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
[VOTE] Apache Syncope 2.1.4
I've created a 2.1.4 release, with the following artifacts up for a vote: GIT source tag (0cd9070): https://gitbox.apache.org/repos/asf?p=syncope.git;a=tag;h=0cd9070 List of changes: https://gitbox.apache.org/repos/asf?p=syncope.git;a=blob;f=CHANGES;h=dba9102ecf4561644c9c109cd06df30550891c2e;hb=0cd9070 Staging artifacts: https://dist.apache.org/repos/dist/dev/syncope/2.1.4/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachesyncope-1058/ Staging site: http://syncope.apache.org/2.1.4/index.html PGP release keys (signed using 273DF287): http://www.apache.org/dist/syncope/KEYS Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Here's my +1 Regards. -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
Re: Preparing Syncope 2.0.13 and 2.1.4
Here we go again: new vote for OpenJPA 3.1.0 is in progress [5]. Regards. On 10/04/19 08:27, Francesco Chicchiriccò wrote: FYI the vote for OpenJPA 3.1.0 was canceled [4] - a nasty issue was found: the plan is to fix it ASAP and start a new vote; fingers crossed. Regards. On 08/04/19 09:41, Francesco Chicchiriccò wrote: Hi all, later this week, once OpenJPA 3.1.0 - whose VOTE is in progress [1] - is released, I would like to start the release process for Syncope 2.0.13 [2] and 2.1.4 [3], both full of fixes and enhancements. Please raise any warning against that, should you have some, thanks! Regards. [1] https://lists.apache.org/thread.html/b24817b3b4b20992abff05dbba858f7a8a5fad46fbde8509df95910f@%3Cdev.openjpa.apache.org%3E [2] https://issues.apache.org/jira/issues/?jql=statusCategory%20%3D%20done%20AND%20project%20%3D%2012313120%20AND%20fixVersion%20%3D%2012344848%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC [3] https://issues.apache.org/jira/issues/?jql=statusCategory%20%3D%20done%20AND%20project%20%3D%2012313120%20AND%20fixVersion%20%3D%2012344849%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC [4] https://lists.apache.org/thread.html/672b2ecc249ddc22c51ce1097e168b6af0a51f408e7e882ecea016e0@%3Cdev.openjpa.apache.org%3E [5] https://lists.apache.org/thread.html/cace26c8842a6cbd193631cc64230ea14b02b81fe8ff8438342bf12b@%3Cdev.openjpa.apache.org%3E -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
Re: Preparing Syncope 2.0.13 and 2.1.4
FYI the vote for OpenJPA 3.1.0 was canceled [4] - a nasty issue was found: the plan is to fix it ASAP and start a new vote; fingers crossed. Regards. On 08/04/19 09:41, Francesco Chicchiriccò wrote: Hi all, later this week, once OpenJPA 3.1.0 - whose VOTE is in progress [1] - is released, I would like to start the release process for Syncope 2.0.13 [2] and 2.1.4 [3], both full of fixes and enhancements. Please raise any warning against that, should you have some, thanks! Regards. [1] https://lists.apache.org/thread.html/b24817b3b4b20992abff05dbba858f7a8a5fad46fbde8509df95910f@%3Cdev.openjpa.apache.org%3E [2] https://issues.apache.org/jira/issues/?jql=statusCategory%20%3D%20done%20AND%20project%20%3D%2012313120%20AND%20fixVersion%20%3D%2012344848%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC [3] https://issues.apache.org/jira/issues/?jql=statusCategory%20%3D%20done%20AND%20project%20%3D%2012313120%20AND%20fixVersion%20%3D%2012344849%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC [4] https://lists.apache.org/thread.html/672b2ecc249ddc22c51ce1097e168b6af0a51f408e7e882ecea016e0@%3Cdev.openjpa.apache.org%3E -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
Preparing Syncope 2.0.13 and 2.1.4
Hi all, later this week, once OpenJPA 3.1.0 - whose VOTE is in progress [1] - is released, I would like to start the release process for Syncope 2.0.13 [2] and 2.1.4 [3], both full of fixes and enhancements. Please raise any warning against that, should you have some, thanks! Regards. [1] https://lists.apache.org/thread.html/b24817b3b4b20992abff05dbba858f7a8a5fad46fbde8509df95910f@%3Cdev.openjpa.apache.org%3E [2] https://issues.apache.org/jira/issues/?jql=statusCategory%20%3D%20done%20AND%20project%20%3D%2012313120%20AND%20fixVersion%20%3D%2012344848%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC [3] https://issues.apache.org/jira/issues/?jql=statusCategory%20%3D%20done%20AND%20project%20%3D%2012313120%20AND%20fixVersion%20%3D%2012344849%20ORDER%20BY%20priority%20DESC%2C%20key%20ASC -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
Re: Some questions
Hi Filipe, please send your future questions to u...@syncope.apache.org, thanks. You can find my replies embedded below. Regards. On 27/03/19 13:46, Filipe Silva wrote: Hi Using 2.14-SNAPSHOT: 1- the execution task lists are ordered by ascending "start date" but it would be more useful, for us, if it was descending. Is a configuration for that available? Task executions are ordered by default by end date descending [1]. Anyway, there is no configuration option for changing such setting, you'll need to override the class in your local project if you want to have this different setting by default. 2- Some rows in notification tasks list do not have the start date with value (even when the status is [EXECUTED]), why? The [EXECUTED] status is set in case the task was executed but the trace level does not allow for storing executions. 3- Shouldn't a notification task get the status [NOT SEND] when it doesn't have a Recipient? The general process is that the NotificationManager wakes up according to the "notificationjob.cronExpression" configuration parameter and create all the Notification Tasks that can be created. If there are no recipients, the code [2] does not create any task. 4- Is it possible to send the TRACE info (depending in the trace level of a notification) in the notification email sent? No, not possible currently, you'll need to extend [3] and provide your own NotificationManager implementation. 5- Is it possible to send the Event type info in the notification email sent? Or do I have to make a notifications for each event type I want to be notified? Same as above, you need to extend [3]. [1] https://github.com/apache/syncope/blob/2_1_X/client/console/src/main/java/org/apache/syncope/client/console/tasks/ExecutionsDirectoryPanel.java#L176 [2] https://github.com/apache/syncope/blob/2_1_X/core/provisioning-java/src/main/java/org/apache/syncope/core/provisioning/java/job/notification/DefaultNotificationJobDelegate.java#L166 [3] https://github.com/apache/syncope/blob/2_1_X/core/provisioning-java/src/main/java/org/apache/syncope/core/provisioning/java/job/notification/DefaultNotificationJobDelegate.java#L166 -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
[ANN] Apache Syncope 2.1.3
The Apache Syncope team is pleased to announce the release of Syncope 2.1.3 Apache Syncope is an Open Source system for managing digital identities in enterprise environments, implemented in Java EE technology . The release will be available within 24h from: http://syncope.apache.org/downloads.html Read the full change log available here: https://s.apache.org/syncope213 Upgrading from 2.1.2? There are some notes about this process: https://s.apache.org/NPtt We welcome your help and feedback. For more information on how to report problems, and to get involved, visit the project website at http://syncope.apache.org/ The Apache Syncope Team
[ANN] Apache Syncope 2.0.12
The Apache Syncope team is pleased to announce the release of Syncope 2.0.12. Apache Syncope is an Open Source system for managing digital identities in enterprise environments, implemented in Java EE technology . The release will be available within 24h from: http://syncope.apache.org/downloads.html Read the full change log available here: https://s.apache.org/syncope2012 Upgrading from 2.0.11? There are some notes about this process: https://s.apache.org/pCzv We welcome your help and feedback. For more information on how to report problems, and to get involved, visit the project website at http://syncope.apache.org/ The Apache Syncope Team
[RESULT] [VOTE] Apache Syncope 2.1.3
[Re-sending with corrected subject] Hi all, after 72 hours, the vote for Syncope 2.1.3 [1] *passes* with 6 PMC + 2 non-PMC votes. +1 (PMC / binding) * Fabio Martelli * Andrea Patricelli * Jean-Baptiste Onofré * Marco Di Sabatino * Matteo Alessandroni * Francesco Chicchiriccò +1 (non binding) * Lorenzo Di Cola * Dima Ayash 0 -1 Thanks to everyone participating. I will now copy this release to Syncope' dist directory, promote the artifacts to the central Maven repository and publish to DockerHub. Best regards. [1] https://lists.apache.org/thread.html/eef4e4986e0eaff0fc2a643f2490cafee71678458dfd5440c24c0eb2@%3Cdev.syncope.apache.org%3E -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
[RESULT] [VOTE] Apache Syncope 2.0.12
Hi all, after 72 hours, the vote for Syncope 2.0.12 [1] *passes* with 6 PMC + 2 non-PMC votes. +1 (PMC / binding) * Fabio Martelli * Andrea Patricelli * Jean-Baptiste Onofré * Marco Di Sabatino * Matteo Alessandroni * Francesco Chicchiriccò +1 (non binding) * Lorenzo Di Cola * Dima Ayash 0 -1 Thanks to everyone participating. I will now copy this release to Syncope' dist directory, promote the artifacts to the central Maven repository and publish to DockerHub. Best regards. [1] https://lists.apache.org/thread.html/2cc134d9732f03a364b95ac3158cd016991cf2ed559b99fd590cfa49@%3Cdev.syncope.apache.org%3E -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
Re: [VOTE] Apache Syncope 2.1.3
Hi all, after 72 hours, the vote for Syncope 2.1.3 [1] *passes* with 6 PMC + 2 non-PMC votes. +1 (PMC / binding) * Fabio Martelli * Andrea Patricelli * Jean-Baptiste Onofré * Marco Di Sabatino * Matteo Alessandroni * Francesco Chicchiriccò +1 (non binding) * Lorenzo Di Cola * Dima Ayash 0 -1 Thanks to everyone participating. I will now copy this release to Syncope' dist directory, promote the artifacts to the central Maven repository and publish to DockerHub. Best regards. [1] https://lists.apache.org/thread.html/eef4e4986e0eaff0fc2a643f2490cafee71678458dfd5440c24c0eb2@%3Cdev.syncope.apache.org%3E -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
[VOTE] Apache Syncope 2.0.12
I've created a 2.0.12 release, with the following artifacts up for a vote: GIT source tag (770e696): https://gitbox.apache.org/repos/asf?p=syncope.git;a=tag;h=770e696 List of changes: https://gitbox.apache.org/repos/asf?p=syncope.git;a=blob;f=CHANGES;h=7babeeaef0ecc2f7a4da042fde9e387a035ceced;hb=770e696 Staging artifacts: https://dist.apache.org/repos/dist/dev/syncope/2.0.12/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachesyncope-1057/ Staging site (yes, same as for 2.1.3, not a typo): http://syncope.apache.org/2.1.3/index.html PGP release keys (signed using 273DF287): http://www.apache.org/dist/syncope/KEYS Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Here's my +1 Regards. -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
[VOTE] Apache Syncope 2.1.3
I've created a 2.1.3 release, with the following artifacts up for a vote: GIT source tag (5121355): https://gitbox.apache.org/repos/asf?p=syncope.git;a=tag;h=5121355 List of changes: https://gitbox.apache.org/repos/asf?p=syncope.git;a=blob;f=CHANGES;h=7babeeaef0ecc2f7a4da042fde9e387a035ceced;hb=5121355 Staging artifacts: https://dist.apache.org/repos/dist/dev/syncope/2.1.3/ Maven staging repo: https://repository.apache.org/content/repositories/orgapachesyncope-1056/ Staging site: http://syncope.apache.org/2.1.3/index.html PGP release keys (signed using 273DF287): http://www.apache.org/dist/syncope/KEYS Vote will be open for 72 hours. [ ] +1 approve [ ] +0 no opinion [ ] -1 disapprove (and reason why) Here's my +1 Regards. -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
[DISCUSS] Apache Syncope 3.0
Hi all, I think it's time to start discussing about the architecture [1] and features [2] we want to include in Apache Syncope 3.0. There are several open points, please share your thoughts, thanks. Regards. [1] https://cwiki.apache.org/confluence/display/SYNCOPE/%5BDISCUSS%5D+Apache+Syncope+3.0+Architecture [2] https://cwiki.apache.org/confluence/display/SYNCOPE/%5BDISCUSS%5D+Access+Management+features -- Francesco Chicchiriccò Tirasa - Open Source Excellence http://www.tirasa.net/ Member at The Apache Software Foundation Syncope, Cocoon, Olingo, CXF, OpenJPA, PonyMail http://home.apache.org/~ilgrosso/
