HI,
I am integrating CAS 5.3.8 with web application. In web application' s
web.xml I am specifying proxycallbackurl as
https://localhost:8443/webapplication/proxycallback but it's showing
"proxyCallback could not be reached or authenticated".
Kindly assist
--
- Website: https://apereo.githu
We have applications that are using CAS protocol as well as CAS REST
protocol. For applications that are using the CAS REST protocol (specially
mobile application) we want to check if the user is already log in to CAS
sso. If so then we want to let the user authenticate. We are using a
memca
Thank you, this does the trick!
There's some other concern around how to appropriately accomplish this in
my reply on the other group. I meant to put that all here instead of over
there, but what's sent is sent so I'll leave it be. If anyone else finds
this thread and needs to see that context,
Hello,
So after some testing with the DefaultTicketRegistryCleaner on CAS 5.1.9 with
JPA ticket registry we have had to disable the DefaultTicketRegistryCleaner
because it would take long to remove tickets from the Oracle Database. We
noticed that it would take some time to attempt a cleanup
Nam,
Logging docs are here
https://apereo.github.io/cas/5.3.x/installation/Logging.html
While CAS is running, you can edit log4j2.xml (in deploy location) and changes
will take effect in 5 seconds.
Ray
On Thu, 2019-03-28 at 13:16 +0700, nam nguyễn wrote:
I still don't understand. Do you have
Still haven't found a resolution for this either.
On Thu, Mar 28, 2019 at 7:15 AM Rob Blais wrote:
> Has there been any resolution to this? I've run into the exact same
> problem with CAS 6.0.1 and 6.1.0-RC2. It worked fine in 5.2.x and previous
> versions I've used.
>
> On Tuesday, September
Has there been any resolution to this? I've run into the exact same
problem with CAS 6.0.1 and 6.1.0-RC2. It worked fine in 5.2.x and previous
versions I've used.
On Tuesday, September 25, 2018 at 3:00:47 PM UTC-4, magicserverpixiedust
wrote:
>
> If I start cas.war and wait for it to complet
Hi,
This change was tested and works in pac4j applications. The issue in CAS is
that there are conflicts regarding the Nimbus versions libraries.
Add this to make it work:
com.nimbusds
nimbus-jose-jwt
6.0.2
com.nimbusds
oauth2-oidc-sdk
6.5
Thanks.
Best regards,
Jér