TYPED AUTHORIZATION DATA

• US 20080082626A1
• Filed: 09/29/2006
• Published: 04/03/2008
• Est. Priority Date: 09/29/2006
• Status: Abandoned Application

• Current Assignee: Microsoft Technology Licensing LLC (Microsoft Corporation)
• Original Assignee: Microsoft Corporation
• Inventors: Kaler, Christopher G., Nanda, Arun K., Wilson, Hervey O., Walter, Douglas A.
• Application Number:
  US11/536,996
• Publication Number:
  US 20080082626A1
• Time in Patent Office: Days
• US Class Current: 709/217
• CPC Class Codes: H04L 63/0823 using certificates cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263

Abstract

Requesting security tokens with typed information. A method includes accessing at a client, information to allow the client to request a token for accessing functionality of a service. The method further includes sending a client request from the client to a token issuer in a token request. The client request includes the information and at least one of information defining the source of the information, proof of the source of the information; or usage information specifying how the information should be used.

Claims

1. In a computing environment including at least a client, a service including functionality accessible by the client, and a token issuer, a method of requesting security tokens, the method comprising:

accessing at the client, information to allow the client to request a token for accessing the functionality of the service; and

sending a client request from the client to the token issuer in a token request, the client request including the information and at least one of information defining the source of the information, proof of the source of the information or usage information specifying how the information should be used.

2. The method of claim 1, wherein the usage information specifies that the information should be used as primary authentication.

3. The method of claim 1, wherein the usage information specifies that the information should be used as secondary authentication.

4. The method of claim 1, wherein the usage information specifies that the information should be used for information purposes.

5. The method of claim 1, wherein the usage information specifies that the information should be logged.

6. The method of claim 1, wherein the proof of source information comprises cryptographic proof from the service.

7. The method of claim 1, wherein the proof of source information comprises a certificate from the service.

8. The method of claim 1, wherein sending a client request from the client to the token issuer for a token comprises sending the information in a non-tokenized portion of the request.

9. The method of claim 1, wherein the information is typed information, and wherein the method further comprising sending type information specifying what the information represents.

10. The method of claim 1, further comprising sending format information specifying how the information is presented.

11. The method of claim 1, wherein accessing at the client, information to allow the client to request a token for accessing the functionality of the service comprises accessing information from an application locally at the client.

12. The method of claim 1, wherein accessing at the client, information to allow the client to request a token for accessing the functionality of the service comprises receiving information from the service.

13. In a computing environment including at least a client, a service including functionality accessible by the client, and a token issuer, a method of providing security tokens, the method comprising:

receiving at the token issuer, a client request in a token request, the client request including information from a service and at least one of information defining the source of the information from the service, proof of the source of the information from the service;

or usage information specifying how the information should be used; and

issuing a token to the client based on at least one of the source of the information from the service, proof of the source of the information from the service or usage information specifying how the information should be used.

14. The method of claim 13, wherein the usage information specifies that the information should be used as primary authentication.

15. The method of claim 13, wherein the usage information specifies that the information should be used as secondary authentication.

16. The method of claim 13, wherein the usage information specifies that the information should be used for information purposes.

17. The method of claim 13, wherein the usage information specifies that the information should be logged.

18. The method of claim 13, wherein the proof of source information comprises cryptographic proof from the service.

19. The method of claim 13, wherein the proof of source information comprises a certificate from the service

20. A computer readable medium for use in a computing environment including at least a client, a service including functionality accessible by the client, and a token issuer, the computer readable medium comprising computer executable instructions for performing the following:

accessing at the client, information to allow the client to request a token for accessing the functionality of the service; and

sending a client request from the client to the token issuer in a token request, the client request including the information and at least one of information defining the source of the information, proof of the source of the information or usage information specifying how the information should be used.