he web
> server hosting your application.
>
> Ray
> --
> *From:* cas-...@apereo.org on behalf of Tomi
> Karlstedt
> *Sent:* May 20, 2025 00:23
> *To:* CAS Community
> *Subject:* [cas-user] Delegated SAML2 logins create huge tickets
>
> You don'
Hi,
We enabled a SAML2 integration on our CAS 7 server. The CAS server acts as
a service provider. For whatever reason, the integration is creating huge
tickets into the database and eventually producing OutOfMemoryErrors on the
CAS server. We checked that one of the serialized tickets looks ot
Hello,
We tried configuring our CAS 7 as SAML service provider with
*cas.authn.pac4j.saml[0].callback-url-type* set to *PATH_PARAMETER*. We do
this since one of our IDPs seems to be picky about query parameters. As far
as I can tell, configuring CAS like this creates a new callback endpoint
li
CAS 6.5 version, but it may give you some guidance how to do it in
> CAS 7. There are also modifications to use eIDAS, but they should be easily
> identified and do not mix or depend on the WAYF code.
>
> Regards,
>
> Michal V.
>
> On 4/10/25 13:27, Tomi Karlstedt wrote:
>
Hi,
We're replacing an old Spring/OpenSAML service provider microservice with
an existing CAS implementation as the SP. This means we need to integrate
our CAS 7.0 with a Shibboleth instance using SAML. The authentication
delegation works fine. CAS sends user to the Shibboleth which then picks
his property on the same page,
> cas.sso.allow-missing-service-parameter
>
> Ray
>
> On Thu, 2023-01-12 at 00:38 -0800, 'Tomi Karlstedt' via CAS Community
> wrote:
>
> Notice: This message was sent from outside the University of Victoria
> email system. Please
Hi,
Our implementation uses the CAS login form to log users in and checks
username/password from a separate service. We're adding an optional MFA for
users and we want to save the chosen MFA provider per user into the same
service that handles usernames and passwords.
There's a way to trigger
