IP Library Granted Patent US 8,307,203
Granted Patent B2
US 8,307,203 · App. 12/502,983 · Granted Nov 6, 2012

Methods and systems for secure communications using a local certification authority

View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 8,307,203
App. No.
12/502,983
Granted
Nov 6, 2012
Kind
B2
Abstract

A local network traffic processor and an application are resident on a common computer system. The application is configured to trust a server certificate issued by a local network traffic processor, the local network traffic processor operatively being paired with a remote network traffic processor. A proxy server certificate, generated using identification information of a server associated with the remote network traffic processor and signed by the local certification authority, is used to establish a secure session between a local network traffic processor and the application.

Claims (52)

1. A method comprising:

determining that a local network traffic processor and a networked application are installed on a common trusted host;

in response to the determination, configuring the networked application to trust a server proxy certificate generated, using a server identifier, for a server associated with a remote network traffic processor that is issued and signed by a local certification authority unique to and associated with the local network traffic processor, the local network traffic processor operatively being paired with the remote network traffic processor to perform a network traffic processing function; and

using a proxy server certificate to establish a secure session between the local network traffic processor and the networked application.

2. The method of claim 1 , wherein the determination that the local network traffic processor is on a trusted host comprises determining that the local network traffic processor and the application are resident on a common computer system that is the trusted host.

3. The method of claim 1 , wherein the application comprises an SSL-enabled browser application and the configuring of the application to trust the server proxy certificate includes configuring the SSL-enabled application to trust an authority.

4. The method of claim 3 , wherein the configuring of the SSL-enabled application to trust the authority includes adding a certification authority (CA) certificate for the authority to a trusted certificate store used by the SSL-enabled application.

5. The method of claim 1 , including:

generating a private/public key pair for the server;

providing the public key of the private/public key pair to the authority; and

issuing the proxy server certificate, comprising the public key of the server signed using the private key of the authority, from the authority.

6. The method of claim 1 , including:

receiving, from the remote network traffic processor and at the local network traffic processor, a server identifier; and

generating the proxy server certificate at the authority using a private key of the local network traffic processor that is unique to the local network traffic processor.

7. The method of claim 6 , wherein the server identifier for a server comprises at least one of a common name or an alternate name of the server.

8. The method of claim 1 , wherein the local network traffic processor comprises a local traffic accelerator that operatively accelerates network traffic communicated with a remote traffic accelerator.

9. The method of claim 1 , wherein the authority forms part of the local network traffic processor.

10. A system comprising:

a configuration application to:

install a local network traffic processor and an networked application on a common trusted computer system; and

configure the networked application to trust a server certificate of the local network traffic processor, the local network traffic processor operatively being paired with a remote network traffic processor,

a local certification authority (CA), unique to and associated the local network traffic processor, to issue and sign a proxy server certificate using a server identifier for a server associated with the remote network traffic processor; and

the networked application to use the proxy server certificate to establish a secure session between the local network traffic processor and the networked application.

11. The system of claim 10 , wherein the networked application comprises a browser application and the configuring of the networked application to trust the server certificate includes configuring the browser application to trust the local CA.

12. The system of claim 10 , wherein the configuration application is to add a certification authority certificate for the local CA to a trusted certificate store used by the networked application.

13. The system of claim 10 , including:

generating a private/public key pair for the server;

providing at least the public key of the private/public key pair to the local certification authority; and

issuing the proxy server certificate from the local CA.

14. The system of claim 10 , including:

receiving, from the remote network traffic processor and at the local network traffic processor, the server identifier; and

generating the proxy server certificate at the local certification authority (CA) using a key pair generated for the server.

15. The system of claim 10 , wherein the local network traffic processor comprises a local traffic accelerator that operatively accelerates network traffic communicated with a remote traffic accelerator.

16. The system of claim 10 , wherein the local CA forms part of the local network traffic processor.

17. The system of claim 10 , wherein the server identifier for the server comprises at least one of a common name, an alternate name or an X509 attribute of the server.

18. A non-transitory machine-readable medium storing instructions that, when executed by a computer system, cause the computer system to perform a method comprising:

configuring a networked application to trust a proxy server certificate, using a server identifier for a server associated with a remote network traffic processor, that is issued and signed by a local certification authority, unique to and associated with a local network traffic processor installed on a common trusted host with the networked application, the local network traffic processor operatively being paired with the remote network traffic processor; and

using a proxy server certificate to establish a secure session between the local network traffic processor and the networked application.

19. A method comprising:

configuring a networked application to trust a proxy server certificate using a server identifier for a server associated with a remote network traffic processor, that is issued and signed by a local certification authority, unique to and associated with a local network traffic processor installed on a common trusted host with the networked application, the local network traffic processor operatively being paired with the remote network traffic processor; and

using a proxy server certificate to establish a secure session between local network traffic processor and the networked application.

20. The method of claim 19 , wherein the networked application comprises an SSL-enabled browser application and the configuring of the networked application to trust the server proxy certificate includes configuring the SSL-enabled application to trust the local certification authority.

21. The method of claim 19 , comprising:

generating a private/public key pair for a server;

providing the public key of the private/public key pair to the local certification authority; and

issuing the proxy server certificate, comprising the public key of the server signed using

the private key of the local certification authority, from the local certification authority.

22. The method of claim 21 , wherein the configuring of the SSL-enabled application to trust the local certification authority includes adding a certification authority (CA) certificate for the local certification authority to a trusted certificate store used by the SSL-enabled application.

