The ?¬?rst provides
a card provider a way to provide the user with contact
information, similar to the phone number and address information
you probably have on the back of many of the cards in your
wallet.
This information can be included in an ???issuerInformation??™
element in the Managed Card ?¬?le and can contain up to 20
name-value pairs, which are shown on the Card Details page so
that the user has easy access to them when looking at the cards.
And although any URLs that are included (such as a link to a
help page) will not directly open a browser window, they can be
cut and pasted from the CardSpace desktop to a browser windows
on the user??™s primary desktop. A window cannot be
opened directly, for security reasons, so the CardSpace desktop
is isolated from the browser process.
Another way for the card provider to communicate to the user is
when an error occurs in using the card. In the ?¬?rst release of
CardSpace, a fairly generic message was displayed. With
CardSpace in .NET 3.5, however, the IP??™s STS can send a custom
message back in a SOAP fault. The message can be anything the
IP deems as useful, ranging from ???Bad username or password???
to ???Your club membership has been discontinued,??? depending
on the type of card.
Pages:
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342