This one was interesting….
Recall that I am working on a project where I had to set up a web application on Apache Tomcat that users can connect to through IIS (an through a secure channel).
In the application, there is a requirement to open up a URL connection to another secure site (essentially a URL starting with https). I got this weird exception message: PKIX path building failed: sun.security.provider.certpath.SunCertPathBuilderException: unable to find valid certification path to requested target.
As usual, a simple Google search led to an article that talks about this very problem. Turns out that the Java Secure Socket Extension of the Java runtime in which Tomcat runs (and hence the web application) cannot connect to the external secure site as the runtime has not been told that the external site is trusted. The fix for this is to store the certificate from this external site in a place which the runtime can access. So the next time around the URL is being accessed, the runtime will allow it.
Following the instructions in the above article I got to generate a certificate store that then needed to be put in a place where the runtime can see. There was a small hiccup here. I thought that the <JDK_HOME>\jre\lib\security is where the certificate store (a file called jssecacerts) needs to reside. Actually it was <JRE_HOME>\lib\security which obviously makes more sense.
Now the world is back to normal…..
P.S: The link to the Sun Java documentation about security certificate stores and all is broken. Here is the correct link and here is the link to the specific section on customizing certificate stores.
Powered by ScribeFire.
Hmmm…I ran into an interesting dilemma. Like the other one hundred zillion people, I have a Facebook profile too. Initially my intent was to socialize (big surprise) and started accepting friend requests from anyone and everyone. I guess that is the goal, after all it is a social network. However, my problem now is that my personal friends, my business acquaintances, my current coworkers, my past coworkers are all in my “friend” network. I realized that I maybe social but I am not very tolerant of the following facts:
- Too much useless “Status Updates”…
- My coworkers knowing about my personal friends…
- Too much noise in general…
I wish there was a way to categorize all my contacts. (Of course, in many cases, my past coworkers have become good friends.) I wish I could have create multiple accounts (still thinking along the lines of email…). So I looked at Facebook help and I was surprised to find that creating multiple accounts is actually against FB’s terms of use. Wow!
Seems like FB Pages is the recommended way to go. Let’s see….
Seems like I found a fix for the problem due to which HTML embedded in my posts (like links etc) were being parsed incorrectly. Here is a link that discusses the issue: http://core.trac.wordpress.org/ticket/7771. Turns out that the problem lies with the fact that the XML parser on the WP server side was not parsing the XML that was coming in through the XML-RPC payload. There is a plugin that works around this problem. That plugin is here: http://josephscott.org/archives/2009/02/update-on-libxml2-issues/.
I have downloaded the plugin and installed it. Hopefully it would work. This post is a test. The proper fix is to update to the correct PHP version. I will get to it someday….
Liked it. Definitely the kind of tool that I wanted. However, I don’t understand one thing…and this is not specific to ScribeFire. Anytime I try to add a link through a desktop tool (or something like ScribeFire), the final rendered product seems to strip out the angle brackets. Is this something on the blog server side? Maybe a setting or something. I would imagine that the client (desktop tool or ScribeFire) would send a properly encoded contents which would mean converting the angle brackets to the right encoded values. Maybe the encoding negotiations are off, need to find out….br /br /div class=”zemanta-pixie”img class=”zemanta-pixie-img” alt=”" src=”http://img.zemanta.com/pixy.gif?x-id=d8a08d19-935d-8937-aa3b-ba5233da94e2″ //div
I am going to play around with this idea of milli-blogging (not as comprehensive as micro blogging or too elaborate like blogging) using which I can quickly upload some thought or idea or something. I found this addon to FF (ScribeFire) which seems to be a good tool for exactly this purpose.
Every once in a while a Grails application will behave completely weirdly throwing out completely unrelated errors when you try to do add or edit some domain objects. I found that deleting the .grails directly and then rebuilding the application clears out that problem. On Windows, the directory is located at C:\\Documents and Settings\\userid. The only impact this will have is that any plugin that the application may be using will be reinstalled by the Grails runtime system (possibly through Maven).
