IP Library Granted Patent US 11,520,868
Granted Patent B2
US 11,520,868 · App. 16/829,779 · Granted Dec 6, 2022

Multi-factor authentication with URL validation

Inventors: William Dudley (Lovettsville, VA); Steven Garcia (South Riding, VA); Khalid Abdullah (Ashburn, VA); Fernando Nakano (Reston, VA)
Assignee: Sybase 365, Inc.
G06F21/31G06F21/35H04L9/3215H04L9/3271H04L63/08H04L63/18H04L67/02H04W12/06G06F2221/2111G06F2221/2137H04L2463/082
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 11,520,868
App. No.
16/829,779
Granted
Dec 6, 2022
Kind
B2
Abstract

Techniques are provided for providing multi-factor authentication with Uniform Resource Locator (URL) validation (MFAUV). One of the multiple authentication factors used may include a unique, user-specific URL that is sent to the user within a message. In this way, the user may simply click on, or otherwise execute or select, the provided URL, directly from within the message in which the URL is provided.

Claims (56)

1. A computer program product, the computer program product being tangibly embodied on a non-transitory computer-readable storage medium and comprising instructions that, when executed, are configured to cause at least one computing device to:

receive an authentication request from a first user for access to a network resource via a first communications channel, the authentication request including at least one authentication parameter;

input the at least one authentication parameter into an authentication code generator to generate a user-specific authentication code, wherein the at least one authentication parameter comprises a password of the first user and an expiration time defined with respect to a time of the authentication request;

after receiving the authentication request, generate, using the at least one authentication parameter received from the first user, a user-specific authentication Uniform Resource Locator (URL) for an access page based on the user-specific authentication code;

send the user-specific authentication URL to the first user via a second communications channel;

receive an access request in response to selection of the user-specific authentication URL by a second user, the access request associated with at least one access parameter, wherein the at least one access parameter is not a part of the authentication URL, and wherein the at least one access parameter identifies the second user associated with the access request;

validate the access request, wherein validating the access request comprises matching the at least one authentication parameter with the at least one access parameter to confirm that the first user and the second user are the same, wherein the first user and the second user are the same when the at least one authentication parameter corresponds to the at least one access parameter received from the second user; and

provide the access page to the first user, in response to the matching, the access page indicating grant of access to the network resource.

2. The computer program product of claim 1 , wherein the authentication request and the validated access request provide a first authentication factor, and wherein the authentication request is received in conjunction with at least a second authentication request that relies on a second authentication factor, to thereby provide multi-factor authentication of the first user with respect to the network resource.

3. The computer program product of claim 1 , wherein the at least one authentication parameter includes a telephone number of a mobile device of the first user to which the authentication URL is sent.

4. The computer program product of claim 1 , wherein the instructions, when executed, are further configured to generate the user-specific authentication code using a one-time password hashing algorithm.

5. The computer program product of claim 1 , wherein the instructions, when executed, are further configured to:

receive the authentication request by way of a client application program interface (API) of a client providing the network resource,

wherein the authentication request is supplemented at the client to include at least one client-specific authentication parameter that is then used when generating the user-specific authentication URL.

6. The computer program product of claim 5 , wherein the authentication URL is generated using data types that are not the same data type as the at least one access parameter, and wherein the instructions, when executed, are further configured to:

notify the client of the validation of the access request.

7. The computer program product of claim 1 , wherein the at least one authentication parameter and the at least one access parameter each includes location information of the first user, and wherein the instructions, when executed, are further configured to validate the access request including verifying a match between the location information of the at least one authentication parameter and the location information of the at least one access parameter.

8. The computer program product of claim 1 , wherein the instructions, when executed, are further configured to:

generate a message in response to the authentication request;

include the authentication URL within the message;

send the message to the first user via the second communications channel; and

receive the access request in response to the selection of the authentication URL from within the message.

9. The computer program product of claim 1 , wherein the instructions, when executed, are further configured to:

provide the access page including a quick review (QR) code; and

provide the network resource in response to receipt of a scanning of the QR code.

10. The computer program product of claim 1 , wherein generating the user-specific authentication code comprises generating, using a time when the authentication request is received, the user-specific authentication code.

11. A computer-implemented method, comprising:

receiving an authentication request from a first user for access to a network resource via a first communications channel, the authentication request including at least one authentication parameter;

