It??™s also not surprising CardSpace deployments are designed to
help facilitate website adoptions. A website will require some
changes to its logon pages, but the majority of the site can remain
unchanged. Here??™s a summary of the logon process, with
Information Cards:
1. The Information Card extension in the Web page is
invoked by the user.
2. The user selects a card.
3. CardSpace returns the token that the card represents to
the site, which posts it to a login page, where it is
processed.
4. If the user is authenticated, the site can use standard
infrastructure for ???logging on the user.??? This probably
involves setting a cookie or some other session state.
Speci?¬?cally, the site needs to add an Information Card control,
post the returned token to an authentication page, and have
some code for authenticating the token.
Understanding the Information Card Browser Extension
The Information Card browser extension is the door between
worlds. It allows the HTML of a Web page to open CardSpace
and request a token. This allows the user to select a card, and
then CardSpace makes the necessary Web service calls to
Using CardSpace in the Browser 225
A site developer
can use an HTML
or XHTML tag to
request an
Information Card
What??™s the Difference Between the Syntaxes?
Neither syntax provides a clear advantage over the other.
Pages:
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345