Re: [cas-user] Unable to get UID attribute in client side

Morning, When you say you get 302, do you mean a 'too many redirects' message in the browser? Does your audit log say that the ticket was validated successfully? The client application needs to be using https during ticket validation. If you are using a self signed cert, add it to the jvm

Re: [cas-user] Unable to get UID attribute in client side

I don't remember the fine specifics of the logs well enough to know. It's possible that both are at fault? Make sure you are listing attributes to lookup in your ldap attribute repository configuration. If they aren't there, that'll be problem one. The other thing is that by default the CAS 2

Re: [cas-user] Question about using CAS with LDAP...?

To provide an update I was able to get this to work. I needed a user-name and password for binding: AuthLDAPBindDN username AuthLDAPBindPassword password Thanks for the assistance... On Friday, February 12, 2021 at 12:25:22 PM UTC-6 dhawes wrote: > On Fri, 12 Feb 2021 at

[cas-user] Unable to get UID attribute in client side

Hi Team, CAS server - 6.2.3 CAS client - 3.6.2 We are not getting UID attribute in client side. We use CAS 2 protocol i,e Cas20ProxyReceivingTicketValidationFilter. Upon redirection, we are getting ticket value(ticket=) in url and after successfull ticket validation got 302 http status code.