It was hard to come up with a title for this article... Essentially the problem that I have been repeatedly been asked to solve is: Company A wants to use Company B's web application within it's own web application. How can we make sure that only people from Company A will be able to access Company B's application?

True, the query string (https://myserver?query=string&is=here) is encrypted when making an HTTPS call. The issue is that some people pose a very similar question with the opposite answer: Is the query string secured when making a GET request over HTTPS? Here's how I proved to myself that data in the query string is encrypted but doesn't really belong there.

Normally this isn't an issue. I've been working with IntelliJ for a few years now and never had this problem before. But no matter what I did, the IDE would only present me with an old version of my filesystem whenever the choose location dialog would come up. Then stranger things started to happen... I couldn't create a new project, builds started to fail and classes that existed on the filesystem wouldn't show up in the project. I took me a while to figure out how to get things back on track, even though the solution takes about 2 seconds once you know what to do.

Our latest software project used CAS for authentication and single sign-on. I couldn't find any good documentation on how Spring Security and CAS played together. There is some documentation about how to configure your application to use CAS but not much on what messages go back and forth by whom and when.

Here's how you can run maven built web applications directly from within Intellij IDEA 8. Once you run this way, you completely eliminate the code, build, deploy, restart cycle just when you want to make a change... you can even change classes on the fly (hot swapping).

I was working on a Weblogic Portal application that needed to get information from a secure (WS-Security) third party web service over https. This web service used a legacy (pre-OASIS) WS-Security namespace and modern clients (like the one bundled with Weblogic server) don't create messages that conform to the old specification. Here's what I did to work around this restriction...

We use client side XSLT to generate our pages. After a push to our testing environment, we noticed that the XSLT would fail in Firefox but not IE.

We recently upgraded Weblogic Workshop to version 10.2. When I went to regenerate an existing Service Control from a new WSDL file, I was greeted with a not so nice error popup...