I may be oversimplifying, but what about changing the trustedIssuerDnPattern to
“CN=.*”? It’s formally a regex pattern, so while I’ve never tried a plain
asterisk there, it shouldn’t work.
--
Ne Desit Virtus,
Sean R. Baker
1LT, MS
United States Army
Office #: (301) 319-0712
Email:
Hello,
Tank you for your help
Robert Oschwald
I had to solve my problem of connection error message to CAS last Tuesday.
The problem was due to the casclient 2.1.1 and the fisrtname and lastname
of the SSL certificate on my CAS server I created.
-For CAS client: I replaced by another casclient
The version of java used by Tomcat is the same one as is used to build CAS
( its all installed on one machine, and I only have one Java installed).
Is CAS incompatible with some versions of Tomcat?
Jeff
On Fri, Aug 15, 2014 at 6:31 PM, Chris Peck crp...@email.wm.edu wrote:
I may try whacking
bean id=x509Handler
class=org.jasig.cas.adaptors.x509.authentication.handler.support.X509CredentialsAuthenticationHandler
property name=trustedIssuerDnPattern value=CN=*/
property name=maxPathLength value=3 /
property name=checkKeyUsage value=false /
MA we will consider providing official patches for [Java CAS Client 3.2
and 3.1] lines if there is interest.
I'm still interested in a patch fixing this issue for the Java CAS Client
3.2 line specifically, since that's the CAS client version used in uPortal
4.0 and 4.1.
However, I've also
I have CAS server that uses x509 authentication. Standalone, with the tomcat
connector clientAuth=true it works fine. However, when I add a client to the
mix (In this case Blackboard, but other clients have the same problem)
everything works fine, except when the client goes to CAS to
