We discovered that a change made to our CAS package to use TLS instead of SSLv3 was the cause of the problem. We are still trying to determine if there was an update on the LDAP Servers that caused them to reject the TLS connections incorrectly or if it was a Java TLS issue.
Anyway, we’re back up and runnning. Thanks for all the ideas and help! Michael -- --------------------------------o--------------------------------- Michael H. Martel | Director of Data Center Administration [email protected] | Systems and Security Administrator Vermont State Colleges | PH:802-224-3010 FX:802-224-3035 On 8/24/15, 5:17 PM, "Martel, Michael H" <[email protected]> wrote: >Greetings! > >Our IDM Expert is leaving on Friday for greener pastures, and today our IDM >system decided to start accepting all passwords as valid. As far as we can >tell this is isolated to our CAS servers and not the Shibboleth and LDAP >Servers. > >When you authenticate to CAS, every password that you enter comes back as >successful. > >Has anyone seen this before ? Any thoughts on where to look ? He’s been >beating his head on it all day and come up with nothing. > >If I didn’t include enough details, tell me what I need to add, I’m new to the >IDM side of this. > >Thanks! > > > >Michael > >-- > > --------------------------------o--------------------------------- > Michael H. Martel | Director of Data Center Administration > [email protected] | Systems and Security Administrator > Vermont State Colleges | PH:802-224-3010 FX:802-224-3035 > > > > >-- >You are currently subscribed to [email protected] as: >[email protected] >To unsubscribe, change settings or access archives, see >http://www.ja-sig.org/wiki/display/JSG/cas-user -- You are currently subscribed to [email protected] as: [email protected] To unsubscribe, change settings or access archives, see http://www.ja-sig.org/wiki/display/JSG/cas-user
