# US 2004/0210756 A1 · Pass-thru for client authentication

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2004/0210756 A1
- Document ID: US20040210756A1
- Status: Published application
- Kind: A1
- Application number: 10/413,799
- Filed: 2003-04-15
- Published: 2004-10-21
- Earliest claimed: 2003-04-15
- Assignees: Microsoft Corporation
- Inventors: David R. Mowers; John Banes; Daniel R. Simon; Paul J. Leach
- Web page: https://patentgrep.com/patent/US20040210756A1

## CPC

- H04L 63/0869: {for achieving mutual authentication (cryptographic mechanisms or cryptographic arrangements for mutual authentication H04L9/3273)}
- H04L 63/08: {for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32)}
- H04L 63/0807: {using tickets, e.g. Kerberos (cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213)}
- H04L 63/10: {for controlling access to devices or network resources}
- H04L 63/166: {at the transport layer}
- H04L 63/0442: {wherein the sending and receiving network entities apply asymmetric encryption, i.e. different keys for encryption and decryption (cryptographic mechanisms or cryptographic arrangements for public-key encryption H04L9/30)}
- H04L 63/12: {Applying verification of the received information (cryptographic mechanisms or cryptographic arrangements for data integrity or data verification H04L9/32)}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

This disclosure pertains generally to client authentication. One aspect of the disclosure relates to a first server for presenting evidence to a Domain Controller (DC) of a first authentication context being submitted from a client to the first server to obtain a delegable credential, wherein the credential can be used to request a second authentication context from that client to a second server. Another aspect relates to the first server providing a pass-thru with evidence to a DC. The evidence relates to a first authentication context being submitted from a client to the first server that it obtained a delegable credential. The pass-thru is used in combination with the credential to request a second authentication context from the client to a second server.

## Claims

### Claim 1

An apparatus comprising:
a first server for presenting evidence to a Domain Controller (DC) of a first authentication context being submitted from a client to the first server to obtain a delegable credential, wherein the credential can be used to request a second authentication context from that same client to a second server.

### Claim 2 (depends on 1)

The apparatus of claim 1, wherein the second authentication context from that client to the second server is based on the first authentication context from that client to the first server.

### Claim 3 (depends on 1)

The apparatus of claim 1, wherein the first authentication context is based on a Kerberos ticket.

### Claim 4 (depends on 1)

The apparatus of claim 1, wherein the authentication context is based on a Secure Sockets Layer (SSL)/Transport Layer Security (TLS) security protocol.

### Claim 5 (depends on 1)

The apparatus of claim 1, wherein the first authentication context is based on a first ticket, and the second authentication context is based on a second ticket.

### Claim 6 (depends on 5)

The apparatus of claim 5, wherein the first ticket is a Kerberos ticket.

### Claim 7 (depends on 5)

The apparatus of claim 5, wherein the second ticket is a Kerberos ticket.

### Claim 8 (depends on 1)

The apparatus of claim 1, further comprising providing an SSL/TLS handshake protocol.

### Claim 9 (depends on 8)

The apparatus of claim 8, wherein the handshake protocol provides the first authentication context and the second authentication context.

### Claim 10 (depends on 1)

The apparatus of claim 1, further comprising the client generating a first master key, and the first server generating a second master key.

### Claim 11 (depends on 1)

The apparatus of claim 1, further comprising the client generating a first session key and the first server generating a second session key.

### Claim 12

A method comprising:
a first server providing a pass-thru with evidence to a Domain Controller (DC), wherein the evidence relates to a first authentication context being submitted from a client to the first server that it obtained a delegable credential; and
using the pass-thru in combination with the credential to request a second authentication context from the client to a second server.

### Claim 13 (depends on 12)

The method of claim 12, wherein the second authentication context from the client to the second server is based on the first authentication context from the client to the first server.

### Claim 14 (depends on 12)

The method of claim 12, wherein the first authentication context is based on a Kerberos ticket.

### Claim 15 (depends on 12)

The method of claim 12, wherein the authentication context is based on a secure sockets layer (SSL)/Transport Layer Security (TLS) security protocol.

### Claim 16 (depends on 12)

The method of claim 12, wherein the first authentication context is based on a first ticket, and the second authentication context is based on a second ticket.

### Claim 17 (depends on 16)

The method of claim 16, wherein the first ticket is a Kerberos ticket.

### Claim 18 (depends on 16)

The method of claim 16, wherein the second ticket is a Kerberos ticket.

