The latest issue of the Architecture Journal is available for download here (I am breaking the news even before the rest of the pages are updated from issue 15 to issue16: see how much I care about you?;-)). What makes this especially interesting is that issue 16 is entirely dedicated to identity! I have to admit that I've yet to read most of the articles, but I've definitely went through 2 of them: One is an interview/profile with Kim Cameron. It's a nice read, and I am sure you'll enjoy to know

Ahh, I’ve been looking forward for this post for a looong time. We just made available for download the bits of the Beta of “Zermatt” Developer Identity Framework . “ Zermatt ” is the codename of a .NET framework that helps developers build claims-aware applications to address challenging application security requirements using a simplified application access model. Let me expand a bit on that. If you want to develop applications that take advantage of claims & identity Metasystem goodness in

| View | Upload your own Slideshare doesn’t handle animation very well. So…here is a run down on the last demo. In addition to inter-operating with other participants, I demoed login to Google Apps, using a server from Ping, CardSpace from Microsoft and an Information Card from Sun. In terms of platform, Sun’s servers were [...]

I’ll be at RSA Conference next week participating in the following events. Concordia What: The current goal is to demonstrate that SAML, WS-Fed and Information cards can co-exist and some of use cases where it makes sense. For instance, if you already have a federation setup (using SAML or WS-Fed), you can leverage Information Cards as [...]

As I just reported over at The Aquarium , Eve and Marina recently published Federated Identity Through the Eyes of the Deployer - what it is, why you might want it and what questions to ask as you architect a federated identity system. As I mentioned on The Aquarium , Eve was a key player in defining XML, SAML and more. What you might not know is that Eve is also a talented musician, shining even when accompanied by those less gifted in the art , such as here, at IIW2006b : Here be the lyrics .

Trust is the business word for love. Identity Federation is the cello tape that ties the business world together. Federation car needs to hitch on the train that is online collaboration. Borrowing from one of ***’s presentation - federation needs to become a Viagra solution (i.e. giving more powers) and not just a painkiller (i.e. solving an [...]

Nan-in, a Japanese master during the Meiji era (1868-1912), received a university professor who came to inquire about Zen. Nan-in served tea. He poured his visitor’s cup full, and then kept on pouring. The professor watched the overflow until he no longer could restrain himself. “It is overfull. No more will go in!” “Like this cup,” Nan-in said, [...]

To date, the vast majority of real-world federation roll-outs have been internal or enterprise type deployments. Things like an enterprise authenticating its users out to an outsourced provider (such as a Fidelity 401K, or AOL's Radio Service). Yes there are many exceptions to this general statement (you can see many of them on Liberty's Adoption Page ), but that is the general view of the industry and I certainly don't knowingly use federation in any cross-provider operations. The time has come

I recently received a comment on my SAML Bashing blog entry. "Jeremy" (not sure which Jeremy as he was otherwise anonymous in his comment -- I wonder if it's really James in disguise -- this seems the kind of comment James would leave, but James is usually quite blatant about it, not hiding behind an identity pseudonym) asked: Kim stated "The question of how the relying party knows which identity provider URL to use is open ended. In a portal scenario, the address might be hard wired, pointing to