23. The method of claim 19 , comprising:

receiving, from the remote network traffic processor and at the local network traffic processor, a server identifier; and

generating the proxy server certificate at the certification authority using a private key of the local network traffic processor that is unique to the local network traffic processor.

24. The method of claim 19 , wherein the local network traffic processor comprises a local traffic accelerator that operatively accelerates network traffic communicated with a remote traffic accelerator.

Assignments (18)
RELEASE OF SECURITY INTEREST Recorded Aug 11, 2023
From: ALTER DOMUS (US) LLC, AS COLLATERAL AGENT
To: RIVERBED TECHNOLOGY, INC.; ATERNITY LLC; RIVERBED HOLDINGS, INC.
Reel/Frame 064673/0739 →
CHANGE OF NAME Recorded Feb 18, 2022
From: RIVERBED TECHNOLOGY, INC.
To: RIVERBED TECHNOLOGY LLC
Reel/Frame 059232/0551 →
TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS Recorded Dec 27, 2021
From: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS U.S. COLLATERAL AGENT
To: RIVERBED TECHNOLOGY, INC.; ATERNITY LLC
Reel/Frame 058593/0169 →
TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS Recorded Dec 27, 2021
From: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT
To: RIVERBED TECHNOLOGY, INC.; ATERNITY LLC
Reel/Frame 058593/0046 →
TERMINATION AND RELEASE OF SECURITY INTEREST IN PATENTS Recorded Dec 27, 2021
From: ALTER DOMUS (US) LLC, AS COLLATERAL AGENT
To: RIVERBED TECHNOLOGY, INC.; ATERNITY LLC
Reel/Frame 058593/0108 →
SECURITY INTEREST Recorded Dec 10, 2021
From: RIVERBED TECHNOLOGY LLC (FORMERLY RIVERBED TECHNOLOGY, INC.); ATERNITY LLC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS U.S. COLLATERAL AGENT
Reel/Frame 058486/0216 →
PATENT SECURITY AGREEMENT Recorded Oct 27, 2021
From: RIVERBED TECHNOLOGY, INC.; ATERNITY LLC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION
Reel/Frame 057943/0386 →
PATENT SECURITY AGREEMENT SUPPLEMENT - FIRST LIEN Recorded Oct 14, 2021
From: RIVERBED HOLDINGS, INC.; RIVERBED TECHNOLOGY, INC.; ATERNITY LLC
To: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT
Reel/Frame 057810/0502 →
PATENT SECURITY AGREEMENT SUPPLEMENT - SECOND LIEN Recorded Oct 14, 2021
From: RIVERBED HOLDINGS, INC.; RIVERBED TECHNOLOGY, INC.; ATERNITY LLC
To: ALTER DOMUS (US) LLC, AS COLLATERAL AGENT
Reel/Frame 057810/0559 →
RELEASE OF SECURITY INTEREST IN PATENTS RECORED AT REEL 056397, FRAME 0750 Recorded Oct 13, 2021
From: MACQUARIE CAPITAL FUNDING LLC
To: RIVERBED HOLDINGS, INC.; RIVERBED TECHNOLOGY, INC.; ATERNITY LLC
Reel/Frame 057983/0356 →
SECURITY INTEREST Recorded May 26, 2021
From: RIVERBED HOLDINGS, INC.; RIVERBED TECHNOLOGY, INC.; ATERNITY LLC
To: MACQUARIE CAPITAL FUNDING LLC
Reel/Frame 056397/0750 →
PATENT SECURITY AGREEMENT Recorded Mar 5, 2021
From: RIVERBED TECHNOLOGY, INC.
To: ALTER DOMUS (US) LLC, AS COLLATERAL AGENT
Reel/Frame 055514/0249 →
CORRECTIVE ASSIGNMENT TO CORRECT THE CONVEYING PARTY NAME PREVIOUSLY RECORDED ON REEL 035521 FRAME 0069. ASSIGNOR(S) HEREBY CONFIRMS THE RELEASE OF SECURITY INTEREST IN PATENTS. Recorded Jun 2, 2015
From: JPMORGAN CHASE BANK, N.A.
To: RIVERBED TECHNOLOGY, INC.
Reel/Frame 035807/0680 →
SECURITY INTEREST Recorded May 1, 2015
From: RIVERBED TECHNOLOGY, INC.
To: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT
Reel/Frame 035561/0363 →
RELEASE OF SECURITY INTEREST IN PATENTS Recorded Apr 28, 2015
From: BARCLAYS BANK PLC
To: RIVERBED TECHNOLOGY, INC.
Reel/Frame 035521/0069 →
RELEASE OF PATENT SECURITY INTEREST Recorded Dec 26, 2013
From: MORGAN STANLEY & CO. LLC, AS COLLATERAL AGENT
To: RIVERBED TECHNOLOGY, INC.
Reel/Frame 032113/0425 →
SECURITY AGREEMENT Recorded Dec 20, 2012
From: RIVERBED TECHNOLOGY, INC.; OPNET TECHNOLOGIES, INC.
To: MORGAN STANLEY & CO. LLC
Reel/Frame 029646/0060 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 19, 2009
From: FRALEIGH, CHARLES; GUPTA, NITIN; LARSEN, CASE; MERUGU, SHASHIDHAR; OGREN, ERIC; SHAH, PARAS; SMOLSKY, OLEG
To: RIVERBED TECHNOLOGY, INC.
Reel/Frame 023120/0855 →