Securely communicating data between an application associated with an entity and a third-party system
AssigneeAtomic FI, Inc.
InventorsScott Nielsen Weinert, Jr., Sean Michael Hill, Michael Contreras
Life of this patent
Estimating the term…
Abstract
A webview associated with a third-party system is provided in an application context associated with an entity. It is determined that a user has been authenticated by the third-party system based on data comprising a page displayed via the provided webview. In response to a determination that the user has been authenticated by the third-party system, one or more tasks to perform a function with the third-party system on behalf of the entity are automated.
Claims16
A system, comprising:
- a communication interface;
- and
- a processor, coupled to the communication interface, configured to:
- provide in an application context corresponding to an entity associated with a user, a webview associated with a third-party system selected from a plurality of third-party systems, wherein the webview associated with the selected third-party system displays a native login page corresponding to the selected third-party system, wherein providing the native login page corresponding to the selected third-party system via the webview associated with the third-party system removes the need to provide the user's login credentials to an intermediary service with which the application context is associated, wherein the user's login credentials are directly provided from an application associated with the application context, via the webview associated with the selected third-party system, to the selected third-party system;
- determine that the user has been authenticated by the selected third-party system using data comprising a page displayed via the provided webview associated with the selected third-party system that is received via the communication interface at least in part by analyzing a response page displayed via the provided webview associated with the selected third-party system and determining that the response page includes one or more visual page elements indicative of the user being authenticated, wherein the response page is the page displayed via the provided webview associated with the selected third-party system;
- and
- in response to the determination that the response page includes the one or more visual page elements indicative of the user being authenticated, automate one or more tasks needed to perform a function, requested by the user, with the selected third-party system on behalf of the entity.
A method, comprising:
- providing in an application context corresponding to an entity associated with a user, a webview associated with a third-party system selected from a plurality of third-party systems, wherein the webview associated with the selected third-party system displays a native login page corresponding to the selected third-party system, wherein providing the native login page corresponding to the selected third-party system via the webview associated with the selected third-party system removes the need to provide the user's login credentials to an intermediary service with which the application context is associated, wherein the user's login credentials are directly provided from an application associated with the application context, via the webview associated with the selected third-party system, to the selected third-party system;
- determining that a user has been authenticated by the selected third-party system using data comprising a page displayed via the provided webview associated with the selected third-party system at least in part by analyzing a response page displayed via the provided webview associated with the selected third-party system and determining that the response page includes one or more visual page elements indicative of the user being authenticated, wherein the response page is the page displayed via the provided webview associated with the selected third-party system;
- and
- in response to a determination that the response page includes the one or more visual page elements indicative of the user being authenticated, automating one or more tasks needed to perform a function, requested by the user, with the selected third-party system on behalf of the entity.
A computer program product embodied in a non-transitory computer readable medium and comprising computer instructions for:
- providing in an application context corresponding to an entity associated with a user, a webview associated with a third-party system selected from a plurality of third-party systems, wherein the webview associated with the selected third-party system displays a native login page corresponding to the selected third-party system, wherein providing the native login page corresponding to the selected third-party system via the webview associated with the selected third-party system removes the need to provide the user's login credentials to an intermediary service with which the application context is associated, wherein the user's login credentials are directly provided from an application associated with the application context, via the webview associated with the selected third-party system, to the selected third-party system;
- determining that the user has been authenticated by the selected third-party system using data comprising a page displayed via the provided webview associated with the selected third-party system at least in part by analyzing a response page displayed via the provided webview associated with the selected third-party system and determining that the response page includes one or more visual page elements indicative of the user being authenticated, wherein the response page is the page displayed via the provided webview associated with the selected third-party system;
- and
- in response to a determination that the response page includes the one or more visual page elements indicative of the user being authenticated, automating one or more tasks needed to perform a function, requested by the user, with the selected third-party system on behalf of the entity.
Dependencies are inferred from the claim text.