# US 2024/0154945 A1 · System and method for third party service integration into a browser client application

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2024/0154945 A1
- Document ID: US20240154945A1
- Status: Published application
- Kind: A1
- Application number: 18/072,364
- Filed: 2022-11-30
- Published: 2024-05-09
- Earliest claimed: 2022-11-04
- Assignees: OpenMethods, Inc.
- Applicants: OpenMethods
- Inventors: Shannon Lekas; Gerrit Voorhis Lydecker, JR.; Carlos Gustavo Colombo; Ankur Kanti Patel
- Web page: https://patentgrep.com/patent/US20240154945A1

## CPC

- H04L 63/0807: {using tickets, e.g. Kerberos (cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213)}
- H04L 63/0815: {providing single-sign-on or federations}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A system and method for third party application integration into browser client application, utilizing an authentication engine operating on a cloud device that presents an application integration service token for integration through the operating system and software applications on the client device, wherein interacting with the application integration service token allows a workflow engine to produce third party data objects to be used to execute customer relationship management client workflows incorporating client application, context, and trust information.

## Claims

### Claim 1

A system for third-party application integration into a browser client application, comprising:
an authentication engine comprising at least a plurality of programming instructions stored in a memory of, and operating on at least one processor of, a computing device, wherein the plurality of programming instructions, when operating on the at least one processor, causes the computing device to:
receive user login information, the user login information comprising one or more of a session ID, a device ID, and client ID;
create a client session token, wherein the client session token is based on the user login information;
send the client session token to a workflow manager;
receive a wrapper token from the workflow manager, the wrapper token comprising a third-party service request and the client session token;
parse the wrapper token to extract the client session token;
validate a user associated with the client session token by comparing client session token data with user data stored in a database;
send the third-party service request to the appropriate third-party service;
receive, from the third-party service, one or more third-party data objects; and
send the one or more third-party data objects to the workflow engine; and
the workflow engine comprising at least a second plurality of programming instructions stored in a memory of, and operating on at least one processor of, a second computing device, wherein the second plurality of programming instructions, when operating on the at least one processor, causes the second computing device to:
receive the client session token from the authentication engine;
receive the third-party service request, the third-party service request comprising service request information;
create the wrapper token by combining the third-party service request information with the client session token;
send the wrapper token to the authentication engine;
receive the one or more third-party data objects; and
display the one or more third-party data objects in a browser-based application user interface.

### Claim 2 (depends on 1)

The system of claim 1, wherein the browser-based application is customer relationship management system.

### Claim 3

A method for third-party application integration into a browser client application, comprising the steps of:
receiving user login information, the user login information comprising one or more of a session ID, a device ID, and client ID;
creating a client session token, wherein the client session token is based on the user login information;
sending the client session token to a workflow manager;
receiving a wrapper token from the workflow manager, the wrapper token comprising a third-party service request and the client session token;
parsing the wrapper token to extract the client session token;
validating a user associated with the client session token by comparing client session token data with user data stored in a database;
sending the third-party service request to the appropriate third-party service;
receiving, from the third-party service, one or more third-party data objects;
sending the one or more third-party data objects to the workflow engine;
receiving the client session token from the authentication engine;
receiving the third-party service request, the third-party service request comprising service request information;
creating the wrapper token by combining the third-party service request information with the client session token;
sending the wrapper token to the authentication engine;
receiving the one or more third-party data objects; and
displaying the one or more third-party data objects in a browser-based application user interface.

### Claim 4 (depends on 3)

The method of claim 3, wherein the browser-based application is customer relationship management system.
