Great timing Scott - I just got the issue resolved and was coming here to let you know! :-) (It will be a relaxing Christmas now! :-)
Turns out this latest issue was a case of duelling (or, more properly, mis-placed/mis-understood) keystores. The Tomcat instance was specifying a keystore that was *not* the one that the CAS server cert had been imported into. I imported the cert into the correct keystore, and, no huge shock, it all actually worked! <:-) So, I'm not sure how many folks have JIRA/CAS going with the ja-sig java client, but here's one testimonial that it works if you know enough to get all the correct pieces lined up correctly. (This has been a learning process for me. :-) I'm going to go back and make sure that I understand the sum of all the steps I've taken and will update this thread with those, in hopes of saving some other noob the pain that I've gone through. (most of it self-induced, I must say) Thanks a Million for your help and patience on this - its truly appreciated!!! Jim -- View this message in context: http://www.nabble.com/JA-SIG-CAS-Client-and-JIRA-tp20959030p21160772.html Sent from the CAS Users mailing list archive at Nabble.com. _______________________________________________ Yale CAS mailing list [email protected] http://tp.its.yale.edu/mailman/listinfo/cas
