This isn't strictly a CAS issue, but we're encountering it trying to test CAS so I'm hoping someone may be able to offer suggestions.
This presents a challenge though to test the DR instance of our login stack without making the aforementioned DNS changes.
When CAS is started, it throws an exception:
Caused by: javax.net.ssl.SSLPeerUnverifiedException: Hostname verification failed for
dr-ldap.example.edu using [org.ldaptive.ssl.HostnameVerifierAdapter@20...63::hostnameVerifier=org.ldaptive.ssl.DefaultHostnameVerifier@41...82]
Is there a way to get CAS to temporarily disable or ignore hostname verification via a property or Java option so that we can confirm things are otherwise working as expected? Any suggestions would be appreciated.
--
Baron Fujimoto <
ba...@hawaii.edu> :: UH Information Technology Services
minutas cantorum, minutas balorum, minutas carboratum desendus pantorum
You received this message because you are subscribed to the Google Groups "CAS Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
.