![]() If an identity provider wants to issue tokens, it must provide a means by which a user can obtain a managed card and provide a Security Token Service (STS) which handles WS-Trust requests and returns an appropriate encrypted and signed token. ![]() To accept information cards, a web developer needs to declare an HTML tag that specifies the claims the website is demanding and implement code to decrypt the returned token and extract the claim values. This means that any technology or platform that supports these protocols can integrate with CardSpace. ![]() Windows CardSpace is built on top of the Web services protocol stack, an open set of XML-based protocols, including WS-Security, WS-Trust, WS-MetadataExchange and WS-SecurityPolicy. Other transactions may require a managed information card these are issued by a third-party identity provider that makes the claims on the person's behalf, such as a bank, employer, or a government agency. CardSpace also allows users to create personal (also known as self-issued) information cards, which can contain one or more of 14 fields of identity information such as full name and address. The user selects a card to use, and the CardSpace software contacts the issuer of the identity to obtain a digitally signed XML token that contains the requested information. The CardSpace UI then appears, switching the display to the CardSpace service, which displays the user's stored identities as visual cards. When an information card-enabled application or website wishes to obtain information about the user, it requests a particular set of claims. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |