Using a bank as an analogue, imagine a
?¬?nancial institution that issues ATM cards that don??™t meet customers??™
expectations for availability or that don??™t work in any
other ATM machines outside of that institution. It would not be
very successful. Applying that to Information Cards, IPs should
be willing to provide availability of those identities any time
they reasonably could be used. Downstream, too, RPs that are
expecting to accept Information Cards from users will ?¬?nd
Common Misconceptions about Becoming an Identity Provider
Managed Cards can
contain any number
of claims
An IP uses an STS
to issue tokens
308 Identity Consumers
themselves quite unhappy when users are blocked from using
their services because of a failure at the IP.
The decision to be a Managed Card IP requires the organization
to understand the technology and scenarios at a deeper level
than an RP. RPs can use off-the-shelf code available to add support
for accepting Information Cards to their sites; IPs have
choices in technology and architecture that could ripple
changes through their entire enterprises. These technology and
architecture choices come with increased costs in software,
hardware, and manpower, and should be weighed against the
tangible business bene?¬?ts of the effort.
Pages:
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442