IP Library Granted Patent US 10,075,432
Granted Patent B2
US 10,075,432 · App. 15/208,735 · Granted Sep 11, 2018

Updating stored passwords

Inventors: Andy Tsang (San Jose, CA); Roger A. Chickering (Granite Bay, CA); Clifford E. Kahn (Westford, MA); Jeffrey C. Venable, Sr. (Union City, CA)
Assignee: Pulse Secure, LLC
H04L63/083G06F17/30097H04L9/3226H04L9/3236H04L63/126H04L67/02H04L67/42
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 10,075,432
App. No.
15/208,735
Granted
Sep 11, 2018
Kind
B2
Abstract

A device may include an authentication server and a server. The authentication server may receive a first form of a password from a client device in accordance with an authentication protocol, and authenticate the client device based on a comparison of the first form to a value derived from a second form of the password stored in a password database, where the comparison fails when the first form is not comparable to a value derived from the second form. The server may establish a secure connection to the client, receive a plain-text password from the client device over the secure connection, authenticate the client device by comparing a value derived from the plain-text password with a value derived from the second form, and update the password database with a third form of the password that permits the authentication server to successfully authenticate the client device when the authentication server receives the first form.

Claims (45)

1. A client device comprising:

an input/output device;

a processor communicatively coupled to the input/output device;

a memory storing executable instructions that, when executed by the processor,

instantiate an authentication client module and a re-authentication client module, the authentication client module configured to:

generate a plain-text password;

generate a first hash value based on the plain-text password, the first hash value generated according to a first hash generating scheme, the first hash generating scheme defining a first hash function that generates a first hash value based on an input value;

request, via the input/output device, access to a network comprising a network access device according to an authentication protocol;

send, via the input/output device, the first hash value to the network access device;

modify the first hash generating scheme to produce a second hash generating scheme, the second hash generating scheme defining a second hash function different than the first hash function that generates a second hash value based on the input value; and

generate a second hash value based on the plain-text password according to the second hash generating scheme; and

the re-authentication client module configured to:

in response to a policy server operating on the network receiving both the first hash value and the second hash value from the client device and failing to authenticate both the first hash value and the second hash value, establish, via the input/output device, a secure HTTP connection between the client device and the policy server; and

transmit, via the input/output device, the plain-text password from the client device to the policy server over the secure HTTP connection.

2. The client device of claim 1 , wherein the processor comprises a microprocessor or a hardware processing logic, and wherein the memory includes any one of a static memory, a dynamic memory, and an onboard cache for storing data and machine-readable instructions.

3. The client device of claim 2 , further comprising a network interface device comprising any one of a wired local area network interface device, a wired wide area network device, a wireless local area network interface device, a wireless wide area network interface device, and a cellular network interface device.

4. The client device of claim 1 , wherein generating the plain-text password comprises one of: prompting a user of the client device to enter the plain-text password, retrieving the plain-text password from the memory, and retrieving the plain-text password from another module operating on the client device.

5. The client device of claim 1 , wherein the authentication protocol is any one of a challenge-handshake authentication protocol (CHAP), a Microsoft (MS) CHAP (MSCHAP) authentication protocol, or a MSCHAP Version 2 (MSCHAPv2) authentication protocol.

6. The client device of claim 1 , wherein the re-authentication client module is further configured to transmit the plain-text password from the client device to the policy server in either one of the Hyper-Text Markup Language (HTML) or the Hyper-Text Transfer Language (HTTP).

7. The client device of claim 1 , wherein the authentication client module is configured to generate the second hash value based on the plain-text password according to the second hash generating scheme by downloading to the client device and installing on the client device a software update of the authentication client module.

8. The client device of claim 1 , wherein the authentication client module is further configured to:

receive a challenge string from the policy server;

store the challenge string on the memory; and

generate each of a first cryptographic hash value of the challenge string and the plain-text password and a second cryptographic hash value of the challenge string and the plain-text password based on one of the first hash generating scheme and the second hash generating scheme.

9. The client device of claim 8 , wherein the authentication client module is further configured to transmit each of the first cryptographic hash value and the second cryptographic hash value to the policy server.

10. The client device of claim 1 , wherein the secure HTTP connection between the client device and a policy server is a temporary connection.

11. The client device of claim 1 , wherein the policy server is further configured to configure the secure HTTP connection between the client device and the policy server to prevent the network access device from modifying the plain-text password.

12. The client device of claim 1 , wherein the policy server is further configured to configure the secure HTTP connection between the client device and a policy server by establishing a virtual local area network (VLAN) between the authentication client module and the policy server.

13. The client device of claim 1 , wherein the policy server is further configured to configure the secure HTTP connection between the client device and the policy server by transmitting an access control list to the network access device.

14. A method comprising:

generating, by an authentication client module of a client device comprising at least one hardware processor, a plain-text password;

generating, by the authentication client module, a first hash value based on the plain-text password according to a first hash generating scheme, the first hash generating scheme defining a first hash function that generates a first hash value based on an input value;

requesting, via an input/output device of the client device, access to a network comprising a network access device according to an authentication protocol;

sending, via the input/output device, the first hash value to the network access device;

modifying, by the authentication client module, the first hash generating scheme to produce a second hash generating scheme, the second hash generating scheme defining a second hash function different than the first hash function that generates a second hash value based on the input value;

generating, by the authentication client module, a second hash value based on the plain-text password according to the second hash generating scheme;

