Re: [cas-dev] _csrf meta tags are blank

Hi, This kind of tokens are generally checked on POST requests to protect against CSRF attacks. I don't think they are used currently. Thus, being blank is not a problem. We should certainly remove these meta tags if we don't use them. There is already a specific login ticket mechanism for the

Re: [cas-dev] stable cas server build with oauth support

Hi, OAuth support exists since CAS 3.5. So you can use the latest stable release: version 4.1.4. Thanks. Best regards, Jérôme 2016-01-24 23:20 GMT+01:00 Kunal Sinha : > Hello Team, > > I am working on integrating CAS server for our authentication services. We > need oauth 2

Re: [cas-dev] 4.2 GA release planning

+1 2016-03-16 9:03 GMT+01:00 Misagh Moayyed : > Team, > > > > Proposing that we cut the 4.2 GA release early next week. (We are actually > a few days behind schedule per the milestone date). With 3 release > candidates behind, I think it’s in a good-enough shape to go out.

Re: [cas-dev] Re: Dependency issue for 5.0.0.M3

cas/development/installation/JSON-Service-Management.html > > > -- > Misagh > > From: Jérôme LELEU <lel...@gmail.com> <lel...@gmail.com> > Reply: Jérôme LELEU <lel...@gmail.com> <lel...@gmail.com> > Date: August 1, 2016 at 9:11:48 PM > To: Mi

Re: [cas-dev] CAS 5 RC2 proposal

Hi, -0 I still have: https://github.com/apereo/cas/issues/1976 to do and I've encountered issues with token authentication support and error handling in case of authentication delegation. Thanks. Best regards, Jérôme 2016-09-09 20:06 GMT+02:00 Dmitriy Kopylenko : > +1

[cas-dev] [cas-announce] Java CAS client v3.6.0

The Java CAS client v3.6.0 is released: https://github.com/apereo/java-cas-client/releases/tag/cas-client-3.6.0 -- You received this message because you are subscribed to the Google Groups "CAS Developer" group. To unsubscribe from this group and stop receiving emails from it, send an email to

[cas-dev] Release Announcement: CAS Security Patches

Hi, Please see: https://apereo.github.io/2020/10/14/gauthvuln/ Thanks. Best regards, Jérôme -- You received this message because you are subscribed to the Google Groups "CAS Developer" group. To unsubscribe from this group and stop receiving emails from it, send an email to

Re: [cas-dev] CAS 4.0.0: Will it support OIDC (OpenID Connect) features

Hi, pac4j v1.7.0 is an old version based on an old version of the Nimbus SDK without default support for Keycloak. So, even if it is feasible, you'll need customisations to make it work. As I said on the pac4j mailing list, I highly recommend upgrading the CAS server. Thanks. Best regards,

[cas-dev] Re: [cas-announce] Apereo Paris 21 & ESUP-Days 31

And you'll talk about CAS at 11h20 ;-) Le mar. 2 févr. 2021 à 07:42, Misagh a écrit : > The ESUP-Portail Consortium and the Apereo Foundation are pleased to > invite you to the eighth edition of the ESUP-Days/Apereo Paris event > that will take place on February 2, 2021. Due to the pandemic >

Re: [cas-dev] Better protocol differentiation

t but I would need to be 300% sure this > is necessary, and cannot be fixed/improved in any other "easy" way, > and that it should start with a concrete use case or problem that can > be produced in #1. > > On Fri, Jun 11, 2021 at 10:42 AM Jérôme LELEU wrote: > > > >

Re: [cas-dev] Better protocol differentiation

Hi, No, it's fixed with the latest snapshot. Thanks. Best regards, Jérôme Le ven. 18 juin 2021 à 09:43, Misagh a écrit : > I might have been a few steps ahead of you. Are you still seeing this > with the latest snapshots? > > On Mon, Jun 14, 2021 at 8:09 PM Jérôme LELEU wrote

Re: [cas-dev] Better protocol differentiation

vice is only authorized for use with a specific > list of protocols, and an attempt to access the registered service (e.g., > by findServiceBy(Service)) for an unauthorized protocol returns null. > > Dan > > Dan Ellentuck > Columbia University I.T. > > > On Mon,

[cas-dev] Different versions in BOM vs WAR

Hi, I notice that the versions in the BOM are sometimes different from the versions in the WAR. For example, in version 6.4.0-RC5, there is: - guava 30.0-jre in the BOM - guava 30.1.1-jre in the WAR. Shouldn't both versions be the same? Thanks. Best regards, Jérôme -- You received this

Re: [cas-dev] Different versions in BOM vs WAR

onally, upgrade guava to the latest. > > On Fri, Jul 2, 2021 at 5:38 PM Jérôme LELEU wrote: > > > > Sorry but I'm not sure to follow you. > > > > Let's take my guava example on master. > > > > In the gradle.properties, I see: guavaVersion=30.0-jre > > &

