SEARCH
0-9 A B C D E F G H I J K L M N O P Q R S T U V W X Y Z
Prev | Current Page 342 | Next

Vittorio Bertocci, Garrett Serack, Caleb Baker

"Understanding Windows CardSpace: An Introduction to the Concepts and Challenges of Digital Identities"

Let??™s say the following line of XML
represents a token with our formatting:
id='tom'>Thomas
Let??™s also say the URI speci?¬?ed by the RP website is
"http://myTokenType". This would work perfectly well with
CardSpace. This really illustrates the ?¬‚exibility of CardSpace.
The token types that a card provider supports are included in the
Managed Card ?¬?le, in SupportedTokenTypeList. CardSpace
will disable any cards that do not support the requested token
type. If no token type is de?¬?ned on the extension, any token
type will be accepted.
PrivacyUrl
The site can specify a link to a privacy policy, which will be
displayed in CardSpace. The privacy policy view in CardSpace
only supports text, so the URL should point to a plain text resource.
The privacy policy is available to the user from the relying
party identi?¬?cation page, which is the ?¬?rst page a user will
see when visiting a site for the ?¬?rst time.
PrivacyVersion
A privacy version must be supplied if the privacy URL is set.
This indicates the version of the privacy policy. If the policy gets
updated at some point, the version should be increased. When
the version changes, CardSpace will notify the user of the
change by retriggering the relying party identi?¬?cation page and
providing an information bar stating that there has been a version
change.


Pages:
330 331 332 333 334 335 336 337 338 339 340 341 342 343 344 345 346 347 348 349 350 351 352 353 354