establishing, by a policy server communicatively coupled to the client device via a network, a secure HTTP connection between a re-authentication module of the client device and the policy server in response to the policy server receiving both the first hash value and the second hash value and failing to authenticate both the first hash value and the second hash value from the client device; and

transmitting, by the re-authentication client module via the input/output device, the plain-text password from the client device to the policy server over the secure HTTP connection.

15. The method of claim 14 , wherein generating the plain-text password comprises one of: prompting a user of the client device to enter the plain-text password, retrieving the plain-text password from the memory, and retrieving the plain-text password from another module operating on the client device.

16. The method of claim 14 , wherein the authentication protocol is any one of a challenge-handshake authentication protocol (CHAP), a Microsoft (MS) CHAP (MSCHAP) authentication protocol, or a MSCHAP Version 2 (MSCHAPv2) authentication protocol.

17. The method of claim 14 , wherein the plain-text password is transmitted from the client device to the policy server in either one of the Hyper-Text Markup Language (HTML) or the Hyper-Text Transfer Language (HTTP).

18. The method of claim 14 , wherein the second hash value is generated based on the plain-text password according to the second hash generating scheme by downloading to the client device and installing on the client device a software update of the authentication client module.

19. The method of claim 14 , wherein the secure HTTP connection between the client device and a policy server is a temporary connection.

20. The method of claim 14 , wherein the secure HTTP connection between the client device and a policy server is configured to prevent the network access device from modifying the plain-text password.

21. The client device of claim 1 , wherein the second hash function is a function of the first hash function.

Assignments (14)
CORRECTIVE ASSIGNMENT TO CORRECT THE PROPERTY 14633493 WHICH WAS ENTERED INCORRECTLY AS 14633793 PREVIOUSLY RECORDED ON REEL 71176 FRAME 315. ASSIGNOR(S) HEREBY CONFIRMS THE FIRST LIEN NEWCO SECURITY AGREEMENT. Recorded Nov 10, 2025
From: PULSE SECURE, LLC; IVANTI, INC.; IVANTI US LLC; IVANTI SECURITY HOLDINGS LLC
To: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT
Reel/Frame 073818/0515 →
FIRST LIEN NEWCO SECURITY AGREEMENT Recorded May 5, 2025
From: PULSE SECURE, LLC; IVANTI, INC.; IVANTI US LLC; IVANTI SECURITY HOLDINGS LLC
To: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT
Reel/Frame 071176/0315 →
SECURITY INTEREST Recorded May 3, 2025
From: PULSE SECURE LLC
To: ALTER DOMUS (US) LLC
Reel/Frame 071165/0027 →
NOTICE OF SUCCESSION OF AGENCY FOR SECURITY INTEREST AT REEL/FRAME 054665/0873 Recorded Apr 29, 2025
From: BANK OF AMERICA, N.A., AS RESIGNING AGENT
To: ALTER DOMUS (US) LLC, AS SUCCESSOR AGENT
Reel/Frame 071123/0386 →
SECURITY INTEREST Recorded Dec 9, 2020
From: CELLSEC, INC.; PULSE SECURE, LLC; IVANTI, INC.; MOBILEIRON, INC.; IVANTI US LLC
To: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT
Reel/Frame 054665/0062 →
SECURITY INTEREST Recorded Dec 9, 2020
From: CELLSEC, INC.; PULSE SECURE, LLC; INVANTI, INC.; MOBILEIRON, INC.; INVANTI US LLC
To: BANK OF AMERICA, N.A., AS COLLATERAL AGENT
Reel/Frame 054665/0873 →
RELEASE OF SECURITY INTEREST : RECORDED AT REEL/FRAME - 053638-0220 Recorded Dec 1, 2020
From: KKR LOAN ADMINISTRATION SERVICES LLC
To: PULSE SECURE, LLC
Reel/Frame 054559/0368 →
SECURITY INTEREST Recorded Aug 29, 2020
From: PULSE SECURE, LLC
To: KKR LOAN ADMINISTRATION SERVICES LLC, AS COLLATERAL AGENT
Reel/Frame 053638/0220 →
RELEASE OF SECURITY INTEREST RECORDED AT REEL/FRAME 042380/0859 Recorded Aug 29, 2020
From: CERBERUS BUSINESS FINANCE, LLC, AS AGENT
To: PULSE SECURE, LLC
Reel/Frame 053638/0259 →
RELEASE OF SECURITY INTEREST Recorded Jul 21, 2020
From: JUNIPER NETWORKS, INC.
To: PULSE SECURE, LLC
Reel/Frame 053269/0339 →
GRANT OF SECURITY INTEREST PATENTS Recorded May 1, 2017
From: PULSE SECURE, LLC
To: CERBERUS BUSINESS FINANCE, LLC, AS COLLATERAL AGENT
Reel/Frame 042380/0859 →
SECURITY INTEREST Recorded May 1, 2017
From: PULSE SECURE, LLC
To: JUNIPER NETWORKS, INC.
Reel/Frame 042197/0822 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 13, 2016
From: TSANG, ANDY; CHICKERING, ROGER A.; KAHN, CLIFFORD E.; VENABLE, JEFFREY C., SR.
To: JUNIPER NETWORKS, INC.
Reel/Frame 039144/0825 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 13, 2016
From: JUNIPER NETWORKS, INC.
To: PULSE SECURE, LLC
Reel/Frame 039144/0835 →
Continuity (4)
Continuation 14659618 · Mar 17, 2015
Continuation 13312062 · Dec 6, 2011
Continuation 11864598 · Sep 28, 2007
Related Publication 20160323263A1 · Nov 3, 2016