Re: [cas-dev] Different versions in BOM vs WAR

Hi, OK. I agree. So what's the fix? Changing the BOM generation process or changing the dependency versions in the gradle.properties? Thanks. Best regards, Jérôme Le ven. 2 juil. 2021 à 11:11, Misagh a écrit : > They should. > > On Fri, Jul 2, 2021 at 1:10 PM Jérôme LELEU wrote: &

Re: [cas-dev] Different versions in BOM vs WAR

, Jérôme Le ven. 2 juil. 2021 à 14:52, Misagh a écrit : > Only when you introduce your own dependencies. Otherwise, it needs to > be fixed at the source where you have to look for the source of > conflict. > > On Fri, Jul 2, 2021 at 4:51 PM Jérôme LELEU wrote: > > &

Re: [cas-dev] Different versions in BOM vs WAR

Hi, Thanks for the feedback. So this is something we must do manually when needed. Best regards, Jérôme Le ven. 2 juil. 2021 à 14:33, Misagh a écrit : > The latter. You'd have to see where the conflict comes from first. > > On Fri, Jul 2, 2021 at 4:31 PM Jérôme LELEU wrote: &

[cas-dev] Re: [cas-user] very slow ticket delivery on CAS 6.6 & redis ticket registry

x in a UniqueTicketIdGenerator, the way > HostNameBasedUniqueTicketIdGenerator suffixes with hostname > (but it may be hard to do...) > > cu > > On 28/10/2022 11:13, Jérôme LELEU wrote: > > Hi, > > > > Thanks for raising the point. > > >

[cas-dev] pac4j v6: development started

Hi, I just started the development of pac4j v6. CAS v7 will use pac4j v6. So the ETA is *February 2023*, just before CAS v7. It is based on *JDK 17*. The deprecated *pac4j-saml*, *pac4j-cas* and *pac4j-springboot *modules are removed. The *pac4j-saml-opensamlv5* module is renamed as

Re: [cas-dev] Re: [cas-user] very slow ticket delivery on CAS 6.6 & redis ticket registry

me: 4 ms > > > > Performance are now very good for the incoming 6.6.3 release. > > > > Thanks. > > Best regards, > > Jérôme > > > > > > Le mardi 15 novembre 2022 à 07:48:36 UTC+1, leleuj a écrit : > >> > >> EXCELLENT! > >>

Re: [cas-dev] Re: [cas-user] very slow ticket delivery on CAS 6.6 & redis ticket registry

gt; > > > Thank you Jérôme. I'll take a look. > > > > -- Misagh > > > > On Wed, Nov 9, 2022, 2:39 PM Jérôme LELEU wrote: > >> > >> Hi, > >> > >> I have made a Redis performance test between v6.5.9 and v7.0.0-RC1 and > figur

Re: [cas-dev] Re: [cas-user] very slow ticket delivery on CAS 6.6 & redis ticket registry

some sort of POC to demonstrate this idea? The > other solutions are non-starters. I'll also poke around to see what > can be done to speed things up. > > On Fri, Oct 28, 2022 at 4:30 PM Jérôme LELEU wrote: > > > > Hi, > > > > Moving the discussion to the dev mailin

Re: [cas-dev] Re: [cas-user] very slow ticket delivery on CAS 6.6 & redis ticket registry

Hi, Yes, double indexing is harder than simple indexing as the second operation may fail and you should revert the first one (transactional aspect). If we did that for all tickets, we would double the size of the keys, but not the size of the database though. And maybe we should have two

Re: [cas-dev] Re: [cas-user] very slow ticket delivery on CAS 6.6 & redis ticket registry

average time: v6.5.9: 1000 logins -> Average time: 3 ms 1 logins -> Average time: 3 ms v7.0.0-RC1: 1000 logins -> Average time: 22 ms 1 logins -> Average time: 195 ms So indeed, I notice a big performance issue. Do you need more information? Thanks. Best regards, Jérôme

Re: [cas-dev] Re: [cas-user] very slow ticket delivery on CAS 6.6 & redis ticket registry

as well. Did you change something else in addition to the cache? Thanks. Best regards, Jérôme Le jeu. 10 nov. 2022 à 17:47, Jérôme LELEU a écrit : > Sure. I will test that on Monday (tomorrow is off in France :-) > > Le jeu. 10 nov. 2022 à 17:27, Misagh a écrit : > >> Could I

Re: [cas-dev] Re: [cas-user] very slow ticket delivery on CAS 6.6 & redis ticket registry

EXCELLENT! Le mar. 15 nov. 2022 à 04:54, Misagh a écrit : > > > > On Mon, Nov 14, 2022, 4:58 PM Jérôme LELEU wrote: > >> Hi, >> >> I have made new tests. >> >> With the new implementation, I have experienced Redis crashes, but I'm >> not sure