IP Library Granted Patent US 11,489,833
Granted Patent B2
US 11,489,833 · App. 16/263,889 · Granted Nov 1, 2022

Methods, systems, and apparatuses for improved multi-factor authentication in a multi-app communication system

Inventors: Mark Pike (Oakland, CA); Roland Schemers (Woodside, CA); James McPhail (San Francisco, CA); Matthew Wahl (San Francisco, CA)
Assignee: Slack Technologies, LLC
H04L63/0884H04L63/102
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,489,833
App. No.
16/263,889
Granted
Nov 1, 2022
Kind
B2
Abstract

Embodiments of the present disclosure relate to verifying a third-party resource by automatically validating multi-factor message codes associated with the third-party resource to enable access to functionality associated with the third-party resource via a multi-app communication system. An example embodiment includes a multi-app communication system including at least one processor and at least one memory. The embodiment multi-app communication system is configured to receive a sign-in request from a multi-app communication system application executed on a client device, and cause transmission of a multi-factor confirmation message to a verified third-party multi-factor authentication resource. The embodiment multi-app communication system is further configured query the verified third-party multi-factor authentication resource to identify the multi-factor confirmation message, and enable access to the third-party resource.

Claims (70)

1. A multi-app communication system capable of communication with a verified third-party multi-factor authentication resource, wherein the multi-app communication system is configured to provide authenticated access to a third-party resource via a multi-app communication system application executed on a client device, and wherein the multi-app communication system comprises at least a processor, and a memory associated with the processor having computer coded instructions therein, with the computer coded instructions configured to, when executed by the processor, cause the multi-app communication system to:

launch an authenticated session associated with an authenticated user account;

receive a third-party sign-in request from a multi-app communication system application executed on the client device during the authenticated session associated with an authenticated user account;

cause transmission of a multi-factor confirmation message to the verified third-party multi-factor authentication resource;

query the verified third-party multi-factor authentication resource to identify the multi-factor confirmation message;

automatically extract a multi-factor message code from the multi-factor confirmation message for authentication without user engagement; and

enable access to the third-party resource during the authenticated session associated with the authenticated user account.

2. The multi-app communication system of claim 1 , wherein the computer coded instructions are further configured to cause the multi-app communication system to:

cause validation of the multi-factor message code.

3. The multi-app communication system of claim 2 , wherein the computer coded instructions configured to cause the multi-app communication system to extract the multi-factor message code from the multi-factor confirmation message are further configured to cause the multi-app communication system to:

parse the multi-factor confirmation message to identify an authentication link comprising the multi-factor message code; and

extract the multi-factor message code from the authentication link.

4. The multi-app communication system of claim 1 , wherein the computer coded instructions are further configured to cause the multi-app communication system to:

generate a sign-in prompt interface; and

cause the client device, via the multi-app communication system application, to render the sign-in prompt interface,

wherein the third-party sign-in request is received in response to engagement with the sign-in prompt interface via the client device.

5. The multi-app communication system of claim 1 , wherein the computer coded instructions are further configured to:

receive verified resource information associated with the third-party resource, wherein the verified resource information is configured to enable access to the third-party resource; and

store the verified resource information associated with the authenticated user account.

6. The multi-app communication system of claim 5 , wherein the verified resource information comprises a third-party resource authentication token associated with the third-party resource.

7. The multi-app communication system of claim 1 , wherein the computer coded instructions are further configured to:

identify user account details associated with the authenticated user account;

cause the third-party resource to validate the user account details to the third-party resource using a primary authentication method; and

receive an authentication response indicating the user account details are associated with a third-party resource user account.

8. The multi-app communication system of claim 1 , wherein the computer coded instructions are further configured to cause the multi-app communication system to:

transmit a third-party multi-factor authentication resource access request;

cause the client device, via the multi-app communication system application, to render a third-party multi-factor authentication resource access prompt interface; and

receive third-party multi-factor authentication resource access approval in response to user engagement with the third-party multi-factor authentication resource access prompt interface.

9. The multi-app communication system of claim 1 , wherein the computer coded instructions are further configured to cause the multi-app communication system to:

transmit a third-party resource access request;

cause the client device, via the multi-app communication system application, to render a third-party resource access prompt interface; and

receive a third-party resource access approval in response to user engagement with the third-party resource access prompt interface.

10. The multi-app communication system of claim 1 , wherein the computer coded instructions are further configured to cause the multi-app communication system to:

generate the multi-factor confirmation message, and

wherein the computer coded instructions configured to cause transmission of the multi-factor confirmation message comprises computer coded instructions configured to cause the multi-app communication system to:

transmit the multi-factor confirmation message to the verified third-party multi-factor authentication resource.

11. The multi-app communication system of claim 1 , wherein the computer coded instructions configured to cause transmission of the multi-factor confirmation message cause the multi-app communication system to:

