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

Patent metadata

Field	Value
Publication number	US-12184651-B2
Application number	US-202217949806-A
Country	US
Kind code	B2
Filing date	Sep 21, 2022
Priority date	Jan 31, 2019
Publication date	Dec 31, 2024
Grant date	Dec 31, 2024

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.

First claim

What is claimed is:

1. One or more non-transitory computer-readable media storing computer-executable instructions that, when executed by at least one processor, perform a method of verifying a third-party resource by a multi-app communication system, the method comprising:
launching a multi-app communication system application on a client device, wherein the multi-app communication system application is configured to provide a user associated with an authenticated user account with authenticated engagement with one or more third-party resources including the third-party resource;
generating a sign-in prompt and causing for display the sign-in prompt by the multi-app communication system application;
receiving a multi-app sign-in request from the multi-app communication system application;
causing transmission of a multi-factor confirmation message to the third-party resource via a third-party multi-factor authentication resource associated with the third-party resource based on the multi-app sign-in request, wherein the third-party multi-factor authentication resource is configured to generate the multi-factor confirmation message;
querying the third-party resource to identify the multi-factor confirmation message;
receiving the multi-factor confirmation message including a multi-factor message code;
extracting the multi-factor message code from the multi-factor confirmation message; and
enabling access to the third-party resource by the user via the multi-app communication system application based on the multi-factor message code.

2. The media of claim 1 , wherein the method further comprises:
launching an authenticated session associated with an authenticated user account, wherein the multi-app sign-in request is received during the authenticated session, and
wherein the access to the third-party resource is enabled during the authenticated session.

3. The media of claim 2 , wherein the third-party resource is a verified email resource and wherein the method further comprises utilizing a webhook to receive an automatic email verification when the verified email resource is associated with the authenticated user account.

4. The media of claim 2 , wherein the method further comprises:
receiving 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
storing the verified resource information associated with the authenticated user account.

5. The media of claim 1 , wherein the method further comprises:
transmitting a third-party multi-factor authentication resource access request;
causing the client device, via the multi-app communication system application, to render a third-party multi-factor authentication resource access prompt interface; and
receiving third-party multi-factor authentication resource access approval in response to user engagement with the third-party multi-factor authentication resource access prompt interface.

6. The media of claim 1 , wherein the method further comprises:
launching an authenticated session;
generating an in-app auto-authentication prompt interface in response to launching the authenticated session;
causing a second client device to render the in-app auto-authentication prompt interface; and
receiving an in-app auto-authentication approval in response to user engagement with the in-app auto-authentication prompt interface.

7. The media of claim 1 , wherein the method further comprises:
parsing the multi-factor confirmation message to identify an action notification; and
causing 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.

8. A method of verifying a third-party resource by a multi-app communication system, the method comprising:
launching a multi-app communication system application on a client device, wherein the multi-app communication system application is configured to provide a user associated with an authenticated user account with authenticated engagement with one or more third-party resources including the third-party resource;
generating a sign-in prompt and causing for display the sign-in prompt by the multi-app communication system application;
receiving a multi-app sign-in request from the multi-app communication system application;
causing transmission of a multi-factor confirmation message to the third-party resource via a third-party multi-factor authentication resource associated with the third-party resource based on the multi-app sign-in request, wherein the third-party multi-factor authentication resource is configured to generate the multi-factor confirmation message;
querying the third-party resource to identify the multi-factor confirmation message;
receiving the multi-factor confirmation message including a multi-factor message code;
extracting the multi-factor message code from the multi-factor confirmation message; and
enabling access to the third-party resource based on the multi-factor message code.

9. The method of claim 8 , further comprising:
launching an authenticated session associated with an authenticated user account, wherein the multi-app sign-in request is received during the authenticated session, and
wherein the access to the third-party resource is enabled during the authenticated session.

10. The method of claim 9 , wherein the third-party resource is a verified email resource; and
further comprising utilizing a webhook to receive an automatic email verification when the verified email resource is associated with the authenticated user account.

11. The method of claim 9 , further comprising:
receiving 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
storing the verified resource information associated with the authenticated user account.

12. The method of claim 8 , further comprising:
transmitting a third-party multi-factor authentication resource access request;
causing the client device, via the multi-app communication system application, to render a third-party multi-factor authentication resource access prompt interface; and
receiving third-party multi-factor authentication resource access approval in response to user engagement with the third-party multi-factor authentication resource access prompt interface.

13. The method of claim 8 , further comprising:
launching an authenticated session;
generating an in-app auto-authentication prompt interface in response to launching the authenticated session;
causing a second client device to render the in-app auto-authentication prompt interface; and
receiving an in-app auto-authentication approval in response to user engagement with the in-app auto-authentication prompt interface.

14. The method of claim 8 , further comprising:
parsing the multi-factor confirmation message to identify an action notification; and
causing 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.

15. A multi-app communication system for verifying a third-party resource, comprising:
at least one processor;
at least one data store associated with the at least one processor; and
one or more non-transitory computer-readable media storing computer-executable instructions that, when executed by the at least one processor

Assignees

• Salesforce Inc

Inventors

• Pike Mark
• Schemers Roland
• Mcphail James
• Wahl Matthew

Classifications

• H04L63/102

  Entity profiles · CPC title

• H04L63/0853

  using an additional device, e.g. smartcard, SIM or a different communication terminal (cryptographic mechanisms or cryptographic arrangements for entity authentication involving additional secure or trusted devices H04L9/3234) · CPC title

• H04L63/0884 Primary

  by delegation of authentication, e.g. a proxy authenticates an entity to be authenticated on behalf of this entity vis-à-vis an authentication entity · CPC title

• G06F21/42 Primary

  using separate channels for security data · CPC title