Adding CardSpace to WCF
Using CardSpace with WCF has many similarities to using
CardSpace with the browser. The overall interaction is basically
the same:
256 CardSpace Implementation
1. The user attempts to access a restricted Web service and
is prompted for a card.
2. The user selects and submits a card.
3. CardSpace returns a token. WCF sends this token to the
Web server.
4. WCF performs the token decryption, and performs token
validation.
5. The Web service processes issuer and claims information
to authenticate the user.
We??™ll take a look at the details of each of these steps, but it is
important to note, this enables the ws-* transactions, such as
ws-security, as discussed in Chapter 2.
Calling CardSpace from WCF
It all starts with the service being able to invoke CardSpace. To
do this, the service needs to be able to specify the security requirements
that a client must meet to communicate with the
service. This is set in the services binding.
There are different binding types de?¬?ned; the different types
specify different default values. Speci?¬?c binding types are easiest
to use with CardSpace. The most restrictive and consequently
easiest to use binding type that works with CardSpace is
wsHttpBinding.
Pages:
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384