Symmetric keys classically provide faster crypto operations,
but are shared between the relying party and
CardSpace client, and so are arguably less secure. The
CardSpace default is to use an asymmetric proof key.
encryptWith. Speci?¬?es the encryption algorithm that will
be used to by the proof token. The supported values
depend on the KeyType.
signWith. Speci?¬?es the signing algorithm that will be
used by the proof token. Again, the supported values
will depend on the KeyType.
keySize. Speci?¬?es the size of the proof key.
EncryptionAlgorithm. The encryption algorithm can also
be speci?¬?ed and is used to determine which algorithm
will be used to protect the proof key.
Despite the additional options available when using CardSpace
with WCF, the usage of CardSpace with WCF Web services and
with websites follow similar patterns and use the same basic
options. So although using CardSpace with websites is the more
prevalent model, learning to use CardSpace with Web services
is a natural progression.
CardSpace Without Web Services
Both websites and Web services were the primary focus of
CardSpace v1. However, other deployment scenarios are possible.
CardSpace exposes both native and managed APIs that
can be used by C++ and C#.
Pages:
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392