Secure traversal of network components
First Claim
Patent Images
1. A method of authenticating a client to a content server comprising the steps of:
- generating, by a ticket authority, a ticket associated with said client, said ticket comprising a first ticket and a second ticket wherein said second ticket is disabled from use, said disabled second ticket validated by said ticket authority after the second ticket is enabled by said ticket authority;
transmitting, by said ticket authority, said first ticket to said client;
validating, by said ticket authority, said first ticket;
using, by said client, said first ticket to establish a communication session with a content server proxy after said first ticket is validated;
enabling, by said ticket authority, said second ticket for use upon said validation of said first ticket, said enabled second ticket validated by said ticket authority; and
using, by said content server proxy, said enabled second ticket to establish a communication session with said content server.
8 Assignments
0 Petitions
Accused Products
Abstract
A method and apparatus for authenticating a client to a content server. A ticket authority generates a ticket associated with the client. The ticket comprises a first ticket and a second ticket. The ticket authority transmits the first ticket to the client and the client uses the first ticket to establish a communication session with an content server proxy. The ticket authority then transmits a second ticket to the content server proxy and the content server proxy uses the second ticket to establish a communication session with the content server.
-
Citations
67 Claims
-
1. A method of authenticating a client to a content server comprising the steps of:
-
generating, by a ticket authority, a ticket associated with said client, said ticket comprising a first ticket and a second ticket wherein said second ticket is disabled from use, said disabled second ticket validated by said ticket authority after the second ticket is enabled by said ticket authority; transmitting, by said ticket authority, said first ticket to said client; validating, by said ticket authority, said first ticket; using, by said client, said first ticket to establish a communication session with a content server proxy after said first ticket is validated; enabling, by said ticket authority, said second ticket for use upon said validation of said first ticket, said enabled second ticket validated by said ticket authority; and using, by said content server proxy, said enabled second ticket to establish a communication session with said content server. - View Dependent Claims (2, 3, 4, 5, 6, 7, 8, 9, 10, 11, 12, 13, 14, 15, 16, 17, 18, 19, 20, 21, 22)
-
-
23. A system for authenticating a user comprising:
-
a client; a ticket authority; a content server; and a content server proxy in communication with said client, said ticket authority, and said content server, wherein said ticket authority generates a first ticket and a second ticket, said second ticket is generated before said first ticket is validated by the ticket authority and said second ticket is disabled from use, said disabled second ticket validated by said ticket authority after the second ticket is enabled by said ticket authority; wherein said first ticket is transmitted to said client and used to establish a first communication session with said content server proxy, and wherein said second ticket is transmitted to said content server proxy and used to establish a second communication session with said content server. - View Dependent Claims (24, 25, 26, 27, 28, 29, 30, 31, 32, 33, 34, 35, 36, 37, 38, 39, 40, 41, 42, 43, 44)
-
-
45. A system for authenticating a user comprising:
-
a client; a ticket authority generating a first ticket and a second ticket wherein said second ticket is generated before said first ticket is validated and said second ticket disabled from use, said disabled second ticket validated by said ticket authority after the second ticket is enabled by said ticket authority; a content server; a content server proxy in communication with said client, said ticket authority, and said content server and receiving said first ticket; and a web server in communication with said client and said ticket authority, wherein said content server proxy establishes a first communication session between said client and said content server proxy after said ticket authority validates said first ticket, wherein said ticket authority enables said second ticket after said validation of said first ticket, said enabled second ticket validated by said ticket authority, and wherein said content server proxy uses said enabled second ticket to establish a second communication session with a protocol different from said first communication session protocol. - View Dependent Claims (46, 47, 48, 49, 50, 51, 52, 53, 54, 55, 56, 57, 58, 59, 60, 61, 62, 63, 64, 65, 66)
-
-
67. A system for authenticating a user comprising:
-
means for generating, by a ticket authority, a first ticket and a second ticket, wherein said second ticket is generated before said first ticket is validated by the ticket authority and said second ticket disabled from use, said disabled second ticket validated by said ticket authority after the second ticket is enabled by said ticket authority; means for transmitting, by said ticket authority, said first ticket to said client; means for using, by said client, said first ticket to establish a first communication session with a content server proxy; means for transmitting, by said ticket authority, said second ticket to said content server proxy; and means for using, by said content server proxy, said second ticket to establish a second communication session with a content server.
-
Specification