transmit a multi-factor request to the third-party resource to cause transmission of the multi-factor confirmation message to the verified third-party multi-factor authentication resource.

12. The multi-app communication system of claim 1 , wherein the computer coded instructions are further configured to cause the multi-app communication system to:

generate an in-app auto-authentication prompt interface in response to launching the authenticated session;

cause a second client device to render the in-app auto-authentication prompt interface; and

receive an in-app auto-authentication approval in response to user engagement with the in-app auto-authentication prompt interface.

13. The multi-app communication system of claim 1 , wherein the computer coded instructions are further configured to cause the multi-app communication system to:

generate an in-app auto-authentication prompt interface in response to launching the authenticated session;

cause a second client device to render the in-app auto-authentication prompt interface; receive an in-app auto-authentication revocation in response to user engagement with the in-app auto-authentication prompt interface; and

terminate the authenticated session in response to the in-app auto-authentication revocation.

14. The multi-app communication system of claim 1 , wherein the multi-factor confirmation message comprises an email message, and wherein the verified third-party multi-factor authentication resource comprises a verified email resource.

15. The multi-app communication system of claim 1 , wherein the enabled access to the third-party resource is associated with a one-time session.

16. The multi-app communication system of claim 1 , wherein the computer coded instructions are further configured to cause the multi-app communication system to:

verify the client device is configured to access the verified third-party multi-factor authentication resource.

17. The multi-app communication system of claim 16 , wherein the computer coded instructions configured to cause the multi-app communication system to verify the client device is configured to access the verified third-party multi-factor authentication resource are configured to cause the multi-app communication system to:

identify a target instance identifier associated with the third-party sign-in request; identify a confirmation instance identifier associated with the multi-factor confirmation message; and

validate the confirmation instance identifier based on the target instance identifier.

18. The multi-app communication system of claim 1 , wherein the computer coded instructions are further configured to cause the multi-app communication system to:

parse the multi-factor confirmation message to identify an action notification; and

cause the client device, via the multi-app communication system application executed on the client device, to render a multi-app communication system interface associated with the action notification.

19. A computer-implemented method for providing authenticated access to a third-party resource via a multi-app communication system capable of communication with a verified third-party multi-factor authentication resource, wherein the multi-app communication system is capable of communication with a multi-app communication system application executed on a client device, the method comprising:

launching an authenticated session associated with an authenticated user account;

receiving a third-party sign-in request from a multi-app communication system application executed on the client device during the authenticated session associated with an authenticated user account;

causing transmission of a multi-factor confirmation message to the verified third-party multi-factor authentication resource;

querying the verified third-party multi-factor authentication resource to identify the multi-factor confirmation message;

automatically extracting a multi-factor message code from the multi-factor confirmation message for authentication without user engagement; and

enabling access to the third-party resource during the authenticated session associated with the authenticated user account.

20. A computer program product for providing authenticated access to a third-party resource via a multi-app communication system capable of communication with a verified third-party multi-factor authentication resource, wherein the multi-app communication system is capable of communication with a multi-app communication system application executed on a client device, the computer program product comprising at least one non-transitory computer-readable storage medium having computer-executable program code instructions stored therein, the computer-executable program code instructions comprising program code instructions for:

launching an authenticated session associated with an authenticated user account;

receiving a third-party sign-in request from a multi-app communication system application executed on the client device during the authenticated session associated with an authenticated user account;

causing transmission of a multi-factor confirmation message to the verified third-party multi-factor authentication resource;

querying the verified third-party multi-factor authentication resource to identify the multi-factor confirmation message;

automatically extracting a multi-factor message code from the multi-factor confirmation message for authentication without user engagement; and

enabling access to the third-party resource during the authenticated session associated with the authenticated user account.

Assignments (5)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Aug 18, 2023
From: SLACK TECHNOLOGIES, LLC
To: SALESFORCE, INC.
Reel/Frame 064642/0564 →
MERGER Recorded Jul 29, 2021
From: SLACK TECHNOLOGIES, INC.
To: SLACK TECHNOLOGIES, LLC
Reel/Frame 057475/0404 →
RELEASE OF SECURITY INTEREST IN PATENT COLLATERAL AT REEL/FRAME NO. 49332/0349 Recorded Jul 19, 2021
From: MORGAN STANLEY SENIOR FUNDING, INC.
To: SLACK TECHNOLOGIES, INC.
Reel/Frame 057649/0882 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 13, 2020
From: PIKE, MARK; SCHEMERS, ROLAND; MCPHAIL, JAMES; WAHL, MATTHEW
To: SLACK TECHNOLOGIES, INC.
Reel/Frame 054037/0866 →
PATENT SECURITY AGREEMENT Recorded May 30, 2019
From: SLACK TECHNOLOGIES, INC.
To: MORGAN STANLEY SENIOR FUNDING, INC., AS COLLATERAL AGENT
Reel/Frame 049332/0349 →