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 383 | Next

Vittorio Bertocci, Garrett Serack, Caleb Baker

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


There is no way to silently import these ?¬?les into the CardSpace
local store. The native call is as follows:
HRESULT _stdcall ImportInformationCard( __in LPCWSTR
?¬?lename);
The managed call is this:
void CardSpaceSelector.Import(string ?¬?lename);
The import call can be particularly useful when writing an application
to distribute Managed Cards. An example is an application
distributed by group policy on corporate desktops, which
prompts users to install a Managed Card.
Get a Token from CardSpace
This is probably one of the most useful calls available to a developer
who wants to develop a native application that works
with CardSpace. The GetToken() call initiates a token request,
The import API
allows an application
to open
CardSpace at the
Import Card page
GetToken is used to
request a token
from CardSpace
CardSpace Without Web Services 265
and makes use of all the policy options available to WCF.
However, it was designed to be called by WCF, and
consequently, the parameters are very specialized for that
purpose. The native call looks like this:
HRESULT
__stdcall GetToken(
__in DWORD cPolicyChain,
__in_ecount(cPolicyChain)PPOLICY_ELEMENT
pPolicyChain,
__deref_out PGENERIC_XML_TOKEN* securityToken,
__deref_out PINFORMATIONCARD_CRYPTO_HANDLE*
phProofTokenCrypto );
The managed call looks like this:
Void void CardSpaceSelector.


Pages:
371 372 373 374 375 376 377 378 379 380 381 382 383 384 385 386 387 388 389 390 391 392 393 394 395