Do you have the attributes in your management config? I have them in
cas.authn.attributeRepository.stub.attributes. A few versions ago the mgmt
webapp would throw an exception without them. Maybe now these options are
greyed out because of this?
Von: cas-user@apereo.org [mailto:cas-user@apereo.
Hi Ted,
This is something that I’ve come across several times in the past and from what
I recall in my previous research, the ShibCas plugin doesn’t support the
processing of CAS attributes.
I’ve ended up configuring the attribute resolver in Shibboleth to perform
additional LDAP queries after
CAS 5.2.0 RC2 is released:
https://github.com/apereo/cas/releases/tag/v5.2.0-RC2
For those of you keeping up with 5.2 RCs, I recommend that you review the
changelog and releases notes. A number of settings are shifted around and
cleaned up as a result of folks working to improve documentation
I switched the client to use https, but get the same error. Using the
debugger I've tracked down where it makes the call to the client with the
/j_spring_cas_security_proxyreceptor and it comes back with a 404.
My client side configuration is done with cas 3.2 and has the following in
the cont
