# US 10,482,235 B2 · Systems and methods for integrating with a native component using a network interface

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

- Number: US 10,482,235 B2
- Document ID: US10482235B2
- Status: Granted
- Kind: B2
- Application number: 16/020,033
- Filed: 2018-06-27
- Published: 2018-11-15
- Granted: 2019-11-19
- Earliest claimed: 2015-01-21
- Assignees: Open Text SA ULC
- Applicants: Open Text SA ULC
- Inventors: Jonathan Carroll; Michel Gagnon; Gregory Pekofsky; Khanh Tuan Vu
- Web page: https://patentgrep.com/patent/US10482235B2

## CPC

- G06F 21/44: Program or device authentication
- H04L 63/0823: {using certificates (cryptographic mechanisms or cryptographic arrangements for entity authentication involving certificates H04L9/3263)}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Embodiments as disclosed herein may provide systems and methods for component integration and security. In particular, in one embodiment, a native component that presents a network based interface may be on a device, where that native component may expose a network based interface for access by other components. This native component can then be accessed through the network based interface. To address security concerns and other issues, the native component may be configured to determine if a received request is associated with the same user space and only respond to requests originating from the same user space.

## Claims

### Claim 1

A system, comprising:
a processor device;
a native component presenting a network accessible interface allowing functionality of the native component to be accessed through the network accessible interface, wherein the native component comprises instructions executable on the processor device to:
receive a request issued from a requesting component executing on the system, wherein the request is received through the network accessible interface of the native component;
determine a first identifier associated with a first user space of the system in which the native component is executing, the first identifier associated with the execution of the native component on the system and a first session;
determine a second identifier associated with a second user space of the system in which the requesting component is executing by:
determining a process identifier associated with the execution of the requesting component on the system based on a port of a connection associated with the request, and
determining the second identifier associated with the process identifier, the execution of the requesting component on the system and a second session; and
determine if the first user space of the native component and the second user space of the requesting component are associated with a same user by comparing the first identifier to the second identifier; and
if the first user space of the native component and the second user space of the requesting component are associated with a same user, allowing the request, and if the if the first user space of the native component and the second user space of the requesting component are not associated with the same user denying the request.

### Claim 2 (depends on 1)

The system of claim 1, wherein the network accessible interface is a Transmission Control Protocol (TCP) or User Datagram Protocol (UDP) based interface.

### Claim 3 (depends on 1)

The system of claim 1, wherein determining the first identifier comprises determining a first session identifier associated with the native component.

### Claim 4 (depends on 3)

The system of claim 3, wherein determining the second identifier comprises:
determining the port of the connection associated with the request;
determining the process identifier associated with the requesting component is based on the port of the connection associated with the request; and
determining a second session identifier associated with process identifier.

### Claim 5 (depends on 4)

The system of claim 4, wherein determining the process identifier associated with the requesting component comprises:
accessing a TCP table; and
determining the process identifier associated with the port of the request in the TCP table.

### Claim 6 (depends on 5)

The system of claim 5, wherein the port is a remote port associated with the request and the port of the request in the TCP table is a local port.

### Claim 7 (depends on 6)

The system of claim 6, wherein the request utilizes Secure Sockets Layer (SSL) and the connection is established with the requesting component using a certificate associated with the requesting component.

### Claim 8 (depends on 7)

The system of claim 7, wherein the certificate is associated with a user associated with the second user space and is stored in a registry of the user on the system.

### Claim 9 (depends on 1)

The system of claim 1, wherein the requesting component, is executing in a browser.

### Claim 10 (depends on 9)

The system of claim 9, wherein the second identifier is an owning process identifier.

### Claim 11

A method, comprising:
receiving, at a network accessible interface of a native component on a system, a request from a requesting component executing on the system;
determine, at the native component, a first identifier associated with a first user space of the system in which the native component is executing, the first identifier associated with the execution of the native component on the system and a first session;
determine, at the native component, a second identifier associated with a second user space of the system in which the requesting component is executing by:
determining a process identifier associated with the execution of the requesting component on the system based on a port of a connection associated with the request, and
determining the second identifier associated with the process identifier; the execution of the requesting component on the system and a second session; and
determine, at the native component, if the first user space of the native component and the second user space of the requesting component are associated with a same user by comparing the first identifier to the second identifier; and
if the first user space of the native component and the second user space of the requesting component are associated with a same user, allowing the request, and if the if the first user space of the native component and the second user space of the requesting component are not associated with the same user denying the request.

### Claim 12 (depends on 11)

The method of claim 11, wherein the network accessible interface is a Transmission Control Protocol (TCP) or User Datagram Protocol (UDP) based interface.

### Claim 13 (depends on 11)

The method of claim 11, wherein determining the first identifier comprises determining a first session identifier associated with the native component.

### Claim 14 (depends on 13)

The method of claim 13, wherein determining the second identifier comprises:
determining the port of the connection associated with the request;
determining the process identifier associated with the requesting component is based on the port of the connection associated with the request; and
determining a second session identifier associated with process identifier.

### Claim 15 (depends on 14)

The method of claim 14, wherein determining the process identifier associated with the requesting component comprises:
accessing a TCP table; and
determining the process identifier associated with the port of the request in the TCP table.

### Claim 16 (depends on 15)

The method of claim 15, wherein the port is a remote port associated with the request and the port of the request in the TCP table is a local port.

### Claim 17 (depends on 16)

The method of claim 16, wherein the request utilizes Secure Sockets Layer (SSL) and the connection is established with the requesting component using the certificate associated with the requesting component.

### Claim 18 (depends on 17)

The method of claim 17, wherein the certificate is associated with a user associated with the second user space and is stored in a registry of the user on the system.

### Claim 19 (depends on 11)

The method of claim 11, wherein the requesting component is executing in a browser.

### Claim 20 (depends on 19)

The method of claim 19, wherein the second identifier is an owning process identifier.