{"id":1156,"date":"2010-09-06T05:50:56","date_gmt":"2010-09-06T13:50:56","guid":{"rendered":"\/?p=1156"},"modified":"2010-09-06T06:04:27","modified_gmt":"2010-09-06T14:04:27","slug":"a-confused-critique-of-identity-federation","status":"publish","type":"post","link":"https:\/\/www.identityblog.com\/?p=1156","title":{"rendered":"A confused critique of identity federation"},"content":{"rendered":"<p>in a <a href=\"http:\/\/thefederalcircle.com\/cant-we-simplify-digital-identity\/\" class=\"broken_link\">recent piece <\/a>at <a href=\"http:\/\/thefederalcircle.com\" class=\"broken_link\">The Federal Circle<\/a>, Earl Smith II, managing partner,\u00a0comes out &#8220;all guns blazing&#8221;\u00a0against identity federation and the &#8220;weird and wonderful&#8221; <a href=\"https:\/\/www.identityblog.com\/stories\/2005\/05\/13\/TheLawsOfIdentity.pdf\">Laws of Identity.<\/a>\u00a0<\/p>\n<p>Earl wishes he could &#8220;simplify&#8221; digital identity, rejecting\u00a0identity federation\u00a0as being too abstract to solve digital identity problems.\u00a0 Unfortunately, his\u00a0view of things\u00a0mixes up architecture and\u00a0the way\u00a0real live systems are\u00a0deployed, and he creates a straw man out of particular deployment assumptions.\u00a0\u00a0The resulting\u00a0explanation\u00a0demonstrates that once confused about this,\u00a0things can\u00a0look\u00a0stranger and stranger:\u00a0<\/p>\n<p style=\"padding-left: 30px;\">All such \u201cfederated identity\u201d models start with the intuitively appealing premise that if an individual has already been identified by one service provider, then that identification should be made available to other services, to save time, streamline processes, reduce costs, and open up new business channels.\u00a0 It\u2019s a potent mix of supposed benefits, and yet strangely unachievable.<\/p>\n<p style=\"padding-left: 30px;\">True, we can now enjoy the convenience of logging onto multiple blogs and social sites with an OpenID, or an unverified Twitter account.\u00a0 But higher risk services like banking, e-health and government welfare stand apart, still maintaining their own identifiers and sovereign registration processes.<\/p>\n<p style=\"padding-left: 30px;\">To my mind, the fashionable open identity approach is ironically lumbered with the same lofty ambitions that killed off traditional Big PKI.\u00a0 The express aim is to create \u201ctrust frameworks\u201d sufficient to enable business to be conducted amongst strangers.\u00a0 To this end, federated identity proponents implore banks and government agencies to re-invent themselves as \u201cIdentity Providers\u201d in accordance with the weird and wonderful <em>Laws of Identity<\/em>.<\/p>\n<p style=\"padding-left: 30px;\">The Laws of Identity embody some powerful ideas, especially the view that when we go about our business, each of us exercises a plurality of virtual identities.\u00a0 In different settings we present different identities, each standing as a <em>proxy <\/em>for a complex and bounded relationship.\u00a0 We have different relationships with various entities and services: banks, government agencies, health services, employers, stores, professional associations, social networks and so on.\u00a0 Each identity is context dependent, and can lose its meaning when taken out of context&#8230;<\/p>\n<p style=\"padding-left: 30px;\">But for the most part, the <em>Laws of Identity<\/em> and the new ecosystem model are chockfull of unfamiliar abstractions. \u00a0They deconstruct identities, attributes and services, and imagine that when two parties meet for the first time with a desire to transact, they start from scratch to negotiate a set of attributes that confer mutual trust.\u00a0 In practice, it is rare for parties in business to start from such a low base.\u00a0 Instead, merchants assume that shoppers come with credit cards, patients assume that doctors come with medical qualifications, and banks assume that customers have accounts.\u00a0 If you don\u2019t have the right credential for the transaction at hand, then you simply can\u2019t play (and you have to go back, out of band, and get yourself appropriately registered).<\/p>\n<p style=\"padding-left: 30px;\">Perhaps the most distracting generalisation in the new identity ecosystem is that Service Providers, Identity Providers and Attribute Providers are all different entities.\u00a0 In reality, these roles are all fulfilled simultaneously and inseparably by banks, governments, social networks and so on.<\/p>\n<p>To put order into this nest of ideas, let&#39;s begin with what Earl calls\u00a0&#8220;the most distracting generalization in the new ecosystem&#8221;:\u00a0 that Service Providers, Identity Providers and Attribute Providers are all different entities.\u00a0<\/p>\n<p>In fact, Earl,\u00a0I made\u00a0no such\u00a0statement in the Laws of Identity or anywhere else, despite my support for an identity ecosystem.\u00a0\u00a0<\/p>\n<p>The <a href=\"https:\/\/www.identityblog.com\/stories\/2005\/05\/13\/TheLawsOfIdentity.pdf\">Laws of Identity<\/a> refers to an Identity Provider as\u00a0issuing &#8220;claims&#8221;,\u00a0a Relying Party as\u00a0&#8220;depending on&#8221;\u00a0claims, and a Subject as &#8220;presenting&#8221; claims, but makes no statement that if you do one you can&#39;t do the others.\u00a0 Why?\u00a0 Identity Provider, Subject\u00a0and Relying Party are <em>architectural roles<\/em>.\u00a0 A single entity can play <em>any combination<\/em> of those roles.\u00a0 One\u00a0particular combination is complete separation of the roles, but in most cases every entity plays more than one.\u00a0 \u00a0\u00a0\u00a0<\/p>\n<p>For example, today&#39;s large web sites (like the MSN&#39;s, Googles and Yahoos) are composed of thousands of individual services.\u00a0 Without having to be conscious of it, people log in to\u00a0a site&#39;s Identity Provider service, which issues claims that are consumed by each of the composite Relying Party services that make up the site.\u00a0 So the\u00a0&#8220;decomposition&#8221;\u00a0which\u00a0Earl sees as &#8220;deconstructed unfamiliar abstractions&#8221; is, at the architectural level, a <strong>MUST<\/strong> in order to have\u00a0large scalable sites, and this is as key to the current web as to the metasystem model which is just standardizing and extending it.\u00a0<\/p>\n<p>I refer Earl and others to the\u00a0<a href=\"\/wp-content\/images\/2009\/06\/UserCentricIdentityMetasystem.pdf\">User-Centric Identity Metasystem <\/a>paper for more details.\u00a0 Section 6.2 states:<\/p>\n<p style=\"padding-left: 30px;\">6.2 ACTORS PARTICIPATING IN THE METASYSTEM<\/p>\n<p style=\"padding-left: 30px;\">The actors participating in the Identity Metasystem can be classified by role, taking into consideration that any individual actor or set of actors can play multiple roles (both at the same time and at different times).<\/p>\n<p style=\"padding-left: 30px;\">(6.2 goes on to define roles such as Subject, Claims Issuer, Relying Party, etc).<\/p>\n<p>That paper is\u00a0not simple-minded in its presentation, but its goal is to\u00a0lay out a model for\u00a0precisely understanding the way identity systems actually work and can work in the future, not to do mass pedagogy.\u00a0 People using Facebook or Google or Windows Live never think about the decomposition of services within the identity fabric, yet depend\u00a0every day\u00a0on that very decomposition.<\/p>\n<p>Continuing to unwind Earl&#39;s comments, let&#39;s factor out what he says about\u00a0Trust Frameworks.\u00a0 Here I&#39;m not unsympathetic to the points he is making, though I think they are only part of the story.\u00a0 I agree that\u00a0most initial usage of the architecture is, as in the examples I&#39;ve given here,\u00a0within tightly bounded trust contexts.\u00a0But I also think that once the technology framework is in place (e.g. now&#8230;) we will see more and more examples of federation within wider contexts where it makes sense.\u00a0 The question is simply, &#8220;what makes sense&#8221;?<\/p>\n<p>If I could use my banking identity to log into the IRS, would that make sense to me?\u00a0 Yes, because I don&#39;t access the IRS site often enough that I can ever remember\u00a0an\u00a0IRS\u00a0credential.\u00a0 Would it make sense to Earl?\u00a0 Maybe not.\u00a0 So that very potential divergence\u00a0leads us to posit the need for an ecology with choices &#8211; one of which would be the IRS itself for those who don&#39;t relate to bridging of contexts.<\/p>\n<p>Earl calls upon us to agree on a few simplifying assumtions:<\/p>\n<ul>\n<li>There aren\u2019t many strangers in real life business<\/li>\n<li>Relying Party and \u201cIdentity Provider\u201d are often the same<\/li>\n<li>There are no surprise credentials<\/li>\n<\/ul>\n<p>These are all good points, but don&#39;t diminish the utility of federation.\u00a0 For example, in the case of using a banking identity to access the IRS, I&#39;m not a stranger to the IRS, nor is the bank.\u00a0 And my banking credential is not a surprise.\u00a0 I just don&#39;t want the IRS to make me manage an extra\u00a0credential for once-a-year use.\u00a0 Requiring me to do this\u00a0is not\u00a0a simplifying assumption!<\/p>\n<p>Paradoxically the next piece by Earl at The Federal Circle is called <a href=\"http:\/\/thefederalcircle.com\/will-cost-savings-continue-to-be-a-significant-driver-for-cloud-computing\/\" class=\"broken_link\">Will Cost Savings Continue to be a Significant Driver for Cloud Computing?<\/a>\u00a0\u00a0But Earl never asks\u00a0how an enterprise or government organization that\u00a0runs some of its services in the cloud handles the resulting identity problems without increasing its costs&#8230;\u00a0<\/p>\n<p>Would he suggest\u00a0two credentials, one for inside the\u00a0enterprise and one to get to the cloud?\u00a0 Two helpdesks?\u00a0 Two authorization systems?\u00a0 Or would he agree we should\u00a0be able to reuse a single credential across these two contexts?\u00a0<\/p>\n<p>Bingo.\u00a0 Wouldn&#39;t it be nice if Cloud services could\u00a0rely on (dare I say be a Relying Party for) identities provided by the enterprise or government?\u00a0 \u00a0The point is that if I build my identity systems today in keeping with an architecture that allows various roles to be played wherever it makes most sense, I set myself up for\u00a0a future that is unfolding in ways I can&#39;t always predict.\u00a0<\/p>\n<p>I hope that as someone advising people on how to grow and future-proof their organizations, Earl looks at the issues\u00a0involved in federation\u00a0one more time.\u00a0 The ability to cross technological and organization boundaries &#8211; which is called federation &#8211; is central to our ability to evolve with the agility Earl rightly sees as necessary.\u00a0<\/p>\n<p>Once Earl comes to see that\u00a0federation architecture is completely consistent with the assumptions he puts forward,\u00a0I have the feeling he will\u00a0have an interesting perspective on the\u00a0kinds of cross-context claims that make sense\u00a0in various business and government contexts.\u00a0<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Federation architecture is already used to run the world&#39;s biggest sites, and reuse of claims across organizational boundaries is a key enabler for cloud computing<\/p>\n","protected":false},"author":68,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[37,43,10,8],"tags":[],"_links":{"self":[{"href":"https:\/\/www.identityblog.com\/index.php?rest_route=\/wp\/v2\/posts\/1156"}],"collection":[{"href":"https:\/\/www.identityblog.com\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.identityblog.com\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.identityblog.com\/index.php?rest_route=\/wp\/v2\/users\/68"}],"replies":[{"embeddable":true,"href":"https:\/\/www.identityblog.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1156"}],"version-history":[{"count":0,"href":"https:\/\/www.identityblog.com\/index.php?rest_route=\/wp\/v2\/posts\/1156\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.identityblog.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1156"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.identityblog.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1156"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.identityblog.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1156"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}