It hardly seems possible, but Kara and I just celebrated our third anniversary yesterday (July 21st). It seems as we’ve known each other forever, but also as though we’ve only been together for months. I suppose that’s the mark of a good relationship, eh? And now we have a beautiful 14 month old son who keeps us very busy as well. I took the day off work and we had a picnic and went geocaching. Kara had never been and it was fun, even in the rain. Timothy certainly enjoyed being out in the woods and we found some local parks we didn’t know about. It was just a nice relaxing day and we’re looking forward to many more anniversaries in the future.

I’ve had a very frustrating few months at work. My current project is WCF and WSE 3.0 interoperability using SAML tokens for authentication (if you don’t know what any of those are, just skip those post). The initial problem was that WCF was failing to load the SAML token from the messsage, I discovered that the SAML tokens issued by WSE aren’t quite standard and was able to adjust. Next, it couldn’t validate the digital signature on the token. This turned out to be a configuration problem, again, make adjustments and move on. Now we’re onto the real problem, WCF won’t validate a message signature when the message is signed using a SAML token. It knows about the SAML token, it’s decrypted the key information embedded in the token, it just won’t use it for message signature validation. The one useful response I’ve gotten to the problem on the MSDN forums is that WCF is treating the SAML token as a secondary token and therefore won’t use it for signature validation. The question I have is “Why?”, why would the SAML token be considered the secondary token when it’s the only token in the message!? So, if anybody out there stumbles across this post and has an answer, please let me know in the comments!