inputting the at least one authentication parameter into an authentication code generator to generate a user-specific authentication code, wherein the at least one authentication parameter comprises a password of the first user and an expiration time defined with respect to a time of the authentication request;

after receiving the authentication request, generating, using the at least one authentication parameter received from the first user, a user-specific authentication Uniform Resource Locator (URL) for an access page based on the user-specific authentication code;

sending the user-specific authentication URL to the first user via a second communications channel;

receiving an access request in response to selection of the user-specific authentication URL by a second user, the access request associated with at least one access parameter, wherein the at least one access parameter is not a part of the authentication URL, and wherein the at least one access parameter identifies the second user associated with the access request;

validating the access request, wherein validating the access request comprises matching the at least one authentication parameter with the at least one access parameter to confirm that the first user and the second user are the same, wherein the first user and the second user are the same when the at least one authentication parameter corresponds to the at least one access parameter received from the second user; and

providing the access page to the first user, in response to the matching, the access page indicating grant of access to the network resource.

12. The method of claim 11 , wherein the authentication request and the validated access request provide a first authentication factor, and wherein the authentication request is received in conjunction with at least a second authentication request that relies on a second authentication factor, to thereby provide multi-factor authentication of the first user with respect to the network resource.

13. The method of claim 11 , wherein the at least one authentication parameter includes a telephone number of a mobile device of the first user to which the authentication URL is sent.

14. The method of claim 11 , further comprising:

receiving the authentication request by way of a client application program interface (API) of a client providing the network resource,

wherein the authentication request is supplemented at the client to include at least one client-specific authentication parameter that is then used when generating the user-specific authentication URL.

15. The method of claim 11 , further comprising:

generating a message in response to the authentication request;

including the authentication URL within the message;

sending the message to the first user via the second communications channel; and

receiving the access request in response to the selection of the authentication URL from within the message.

16. A computer-implemented system, comprising:

one or more computers; and

one or more computer memory devices interoperably coupled with the one or more computers and having tangible, non-transitory, machine-readable media storing one or more instructions that, when executed by the one or more computers, perform one or more operations comprising:

receiving an authentication request from a first user for access to a network resource via a first communications channel, the authentication request including at least one authentication parameter;

inputting the at least one authentication parameter into an authentication code generator to generate a user-specific authentication code, wherein the at least one authentication parameter comprises a password of the first user and an expiration time defined with respect to a time of the authentication request;

after receiving the authentication request, generating, using the at least one authentication parameter received from the first user, a user-specific authentication Uniform Resource Locator (URL) for an access page based on the user-specific authentication code;

sending the user-specific authentication URL to the first user via a second communications channel;

receiving an access request in response to selection of the user-specific authentication URL by a second user, the access request associated with at least one access parameter, wherein the at least one access parameter is not a part of the authentication URL, and wherein the at least one access parameter identifies the second user associated with the access request;

validating the access request, wherein validating the access request comprises matching the at least one authentication parameter with the at least one access parameter to confirm that the first user and the second user are the same, wherein the first user and the second user are the same when the at least one authentication parameter corresponds to the at least one access parameter received from the second user; and

providing the access page to the first user, in response to the matching, the access page indicating grant of access to the network resource.

17. The computer-implemented system of claim 16 , wherein the authentication request and the validated access request provide a first authentication factor, and wherein the authentication request is received in conjunction with at least a second authentication request that relies on a second authentication factor, to thereby provide multi-factor authentication of the first user with respect to the network resource.

18. The computer-implemented system of claim 16 , wherein the at least one authentication parameter includes a telephone number of a mobile device of the first user to which the authentication URL is sent.

Assignments (3)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 27, 2021
From: SYBASE 365, LLC
To: SYBASE, INC.
Reel/Frame 055049/0216 →
CHANGE OF NAME Recorded Jan 27, 2021
From: SYBASE 365, INC.
To: SYBASE 365, LLC
Reel/Frame 055560/0178 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Mar 25, 2020
From: DUDLEY, WILLIAM; GARCIA, STEVEN; ABDULLAH, KHALID; NAKANO, FERNANDO
To: SYBASE 365, INC.
Reel/Frame 052227/0246 →
Continuity (2)
Continuation 15692754 · Aug 31, 2017
Related Publication 20200226236A1 · Jul 16, 2020