On Fri, 12 Feb 2021 at 12:25, KC Pullen wrote:
>
>
> Ray,
>
> I'll take a look at the LDAP logs and see if I can find anything...
What do your mod_authnz_ldap logs say?
--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines:
Morning,
You do not need to override any classes/filters in cas client for it to work.
Turn up your cas server logs to debug to see what it is doing.
There is also this logger which will output the http client used for
communication between the client application and cas for ticket validation
Hi Team,
We have upgraded CAS Server to 6.2.2 and CAS client to 3.6.2. After
successful authentication, CAS client is not redirecting to our application
with samlArt param and 302 http status code.
*We have updated the dependencies like below:*
org.jasig.cas.client
cas-client-core
In particular, I would either be looking at
https://apereo.github.io/cas/6.3.x/services/Configuring-Service-Access-Strategy.html
Or
https://github.com/apereo/mod_auth_cas
Require cas-attribute :
The first page you referenced is nearly a decade old, and brings an LDAP
dependency into your HTTPD
KC,
Perhaps it is the LDAP side of things that is having problems.
Are you able to look at LDAP logs?
Ray
On Thu, 2021-02-11 at 18:38 -0800, KC Pullen wrote:
Notice: This message was sent from outside the University of Victoria email
system. Please be cautious with links and sensitive
I wouldn't mix the two methods. There's probably a way to make that work, but
that's an HTTPD question, not a CAS question. You can have CAS authenticate
against LDAP from the CAS IdP. That can either then return the list of
attributes to have mod_auth_cas filter on. Or you can have the IdP do
