Hi all,
After installing and configuring CAS to work with our DegreeWorks install,
I'm seeing that the application is unable to login with CAS despite having
a service registry. Is there some formatting issues with our registry entry?
For reference, we're running tomcat 10, cas 7.0.0, jdk17.
Hello there,
I am using CAS 5.1.X, and facing this problem intermittently. Can you
please suggest some solution?
In my case CAS is working as SP in delegated auth mode and Azure is as
IDP. So when authentication is done on Azure, i get the SAML response.
After that the control flow goes to
Hello Apereo Community,
I wanted to share *three upcoming events* those working in and with open
source software across higher education won't want to miss. Details below.
Hope to see you there,
Patrick
*_Apereo
Miguel,
This sounds like what Jérôme talked about in this thread
https://groups.google.com/a/apereo.org/g/cas-user/c/fNZ82V32sio/m/RKhi5VQCAQAJ?utm_medium=email_source=footer
Ray
On Fri, 2023-06-09 at 05:03 -0700, Miguel Martínez De Espronceda Cámara wrote:
Notice: This message was sent from
Andrea,
It is possible that property names have changed across versions.
To get a file with all cas properties:
./gradlew exportConfigMetadata
Then search that file for your property. eg:
You have:
cas.authn.attributeRepository.defaultAttributesToRelease
In version 6.5 it is:
Hi everyone,
I'm working on my Apereo CAS installation to upgrade it from 6.0.x to
the last 6.6.x. My installation has a number of services which must be
accessed on a role-based policy basis and the are configured like this:
/"accessStrategy" : {//
// "@class" :
Dear all,
I am reaching out regarding the use of CAS 6.6.8 for serving SAML2
requests. Currently, we are in the process of migrating our Google
integration from the deprecated Google-native integration to standard SAML2
endpoints. To provide some context, the deprecated module was designed to
