Virtual folders for tracking HTTP sessions

• US 7,886,061 B1
• Filed: 01/27/2009
• Issued: 02/08/2011
• Est. Priority Date: 11/17/2004
• Status: Active Grant

• Current Assignee: Juniper Networks Incorporated
• Original Assignee: Juniper Networks Incorporated
• Inventors: Cheng, Chunqing
• Primary Examiner(s): Jean; Frantz B
• Application Number:
  US12/360,320
• Time in Patent Office: 742 Days
• Field of Search: 709/227, 709/228, 715/811
• US Class Current: 709/227
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32
• CPC Class Codes: H04L 63/0876 based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
• CPC Class Codes: H04L 63/168 above the transport layer
• CPC Class Codes: H04L 67/02 based on web technology, e.g. hypertext transfer protocol [HTTP]
• CPC Class Codes: H04L 67/14 Session management for real-time applications in data packet communications networks H04L65/1066

Abstract

Requests from a client to a network device are authenticated based on a session ID obtained by the network device. Requests may be authenticated by obtaining a session ID value when a session is initiated and transmitting a document to the client that embeds the session ID in such a manner that additional requests to the network device based on the document include the session ID in the request. The additional requests are authenticated based on a determination of whether the session ID is included in the additional requests.

Claims

1. A method performed by a network device, comprising:

concurrently hosting a plurality of different communication sessions;

generating, after a session login, a session identification (ID) for each of the plurality of communication sessions;

storing the session IDs;

embedding each of the session IDs in a respective one of a plurality of documents, each of the plurality of documents corresponding to a particular one of the plurality of communication sessions;

transmitting the documents as part of the particular one of the plurality of communication sessions; and

distinguishing received requests associated with the particular one of the plurality of communication sessions based on the session ID included in the requests, without using at least one of cookies, a login name, credential information, or an Internet protocol address related to the requests.

2. The method of claim 1, further comprising:

distinguishing the received requests without using at least two of cookies, a login name, credential information, or an Internet protocol address.

3. The method of claim 1, further comprising:

distinguishing the received requests without using at least three of cookies, a login name, credential information, or an Internet protocol address.

4. The method of claim 1, further comprising:

distinguishing the received requests without using any of cookies, a login name, credential information, or an Internet protocol address.

5. The method of claim 1, where the plurality of different communication sessions comprise stateless protocol sessions.

6. The method of claim 1, where concurrently hosting a plurality of different communication sessions comprises:

communicating with a plurality of clients that appear to the network device as having a single Internet protocol address.

7. The method of claim 1, where concurrently hosting a plurality of different communication sessions comprises:

communicating with a single administrator using at least one of different login names or different passwords for separate ones of the different communication sessions.

8. The method of claim 1, where embedding each of the session IDs comprises:

using at least one of a virtual folder, a query string, or a hidden form field.

9. The method of claim 1, where transmitting the documents comprises:

transmitting at least one of a hyper-text markup language (HTML) page or a user interface.

10. The method of claim 1, where distinguishing received requests comprises:

extracting the session ID from a received request, and

matching the extracted session ID to one of the stored session IDs to determine if the extracted session ID is valid.

11. A computer-readable memory device that stores instructions executable by at least one processor, comprising:

instructions to generate, after a session login, a session identification (ID) for a communication session;

instructions to store the session ID with a plurality of other session IDs;

instructions to embed the session ID in a document;

instructions to transmit the document as part of the communication session;

instructions to receive, during the communication session, a request based on the document;

instructions to determine whether the session ID is included in the request; and

instructions to grant the request, without using at least one of cookies, a login name, credential information, or an Internet protocol address related to the request, when the session ID is included the request.

12. The computer-readable memory device of claim 11, where the instructions to grant the request comprise:

instructions to grant the request, without using at least two of cookies, a login name, credential information, or an Internet protocol address related to the request, when the session ID is included the request.

13. The computer-readable memory device of claim 11, where the instructions to grant the request comprise:

instructions to grant the request, without using at least three of cookies, a login name, credential information, or an Internet protocol address related to the request, when the session ID is included the request.

14. The computer-readable memory device of claim 11, where the instructions to grant the request comprise:

instructions to grant the request, without using any of cookies, a login name, credential information, or an Internet protocol address related to the request, when the session ID is included the request.

15. The computer-readable memory device of claim 11, where the communication session comprises a stateless protocol session.

16. The computer-readable memory device of claim 11, where instructions to embed the session ID comprises:

instructions to use at least one of a virtual folder, a query string, or a hidden form field.

17. The computer-readable memory device of claim 11, where instructions to transmit the document comprises:

instructions to transmit a hyper-text markup language (HTML) page.

18. The computer-readable memory device of claim 11, where instructions to transmit the document comprises:

instructions to transmit a management interface.

19. The computer-readable memory device of claim 11, where the instructions to determine whether the session ID is included in the request comprises:

instructions to extract the session ID from the request, and

instructions to compare the extracted session ID to the stored session IDs to determine a match.

20. A system comprising:

means for concurrently hosting a plurality of different communication sessions;

means for generating, after a session login, a session identification (ID) for each of the plurality of communication sessions;

means for storing the session IDs;

means for embedding each of the session IDs in a respective one of a plurality of documents, each of the plurality of documents corresponding to a particular one of the plurality of communication sessions;

means for transmitting the documents with the embedded session IDs as part of the particular one of the plurality of communication sessions; and

means for distinguishing received requests associated with the particular one of the plurality of communication sessions based on session IDs included in the requests and the stored session IDs, without using at least one of cookies, a login name, credential information, or an Internet protocol address related to the received requests.