Websites interested in using Information Cards can choose their
own level of comfort, deciding on speci?¬?cally which features
they would like to adopt, to gain the following:
Form ?¬?lling. Filling in commonly found ?¬?elds in websites,
saving users time and effort. This can be done with
little effort.
Simple authentication. Using Information Cards as a
replacement for usernames and passwords, enhancing
existing web-based systems. As the most common pro?¬?le
for using Information Cards, this is accomplished with a
modest level of effort.
Extended authentication. Deploying a resource Security
Token Service (STS), of?¬‚oading the authentication services
onto other servers, and even possibly outsourcing
those services to other companies. Adopting an STS is
signi?¬?cantly more effort and requires a greater understanding
of WS-* and the mechanics of the Identity
Metasystem.
Claims-based programming. Accepting identity information
from identity providers (IPs) and using that information
to make service decisions. This level of involvement
really pushes far more fundamental changes in application
architecture and design.
There are many
different reasons to
use Information
Cards
273
Identity federation.
Pages:
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404