IP Library Granted Patent US 10,455,025
Granted Patent B2
US 10,455,025 · App. 15/226,499 · Granted Oct 22, 2019

Multi-factor authentication

Inventors: Lloyd Leon Burch (Payson, UT); Gulshan Govind Vaswani (Bangalore, IN); Sureshkumar Thangavel (Bangalore, IN); Rik Peters (Etten-Leur, NL)
Assignee: Micro Focus Software Inc.
H04L67/14H04L63/08H04L63/18H04L2463/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 10,455,025
App. No.
15/226,499
Granted
Oct 22, 2019
Kind
B2
Abstract

An authenticated session with a remote system is established and identified through an authentication token for the session. During that session, a resource is accessed requiring additional authentication beyond what the authentication token was originally authorized for. Out-of-band processing from the existing session performs the additional authentication and permission from the authentication token are upgraded to include permissions for accessing the resource during the session. The resource is accessed during the session with the authentication token having the upgraded permissions.

Claims (38)

1. A method, comprising:

issuing a token to a first device operated by a principal for a session between the principal and a service by providing the token as an authentication token for the session when the principal authenticates for access to the service and linking the token to session access rights for the session;

obtaining a session key to access the session between the principal and the service, and obtaining a hook to a principal service of the first device;

receiving a request from the service to validate the token for principal access to a resource of the service during the session and determining that the session access rights lacks permission to access the resource during the session, wherein the service is executed on a second device;

establishing an out-of-band communication channel with the principal service of the first device using the hook;

verifying a credential provided over the out-of-band communication channel from the principal service of the first device; and

upgrading permissions associated with the session access rights linked to the token and authorizing the principal to access the resource on the second device during the session based on verifying the credential and by using the session key and without changing the token.

2. The method of claim 1 , wherein issuing further includes causing the principal service to be instantiated on the first device associated with the principal in response to issuing the token.

3. The method of claim 2 , wherein obtaining further includes receiving the hook as a link to the principal service in response to issuing the token after the principal service is instantiated on the first device and receiving the link from the principal service.

4. The method of claim 1 , wherein issuing further includes performing a first factor authentication on the principal for establishing the session between the principal and the service.

5. The method of claim 1 , wherein establishing further includes establishing the out-of-band communication channel by pushing a notification to the principal service using the hook.

6. The method of claim 1 , wherein establishing further includes establishing the out-of-band communication channel in response to a status request received from the principal service.

7. The method of claim 1 , wherein establishing further includes maintaining the out-of-band communication channel while the session remains active between the principal and the service.

8. The method of claim 1 , wherein establishing further includes instructing the principal service to obtain a credential type associated with the credential from the principal over the out-of-band communication channel.

9. The method of claim 8 , wherein instructing further includes determining the credential type based on evaluation of a policy associated with the resource.

10. The method of claim 1 , wherein verifying further includes notifying the service that the token presented is authorized to access the resource during the session.

11. A method, comprising:

receiving, on a principal device, a token as an authentication taken for an initiated session between a principal and a service that executes on a service device, wherein receiving further includes receiving the token from an identity provider device that executes an identity provider;

notifying, by the principal device, the identity provider over an out-of-band communication Channel of the token and the session by providing the identity provider a session key for the session, the token, and a hook to interact with the method over the out-of-band communication channel;

obtaining, by the principal device, an instruction from the identity provider over the out-of-band communication channel to obtain a credential from the principal during the session;

interacting, by the principal device, with the principal for obtaining the credential; and

providing, by the principal device, the credential to the identity provider over the out-of-band communication channel for the identity provider to upgrade existing permissions associated with the token during the session without changing the token based on verification of the credential by the identity provider that was processed over the out-of-band communication channel during the session.

12. The method of claim 11 , wherein receiving further includes receiving the token from the identity provider when the identity provider authenticates the session using a first factor credential provided by the principal.

13. The method of claim 11 , wherein obtaining further includes receiving the instruction in response to a push notification sent from the identity provider over the out-of-band communication channel.

14. The method of claim 11 , wherein obtaining further includes receiving the instruction in response to a request sent to the identity provider over the out-of-band communication channel.

15. The method of claim 11 , wherein obtaining further includes initiating an interface window on the principal device being operated by the principal in response to obtaining the instruction.

16. The method of claim 15 , wherein initiating further includes customizing the interface window for obtaining the credential from the principal as a specific credential type identified in the instruction.

17. The method of claim 11 , wherein obtaining further includes initiating a device driver on the principal device being operated by the principal in response to the instruction, wherein the device driver associated with a peripheral device that is interfaced to the principal device and the peripheral device is equipped for obtaining the credential from the principal.

18. A device, comprising:

a hardware processor; and

a non-transitory computer-readable storage medium including executable instructions executable by the hardware processor to:

provide a token as an authentication token for a principal that operates a principal device and a service that executes on a service device to establish a session with one another using a first set of permissions, wherein the token is linked to the first set of permissions;

obtain a session key for the session and obtain a hook to a principal service that executes on the principal device;

utilize a back channel of communication to the principal service using the hook to obtain a credential for the principal during the session when the principal attempts to access a resource during the session that the first set of permissions lack access rights to access for the session and

upgrade the first set of permissions to a second set of permissions for the session using the session key without changing the token for the session when the credential provided over the back channel is successfully validated.

19. The device of claim 18 , wherein the non-transitory computer-readable storage medium further includes instructions executable by the hardware processor to:

authenticate the principal for the session as a first factor authentication and provide the token based on the first set of permissions; and

authenticate the principal for the upgraded second set of permissions as a second factor authentication based on validation of the credential over the back channel.

Assignments (5)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Feb 11, 2026
From: MICRO FOCUS SOFTWARE INC.
To: MICRO FOCUS LLC
Reel/Frame 073758/0781 →
RELEASE OF SECURITY INTEREST REEL/FRAME 044183/0718 Recorded Feb 2, 2023
From: JPMORGAN CHASE BANK, N.A.
To: MICRO FOCUS LLC (F/K/A ENTIT SOFTWARE LLC); BORLAND SOFTWARE CORPORATION; MICRO FOCUS (US), INC.; SERENA SOFTWARE, INC; ATTACHMATE CORPORATION; MICRO FOCUS SOFTWARE INC. (F/K/A NOVELL, INC.); NETIQ CORPORATION
Reel/Frame 062746/0399 →
SECURITY INTEREST Recorded Oct 11, 2017
From: ATTACHMATE CORPORATION; BORLAND SOFTWARE CORPORATION; NETIQ CORPORATION; MICRO FOCUS (US), INC.; MICRO FOCUS SOFTWARE, INC.; ENTIT SOFTWARE LLC; ARCSIGHT, LLC; SERENA SOFTWARE, INC.
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 044183/0718 →
CHANGE OF NAME Recorded Sep 13, 2016
From: NOVELL, INC.
To: MICRO FOCUS SOFTWARE INC.
Reel/Frame 040020/0703 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 23, 2016
From: BURCH, LLOYD LEON; VASWANI, GULSHAN GOVIND; THANGAVEL, SURESHKUMAR; PETERS, RIK
To: NOVELL, INC.
Reel/Frame 039510/0584 →
Cited By (2)
US 12,316,762 US 12,375,478