### Claim 19 (depends on 12)

The method of claim 12, further comprising providing an SSL/TLS handshake protocol.

### Claim 20 (depends on 19)

The method of claim 19, wherein the handshake protocol provides the first authentication context and the second authentication context.

### Claim 21 (depends on 12)

The method of claim 12, further comprising the client generating a first master key, and the first server generating a second master key.

### Claim 22 (depends on 12)

The method of claim 12, further comprising the client generating a first session key and the first server generating a second session key.

### Claim 23

An apparatus, comprising:
a first ticket providing a first authentication context for authenticating a client for a first server by performing authentication calculations;
a second ticket providing a second authentication context for authenticating the client for a second server, wherein the second ticket is generated based on a pass-through with evidence produced by a Domain Controller (DC).

### Claim 24 (depends on 23)

The apparatus of claim 23, wherein the first ticket and the second ticket are both Kerberos tickets.

### Claim 25 (depends on 23)

The apparatus of claim 23, further comprising generating a credential at the DC.

### Claim 26 (depends on 23)

The apparatus of claim 23, further comprising a delegable credential that generates the second ticket from the first ticket.

### Claim 27 (depends on 23)

The apparatus of claim 23, wherein the evidence includes evidence authenticating the client for the first server.

### Claim 28 (depends on 23)

The apparatus of claim 23, wherein the DC re-computes the authentication calculations associated with the first authentication context for authenticating the client for the first server.

### Claim 29 (depends on 23)

The apparatus of claim 23, wherein the first ticket includes a Kerberos ticket.

### Claim 30 (depends on 23)

The apparatus of claim 23, wherein the second ticket includes a Kerberos ticket.

### Claim 31

A method comprising:
a client transmitting a request for an authentication context from a server;
the server performing authentication calculations in response to the request for authentication context;
the server transmitting the request for an authentication context to a Domain Controller (DC); and
the DC re-performing the authentication calculations associated with the client.

### Claim 32 (depends on 31)

The method of claim 31, wherein the request for the authentication context relates to a first authentication context being submitted from a client to the first server that it obtained a delegable credential; and
the request for authentication context transmitted from the server to the DC includes a pass-thru with evidence that is used to request a second authentication context from the client to a second server.

### Claim 33

A method of authenticating a client at a Domain Controller (DC) using a Secure Sockets Layer (SSL)/Transport Layer Security (TLS) security protocol.

### Claim 34

A method comprising:
authenticating a client at a server; and
proving to an authentication authority that the server authenticated, the client.

### Claim 35 (depends on 34)

The method of claim 34, wherein the authentication authority is a centralized authentication authority.

### Claim 36 (depends on 34)

The method of claim 34, further comprising passing the authentication of the client from the server to a second server.

### Claim 37 (depends on 34)

The method of claim 34, wherein the authentication of the client at the server is based on a Secure Sockets Layer/Transport Layer Security (SSL/TLS) handshake.

### Claim 38 (depends on 34)

The method of claim 34, wherein the proving to an authentication authority that the server authenticated the client is based on a Secure Sockets Layer/Transport Layer Security (SSL/TLS) handshake.

### Claim 39

A computer readable medium having computer executable instructions for performing steps comprising:
a first server providing a pass-thru with evidence to a Domain Controller (DC), wherein the evidence relates to a first authentication context being submitted from a client to the first server that it obtained a delegable credential; and
using the pass-thru in combination with the credential to request a second authentication context from the client to a second server.

### Claim 40

A computer readable medium having computer executable instructions for performing steps comprising:
authenticating a client at a server; and
proving to an authentication authority that the server authenticated the client.

### Claim 41 (depends on 40)

The computer readable medium having computer executable instructions for performing steps of claim 40, wherein the authentication authority is a centralized authentication authority.

### Claim 42 (depends on 40)

The computer readable medium having computer executable instructions for performing steps of claim 40, further comprising passing the authentication of the client from the server to a second server.

### Claim 43 (depends on 40)

The computer readable medium having computer executable instructions for performing steps of claim 40, wherein the authentication of the client at the server is based on a Secure Sockets Layer/Transport Layer Security (SSL/TLS) handshake.

### Claim 44 (depends on 40)

The computer readable medium having computer executable instructions for performing steps of claim 40, wherein the proving to an authentication authority that the server authenticated the client is based on a Secure Sockets Layer/Transport Layer Security (SSL/TLS) handshake.
