{"id":689,"date":"2007-02-19T16:32:18","date_gmt":"2007-02-20T00:32:18","guid":{"rendered":"\/?p=689"},"modified":"2007-02-19T16:35:23","modified_gmt":"2007-02-20T00:35:23","slug":"helloworld-information-cards-part-iii","status":"publish","type":"post","link":"https:\/\/www.identityblog.com\/?p=689","title":{"rendered":"HelloWorld Information Cards Part III"},"content":{"rendered":"

To understand this discussion, <\/em>start here<\/em><\/a> and then follow the continuation<\/strong> links until you return to this posting. Click on the images below to see a larger and more readable version.<\/em><\/p>\n

In the demo, as shown in the following screen shot, only the HelloWorld card is illuminated – all the other cards were “greyed out” as inappropriate:<\/p>\n

<\/a><\/p>\n

This happened because in the Information Card login page,  the “relying party” expressed a requirement that a HelloWorld card be presented.  This was done by embedding “policy” in the “object tag” that tells the browser (and through it, CardSpace) what Information Cards will be accepted.  To drill into this, let's look again at the login page:<\/p>\n

<\/a><\/p>\n

Here's the HTML that created it:<\/p>\n

<\/p>\n

You'll see that one of the PARAMs in the OBJECT tag is “tokenType”.  It's set to a completely arbitrary value – one I made up to show you can do whatever you want – of http:\/\/kcameron11\/identity\/helloworldToken<\/a>,  Since I specified this specific token type, only Information Cards that support it will illuminate<\/em> at selection time when you go to this web page.  Further, the other PARAM specifies “requiredClaims”.  Only Information Cards that support these values will be possible candidates.<\/p>\n

The InfoCard Web App and Browser Guide<\/a> has more information about the OBJECT tag.<\/p>\n

In the next installment, I'll explain how the Identity Provider works, and you'll be able to examine the code.<\/p>\n

 <\/p>\n","protected":false},"excerpt":{"rendered":"

A continuing exploration of Information Card technology as a flexible conduit for payloads of any kind. <\/p>\n","protected":false},"author":68,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[2,8,7,22,4],"tags":[],"_links":{"self":[{"href":"https:\/\/www.identityblog.com\/index.php?rest_route=\/wp\/v2\/posts\/689"}],"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=689"}],"version-history":[{"count":0,"href":"https:\/\/www.identityblog.com\/index.php?rest_route=\/wp\/v2\/posts\/689\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.identityblog.com\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=689"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.identityblog.com\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=689"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.identityblog.com\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=689"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}