In a few short weeks, I have taken in BarCamp Vancouver, Drupal Camp LA, Digital Identity World, Drupal Camp Victoria and Drupal Camp Seattle.

Recently I have delved a little more into understanding more about topics related to distributed search and identity. It was an eye opener to a whole new world of acronyms. To try to resolve the issue of lack of awareness and information, I have signed up for 3 events in 2 weeks

• Drupal Camp Victoria, where I will be attending/organizing a BOF on identity, to discuss, listen and understand with other interested parties. As well, trying to do my part, by giving a talk on setting up local development environments
• Digital Identity conference in Los Angeles, where I managed to register as a "blogger".
• Drupal Camp LA since I will be down in Los Angeles, might as well.

OpenID is an open decentralized identity framework where you can get your own identity and re-use it across the internet. The first application is single sign on which means you can login onto many websites and web applications and services (more being added daily! And all Bryght Basic sites can now support OpenId) using just one id (a URL) and one password rather than multiple passwords and multiple identities which is the case today.

To explain OpenID single sign on, we have two new screencasts for OpenID which has been included in Bryght Basic since July 31, 2007:

• Logging into a Drupal Site and Ma.gnolia using OpenID Screencast
• Associating an OpenID with your Drupal Account

As James, mentioned, he just finished one of the world's first implementations of OpenID 2 code (go James go!).

Here's an N93 video that I took of him presenting at last night's Open ID 2 Mashpit held at sxip:

Last night, a bunch of us Bryght guys attended the OpenID Mashpit hosted here in Vancouver by the folks at SXIP. It was a chance for a bunch of developer-types and interested techies to get together and dive into what, exactly, OpenID is and what this identity space is all about.

Dick Hardt started us off with an overview, so everyone was up to speed on the basic terminology and flow. The questions started coming pretty quickly and it turned into a very interactive session, proving that there is a lot of interest. We had a short break and then went into "lightning talks"....which ended up being more, longer interactive sessions.

I wanted to have an open session on "federation" – a word we never ended up defining. In short, in the network of networks world that is emerging, where any system/node can be both a consumer and provider of identity or attributes, how do pieces of the network easily share trust? The short answer is that trust is hard, but the OpenID 2 infrastructure likely gives us the extensible pieces we need (along with SAML payloads) to build such a system. We'll be focusing on making this work "out of the box" over the coming months. I had a great time during this session – I got up to the front and sort of set the stage, and then Dick Hardt joined me and we went back and forth, diving into the details of attribute exchange and how various parties in a system would grant or gain access to resources, attributes, etc. Thanks, Dick, let's take our show on the road!

When we moved into break out room, I went around the room and cornered people into installing plugins for different systems – we captured this on the wiki, and should be able to test logging into people's sites with our own OpenID URLs. For testing with OpenID 2 code, we found that SXIP has Email Verification and Attribute Exchange systems set up.

Oh yes, and as Steve Jobs likes to say....just one more thing: OpenID 2 code is now available for Drupal, with both consumer and server modules available. As far as we know, this is some of the first OpenID code out in the wild. James demo'd it last night, and Bryght has set up an identity provider at home.bryght.com. Feel free to use that as a home site, for testing or other purposes (the OSCMS Summit site has the compatible consumer module enabled). The code is not quite "finished" as James complains, but we wanted to get it out so that other people could start working on it with us and that we would be able to start testing. The big thing to note is that the OpenID 1.1 compatibility part isn't implemented yet, and large chunks of the attribute exchange aren't either.