Re: Release 0.14.0 Status

2017-12-06 Thread larry mccay
All - Open JIRAs for 0.14.0 are down to a couple doc issues. I have started to spin a new RC. Please hold off on any commits to the v0.14.0 branch at this point. I will announce the RC availability for testing once it is ready. thanks, --larry On Wed, Nov 22, 2017 at 10:05 AM, larry mccay wr

Re: Release 0.14.0 Status

2017-11-22 Thread larry mccay
Thanks, Jérôme - I hadn't actually noticed that setConfig is setting the singleton too! On Wed, Nov 22, 2017 at 4:47 AM, Jérôme LELEU wrote: > Hi, > > It's great to see you're fully autonomous with pac4j now! > > You certainly already know that, but to stay away from the ConfigSingleton, > you m

Re: Release 0.14.0 Status

2017-11-22 Thread Jérôme LELEU
Hi, It's great to see you're fully autonomous with pac4j now! You certainly already know that, but to stay away from the ConfigSingleton, you must use the setConfigOnly method instead of the setConfig method (on the SecurityFilter component). Am I'm still there if you have issues/questions with

Re: Release 0.14.0 Status

2017-11-21 Thread larry mccay
Thanks, Jérôme - we are already on those versions! Looks like we need a final cleanup task to divorce us from the ConfigSingleton. On Tue, Nov 21, 2017 at 12:59 PM, Jérôme LELEU wrote: > Hi, > > You should use j2e-pac4j v3.0.0 and pac4j v2.1.0. > > Keep me posted if you have any issue. > > Thank

Re: Release 0.14.0 Status

2017-11-21 Thread Jérôme LELEU
Hi, You should use j2e-pac4j v3.0.0 and pac4j v2.1.0. Keep me posted if you have any issue. Thanks. Best regards, Jérôme On Tue, Nov 21, 2017 at 5:55 PM, larry mccay wrote: > All - > > I have identified a couple other blockers for this release and they are > delaying the creation of a new RC

Release 0.14.0 Status

2017-11-21 Thread larry mccay
All - I have identified a couple other blockers for this release and they are delaying the creation of a new RC. Pac4J is becoming more and more important as KnoxSSO is being used more. * KNOX-1119 is intended to acquire a meaningful identity attribute from the resulting UserProfile rather than