Super E-book library
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
PARTS:
Part 10
Part 11
Part 12
Part 13
Part 14
Part 15
Part 16
Part 17
Part 18
Part 19
Part 20
Part 21
Part 22
Part 23
Part 24
Part 25
Prev
|
Current Page 276
|
Next
Vittorio Bertocci, Garrett Serack, Caleb Baker
"Understanding Windows CardSpace: An Introduction to the Concepts and Challenges of Digital Identities"
The token is then
passed to code to process the token. This code can be written in
Only a simple
tag is
required for a site
to use Information
Cards
A Token Processor
page is needed to
get information
from the token
175
any language, including C#, VB.NET, Java, and PHP. It is up to
the website to decide which libraries best ?¬?t with their deployment.
Is CardSpace Just for Websites?
CardSpace provides a consistent user experience for accessing
digital identities across a range of applications. The ?¬?rst version
of CardSpace supports four main categories of applications.
Web pages. This is one of the major areas of focus for
CardSpace. Web page developers need to make minimal
changes to their HTML to support CardSpace. This can
be done by using the ???application/xinformationCard??™
tag. There are also a number
of tool kits available to help with deployment.
Rich applications using web services. Windows
Communication Foundation (WCF) supports CardSpace
and greatly simpli?¬?es writing a web service with a clientside
application that uses CardSpace for authentication.
Often switching from one authentication type (such as
username and password) to Information Cards is as
simple as changing a few lines in the web services con-
?¬?guration ?¬?le.
Pages:
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
Beginners Guide to SQL Server Integration Services Using Visual Studio 2005 (page 1)
Pro ASP.NET 3.5 Server Controls and AJAX Components (page 692)
Practical Reporting with Ruby and Rails (page 331)