If you're specifying the location of the trust store file make sure its not corrupted and that the path is correct. I don't have JBoss so I can't comment more if its a JBoss issue. We use Tomcat here, which is what most of our instructions are for (unfortunately for you ;-)).
On Tue, Apr 21, 2009 at 11:30 AM, Scott Battaglia <[email protected] > wrote: > On Tue, Apr 21, 2009 at 11:10 AM, Bruno Melloni < > [email protected]> wrote: > >> <snip /> >> > I don’t make false accusations, or even accusations of any kind. What you >> perceive as accusations is nothing more than what I understand from your >> words. For example ‘callback to mothership’, a common term for the >> standard industry practice of tracking usage, I got from your statement >> “You're >> probably hitting on the fact that one of our tests checked against the old >> Jasig web site”. It wasn’t clear until your last email that you meant >> that it is a test to verify that HTTP is working. I apologize for >> misunderstanding you. >> > I would just caution to be more careful before making statements like that. > The email I sent was explicit about the fact that it was a test case that > expected a 404 error (read the second sentence) and no longer received a 404 > error. It'd be pretty weird if we had a callback that depended on a page > not existing ;-). Regardless, I'm glad we're both understanding each other > now. The important part is that you understand that we don't do nefarious > things like call home. > >> >> >> And yes, the first exception was mine and caused by upgrades on my PC >> (still not sure why since jBoss does not rely on cacerts like Tomcat), had >> already been fixed when I regenerated the keystore and cert as you suggested >> earlier, and –as mentioned - included in the email only for completeness. >> The issue remaining is the 2nd exception. As I had mentioned, it >> happened during execution, not during a CAS build. >> > I was actually talking about the second exception, as mentioned in my email > with regards to the JVM exception. Its related to the JVM attempting to > validate the certificate and not being able to find it. As I mentioned in > the previous email, searching for that exception related to trustAnchors > shows a number of possible fixes. One of which could be that the file is > corrupt or that the path to the file is set wrong, or that the file space > contains errors. I'm unfortunately not in the same location as you, so I > can't quickly determine if its any of those. This may seem like I'm trying > to get out of answering it, but since its not a CAS problem, the best I can > offer is to take the JVM exception and search in Google and try a few of the > results (I mentioned a few of the possibilities here). > > Cheers. > -Scott > >> >> >> b. >> >> >> ------------------------------ >> >> *From:* Scott Battaglia [mailto:[email protected]] >> *Sent:* Tuesday, April 21, 2009 9:19 AM >> *To:* [email protected] >> *Subject:* Re: [cas-user] CAS 3.3.1, 3.2, old and new Jasig CAS sites >> >> >> >> -- >> >> 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 >> >> > -- 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
