John Clippinger, who directs the Law Lab at Harvard University and who is a co-founder of Parity Communications now Azigo, talks about Information Cards, the wallet and that this will be integrated into Google wave.
This video is from the ideas project:
My hope is that companies like Google will help to put Information Cards into the browser.
Thursday, July 30, 2009
John Clippinger on i-cards and Google wave
Posted by Unknown at 11:18 AM 0 comments
Labels: Azigo, google, google wave, information card, wave
Friday, July 24, 2009
IIW 2009B Save the Date
Posted by Unknown at 11:16 AM 0 comments
Labels: iiw, iiw2009b, internet identity workshop
Thursday, July 23, 2009
DroidCon and DroidCamp Berlin
Nov 3, 2009
Nov 4, 2009
Sponsored by T-Labs!!!
Posted by Unknown at 5:36 PM 0 comments
Labels: Android, BarCamp, conference, opensource
Auth-napping OpenId by Weave
My first feeling was that this is a bit intrusive but then...
Here is a picture of the authnapped OpenId form:
Here is a picture of the original OpenId login:
It is the user's decision to install and use Mozilla Lab's project "weave" or not. And this solves parts of the NASCAR problem. Why should the service provider suggest some OpenId providers using the NASCAR? Well, if he has a whitelist of trusted OPs then yes.
But the OpenId-NASCAR is a cludge anyway.
I think that there should be an XRD description of which authentication methods and providers and token formats and so on a service provider supports or requires. Then a client component - read Browser extension - could help the user to make a good decision and prevent phishing attacks and more.
The user does not care whether the protocol is OpenId or Information Card or if the token format is SAML2 or what not. A unique user experience is desired. Ease of use is required. User consent is required. Security and Privacy need to be protected.
This should be "in the browser"! Secure by default. Privacy protecting by default.
I guess I don't have to repeat that I prefer the Information Card metaphor and UI. A client component is a good thing and it should be ubiquious, build-in but replacable and configurable at the user's choice.
Identification, authentication and claims/attribute transfer is not the primary service provider's interest. Those tasks should be moved outside of the website's code into an authnapping module of the user's browser.
Authnapping is good!
Posted by Unknown at 12:32 PM 2 comments
Labels: information card, Information Card Foundation, OpenId, privacy, security, weave
Imaginary Schedule for Catalyst '09
If I could travel to Burton Group Catalyst Conference I would go to this talks:
speaker | title |
---|---|
Bob Blakley | 2009: Upheaval In The Identity Market |
Lori Rowland; Bob Blakley; Mark Diodati;Gerry Gebel;Ian Glazer;Kevin Kampman | Identity Management: No Time Like the Present |
Michael Barrett | "Two Billionths of a Second after the Big Bang - Where Is Consumer Identity |
Bob Blakley | The Identity Services Market |
Bill Peer | Coming to Grips with Your Inner Cloud |
Mary Ruddy; Ron Carpinella; Tom Oscherwitz; Rick Rubin; Denise Tayloe | The Age of Identity Oracles |
Anne Thomas Manes | In Memory of SOA |
Robert Amos | Empower the Business with Identity Management |
Richard Watson | Service Modeling: Making Sure Your Services Deliver Value |
Dharmesh Panchmatia | Service Orientation for Success: a Case Study |
and more. Listing all interesting talks here takes too much time.
And then there is the Concordia workshop and the ICF Directors Face-to-face meeting...
I wish I could be there.
Posted by Unknown at 10:11 AM 1 comments
Labels: catalyst09, concordia, icf, IDM, Information Card Foundation, Kantara
Friday, July 03, 2009
iPhone Selector @ xmldap.org
The Higgins Project, namely Markus Sabadello, created an Information Card Selector that runs on the iPhone. Due to Apple's benevolent dictatorship which prevents extensions to the iPhone's webbrowser this selector uses a custom URL-scheme to launch the selector from a web page. Details can be found here.
I adapted the xmldap relying party to output the new URL-scheme when the user-agent contains "iPhone" or "iPod".
Here are some screenshots that Markus provided:
Integrating this into the openinfocard selector is a task for this evening.
Posted by Unknown at 10:07 AM 0 comments
Labels: higgins, iPhone, openinfocard, selector