{"id":32,"date":"2007-09-30T17:48:19","date_gmt":"2007-10-01T00:48:19","guid":{"rendered":"https:\/\/self-issued.info\/?p=32"},"modified":"2007-09-30T17:48:19","modified_gmt":"2007-10-01T00:48:19","slug":"the-popularity-of-openid-and-how-it-relates-to-%e2%80%9chome-realm-discovery%e2%80%9d","status":"publish","type":"post","link":"https:\/\/self-issued.info\/?p=32","title":{"rendered":"The Popularity of OpenID and How It Relates To “Home Realm Discovery”"},"content":{"rendered":"

Andy Dale<\/a> recently made a great post titled “Adopting Evolution<\/a>” in which he asked the question:<\/p>\n

Why has OpenID grabbed so much popularity while SAML, a much more mature, academically respected, ‘robust’ specification has been largely ignored by the cutting edge web 2.0 community?<\/p><\/blockquote>\n

I’ll encourage you to read his post<\/a> for his insightful answer.<\/p>\n

His question reminded me of another answer to the same question that I gave during the recent Concordia<\/a> meeting at DIDW: OpenID solves the “Home Realm Discovery” problem that all Federation protocols face; that is, figuring out where the person’s authentication information should come from.<\/p>\n

There’s lots of ways this problem can be solved, many of which involve potential identity providers being pre-configured by system administrators as possible choices for specific services. Some systems have even dictated the use of a particular identity provider. OpenID’s solution to this is elegant in its simplicity: Let the user decide.<\/strong><\/em> When I type in an OpenID URL such as https:\/\/mbj.signon.com\/ I’m telling the relying party where my identity provider for this interaction is — thus solving the “Home Realm Discovery” problem. As elegant as this is, of course, the potential downside of this solution is that it assumes that people will remember their OpenID identifiers and will faithfully type them in when a page prompts them for an OpenID.<\/p>\n

OpenID 2.0 actually allows i-names<\/a> such as =mbj or =Mike.Jones to be used as OpenIDs as well. I-names then use their own lookup protocol to discover the identity provider behind the i-name typed. This is arguably better (and is the kind of OpenID I personally use), but still relies on the user to reliably enter their OpenID identifier when prompted.<\/p>\n

In this discussion at Concordia<\/a>, others pointed out that using an Identity Selector (such as DigitalMe<\/a> or CardSpace<\/a>) is another means of solving the problem. Like OpenID, it also lets the user decide, but in this case, by clicking on a visual Information Card, rather than typing in a string. I personally believe that this will be an easier metaphor for many people to use once it’s commonly available than typing in an OpenID identifier.<\/p>\n

I’ll also point out that it’s not a one-or-the-other choice between OpenIDs and Information Cards when letting the user decide. As was recently demonstrated<\/a>, OpenID Information Cards can be used to deliver the OpenID identifier to the OpenID relying party, rather than having the user type it.<\/p>\n

In conclusion, while it may seem esoteric, solving the “Home Realm Discovery” problem is essential to working digital identity deployments. And the usability of the solution chosen matters a lot. Using Andy’s terminology, I believe that its solution to this problem both accounts for some of “the juju that OpenID has” and may result in usability problems for less technical audiences that will need to be addressed if it’s to break out beyond just us geeks.<\/p>\n","protected":false},"excerpt":{"rendered":"

Andy Dale recently posted a great entry titled “Adopting Evolution<\/a>” in which he asked the question:<\/p>\n

Why has OpenID grabbed so much popularity while SAML, a much more mature, academically respected, ‘robust’ specification has been largely ignored by the cutting edge web 2.0 community?<\/p><\/blockquote>\n

I’ll encourage you to read his post<\/a> for his insightful answer.<\/p>\n

His question reminded me of another answer to the same question that I gave during the recent Concordia<\/a> meeting at DIDW: OpenID solves the “Home Realm Discovery” problem that all Federation protocols face; that is, figuring out where the person’s authentication information should come from.<\/p>\n","protected":false},"author":4,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[7,18,3,14],"tags":[],"class_list":["post-32","post","type-post","status-publish","format-standard","hentry","category-federation","category-i-names","category-information-cards","category-openid"],"_links":{"self":[{"href":"https:\/\/self-issued.info\/index.php?rest_route=\/wp\/v2\/posts\/32","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/self-issued.info\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/self-issued.info\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/self-issued.info\/index.php?rest_route=\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/self-issued.info\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=32"}],"version-history":[{"count":0,"href":"https:\/\/self-issued.info\/index.php?rest_route=\/wp\/v2\/posts\/32\/revisions"}],"wp:attachment":[{"href":"https:\/\/self-issued.info\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=32"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/self-issued.info\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=32"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/self-issued.info\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=32"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}