Thank you for the response. I have already tried the solution presented there, which was to import the key into a truststore. That approach did not seem to fix the problem.
The sample CAS application includes a combined keystore/truststore. When I run the sample application, there is no problem with the SSL certificates. When I point my own application server at the exact same combined keystore/truststore, I get an error with the SSL certificate. I am confused as to why the keystore/truststore included with the sample application works fine for it, but not for my application. I was hoping that using the sample app's keys would help me eliminate a variable for the problem, but for whatever reason, I still can't get my own app to recognize the SSL certificate. If I could figure out why my application chokes on the keystore/truststore the sample app uses successfully, I might be able to get my application to work with my own self-signed key. Regards, Lance Hill -----Original Message----- From: Marvin Addison [mailto:[email protected]] Sent: Monday, March 15, 2010 1:54 PM To: [email protected] Subject: Re: [cas-user] SSL certificate problems This is a common problem that we discuss at http://www.ja-sig.org/wiki/display/CASUM/SSL+Troubleshooting+and+Reference+G uide along with steps to resolve. M -- 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
