Systems and methods for integrating systems over untrusted networks

Patent metadata

Field	Value
Publication number	US-11240229-B2
Application number	US-202016836641-A
Country	US
Kind code	B2
Filing date	Mar 31, 2020
Priority date	Mar 31, 2020
Publication date	Feb 1, 2022
Grant date	Feb 1, 2022

Abstract

Described herein is a computer implemented method for configuring a receiving system to receive data from a sending system. The method comprises receiving an integration creation request from a client application. In response, a specific integration user account is created with credentials which provide access to the receiving system. The credentials are communicated to the client application. In addition, an integration record comprising details in respect of the integration is created, stored, and associated with the specific integration user account.

First claim

What is claimed is:

1. A computer implemented method comprising:
receiving, at a first backend system configured to provide server-side multitenant functionality for a first software platform, an integration management request from a client application configured to provide client-side functionality for the first software platform, the integration management request referencing at least one of a plurality of integrations, each of which is respectively associated with a respective one tenant for which the first backend system provides access to the first software platform;
determining an integration identifier for each integration of the plurality of integrations that is associated with a selected tenant of the first backend system, each integration being associated with a second backend system configured to provide server-side multitenant functionality for a second software platform and each providing a mechanism for the second backend system to communicate data to the first backend system; and
for each respective integration identifier:
retrieving a set of integration details comprising:
specific integration user account details that can be used by the respective second backend system to communicate data to the first backend system;
one or more data types, each identifying:
a particular type of data that the respective second backend system can communicate to the first backend system; and
one or more APIs of the first backend system that can be used by the respective second backend system to communicate the particular type of data to the first backend system; and

returning the retrieved set of integration details to the client application.

2. The computer implemented method according to claim 1 , wherein:
the integration management request is made via a first backend system user account; the first backend system user account is associated with the selected tenant; and
determining the integration identifier for each integration of the plurality of integrations comprises determining integration identifiers for all integrations that have been installed at the first backend system by all user accounts associated with the selected tenant.

3. The computer implemented method according to claim 2 , wherein determining integration identifiers comprises:
determining a tenant identifier of the selected tenant;
determining a general integrations user account associated with the tenant identifier; and determining integration identifiers of all integrations that have been installed at the first backend system and that are associated with the general integrations user account.

4. The computer implemented method according to claim 1 , wherein the specific integration user account is associated with the general integrations user account.

5. The computer implemented method according to claim 1 , wherein the specific integration user account details are retrieved from a user directory component of the first backend system.

6. The computer implemented method according to claim 5 , wherein determining the general integrations user account associated with the tenant identifier comprises querying a data store of the first backend system, the data store being separate to the user directory component.

7. The computer implemented method according to claim 1 , wherein for a particular integration identifier that identifies a particular integration that is associated with a particular second backend system, the set of integration details includes an identifier of the particular second backend system.

8. The computer implemented method according to claim 1 , wherein for a particular integration identifier that identifies a particular integration that is associated with a particular second backend system, the set of integration details includes a resource locator of an endpoint of the second backend system.

9. A computer processing system configured as a first backend system configured to provide multitenant server-side functionality of a first software platform, the system comprising:
a processing unit;
a communication interface; and
a non-transient computer-readable storage medium storing sequences of instructions, which when executed by the processing unit, cause the processing unit to:
receive, via the communication interface, an integration management request from a client application, the integration management request associated with at least one of a plurality of integrations associated with a selected tenant of the first backend system for which the first backend system provides access to the first software platform;
determine an integration identifier for each integration of the plurality of integrations associated with the selected tenant, each integration being associated with a second backend system configured to provide multitenant server-side functionality of a second software platform for which the selected tenant is also a tenant and each providing an integration-specific mechanism for the second backend system to communicate data owned by the selected tenant to the first backend system; and
for each respective integration identifier:
retrieving a set of integration details comprising:
specific integration user account details that can be used by the respective second backend system to communicate data to the first backend system;
one or more data types, each identifying:
a particular type of data that the respective second backend system can communicate to the first backend system; and
one or more APIs of the first backend system that can be used by the respective second backend system to communicate the particular type of data to the first backend system; and

returning the retrieved set of integration details to the client application.

10. The computer processing system according to claim 9 , wherein:
the integration management request is made via a first backend system user account;
the first backend system user account is associated with the selected tenant; and
determining the integration identifier for each integration of the plurality of integrations comprises determining integration identifiers for all integrations that have been installed at the first backend system by all user accounts associated with the selected tenant.

11. The computer processing system according to claim 10 , wherein determining integration identifiers comprises:
determining a tenant identifier of the selected tenant;
determining a general integrations user account associated with the tenant identifier; and
determining integration identifiers of all integrations that have been installed at the first backend system and that are associated with the general integrations user account.

12. The computer processing system according to claim 9 , wherein the specific integration user account is associated with the general integrations user account.

13. The computer processing system according to claim 9 wherein the specific integration user account details are retrieved from a user directory component of the first backend system.

14. The computer processing system according to claim 13 , wherein determining the general integrations user account associated with the tenant identifier comprises querying a data store of the first backend system, the data store being separate to the user directory component.

15. The computer processing system according to claim 9 , wherein for a particular integration identifier that identifies a particular integration that is associated with a particular second backend system, the set of integration details includes an identifier of the particular second backend system.

Assignees

• Atlassian Pty Ltd
• Atlassian Inc

Inventors

• Rolf Carl Christian
• Burn Oliver
• Navin James
• Myslek Rafal Krzysztof

Classifications

• H04L63/10

  for controlling access to devices or network resources · CPC title

• G06F9/547

  Remote procedure calls [RPC]; Web services · CPC title

• H04L63/20

  for managing network security; network security policies in general (filtering policies H04L63/0227) · CPC title

• H04L63/083 Primary

  using passwords (cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226) · CPC title