cas version: v5.3.16
cas-server-support-token-core / JWTTokenTicketBuilder[1] use cas-client
TicketValidator to validate service ticket, which issue an http request to
the server itself.
That's not good, there is a performance impact.
I think it'll be better if server validate the service t
Hi Fernando,
We use something like this:
==
"accessStrategy": {
"@class":
"org.apereo.cas.services.DefaultRegisteredServiceAccessStrategy",
"delegatedAuthenticationPolicy" : {
"@class" :
"org.apereo.cas.services.DefaultRegisteredService
Hello, the following warning is coming out in my logs:
*
[org.apereo.cas.services.DefaultRegisteredServiceDelegatedAuthenticationPolicy]
- *
**
The problem is that the production log is filling up very quickly for this
issue.
I have my service configured as follows:
{
"@class": "org.aper
Hello,
I developped a non interactive authentication module which works as
expected. I tested when a /cas/login is sent with renew parameter if CAS
ignores silent authentication and force authentication from login page but
not. I was wondering If anyone has the same behaviour with another "non
I should've specified that I am using the SAML1.0 and SAML2.0 CAS 6.3.2
gradle implementations. It seems like other SAML2.0 services are also
having trouble. I've seen errors with SLO null pointers:
2021-06-03 11:16:29,550 ERROR
[org.apereo.cas.logout.slo.BaseSingleLogoutServiceMessageHandler