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 pac4j ;-) Thanks. Best regards, Jérôme On Tue, Nov 21, 2017 at 9:35 PM, larry mccay <[email protected]> wrote: > 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 <[email protected]> wrote: > >> 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 <[email protected]> wrote: >> >>> 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 just the ID. This is especially >>> important for the indirect authentication clients in pac4j such as SAML, >>> OAuth, OpenID. >>> >>> * KNOX-1120 is intended to complete the migration to pac4j 2.1.0 which >>> should include eliminating the use of ConfigSingleton class which makes it >>> difficult to have multiple pac4j protected topologies in the same instance >>> - as they step on each other. >>> >>> I expect these to take a few days to resolve and am hoping to get a new >>> RC spin up by the end of the week. >>> >>> Thanks, >>> >>> --larry >>> >> >> >
