Method, apparatus, and computer program product for installing and updating third party applications requiring variable host address identification in a group-based communication system

Patent metadata

Field	Value
Publication number	US-12143394-B2
Application number	US-202217827331-A
Country	US
Kind code	B2
Filing date	May 27, 2022
Priority date	Jul 25, 2018
Publication date	Nov 12, 2024
Grant date	Nov 12, 2024

Abstract

Embodiments of the present disclosure provide methods, systems, apparatuses, and computer program products that enable client devices to install integrations of a third party application that supports variable host address identification.

First claim

The invention 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 for managing permissions for third-party applications in a group-based communication system, the method comprising:
receiving a defined scopes-and-features request for a third-party application, the defined scopes-and-features request indicating a requested set of permissions associated with a plurality of users of the group-based communication system for the third-party application, wherein the requested set of permissions specifies one or more actions of the third-party application associated with one or more group-based communication system objects associated with the group-based communication system, and wherein each user of a plurality of users is associated with one or more group identifiers;
generating an authentication token configured to enable the requested set of permissions for the third-party application, wherein the authentication token is associated with the defined scopes-and-features request for the third-party application and the one or more group identifiers;
transmitting the authentication token to a third-party application provider associated with the third-party application for validation of the requested set of permissions associated with the third-party application for the one or more group-based communication system objects, wherein the validation of the requested set of permissions comprises validation of the one or more group identifiers; and
storing, in a group-based communication system repository, information related to the requested set of permissions for the third-party application, wherein the information includes the one or more group identifiers.

2. The one or more non-transitory computer-readable media of claim 1 , wherein the one or more actions include at least one of:
viewing a history of the one or more group-based communication system objects, reading the one or more group-based communication system objects, or writing to the one or more group-based communication system objects.

3. The one or more non-transitory computer-readable media of claim 1 , wherein the one or more group-based communication system objects include at least one of: a file object, a search object, a chat object, a reaction object, a channel object, a do not disturb object, an instant message object, or an emoji object.

4. The one or more non-transitory computer-readable media of claim 1 , wherein the defined scopes-and-features request corresponds to a workspace within the group-based communication system and wherein the authentication token enables the requested set of permissions for group-based communication system objects only within the workspace.

5. The one or more non-transitory computer-readable media of claim 1 , wherein the defined scopes-and-features request corresponds to a channel within the group-based communication system and wherein the authentication token enables the requested set of permissions for group-based communication system objects only within the channel.

6. The one or more non-transitory computer-readable media of claim 1 , the method further comprising:
receiving a modification request to modify the defined scopes-and-features request for the third-party application;
in response to the modification request to modify the defined scopes-and-features request, generating an updated set of permissions for the third-party application; and
storing, in the group-based communication system repository, updated information related to the updated set of permissions for the third-party application.

7. The one or more non-transitory computer-readable media of claim 6 , the method further comprising:
generating an updated authentication token configured to enable the updated set of permissions for the third-party application; and
transmitting the updated authentication token to the third-party application provider associated with the third-party application.

8. A method for managing permissions for third-party applications in a group-based communication system comprising:
receiving a defined scopes-and-features request for a third-party application, the defined scopes-and-features request indicating a requested set of permissions associated with a plurality of users of the group-based communication system for the third-party application, wherein the requested set of permissions specifies one or more actions of the third-party application associated with one or more group-based communication system objects associated with the group-based communication system, and wherein each user of a plurality of users is associated with one or more group identifiers;
generating an authentication token configured to enable the requested set of permissions for the third-party application, wherein the authentication token is associated with the defined scopes-and-features request for the third-party application and the one or more group identifiers;
transmitting the authentication token to a third-party application provider associated with the third-party application for validation of the requested set of permissions associated with the third-party application for the one or more group-based communication system objects, wherein the validation of the requested set of permissions comprises validation of the one or more group identifiers; and
storing, in a group-based communication system repository, information related to the requested set of permissions for the third-party application, wherein the information includes the one or more group identifiers.

9. The method of claim 8 , wherein the one or more actions include at least one of:
viewing a history of the one or more group-based communication system objects, reading the one or more group-based communication system objects, or writing to the one or more group-based communication system objects.

10. The method of claim 8 , wherein the one or more group-based communication system objects include at least one of a file object, a search object, a chat object, a reaction object, a channel object, a do not disturb object, an instant message object, or an emoji object.

11. The method of claim 8 , wherein the defined scopes-and-features request corresponds to a workspace within the group-based communication system and wherein the authentication token enables the requested set of permissions for group-based communication system objects only within the workspace.

12. The method of claim 8 , wherein the defined scopes-and-features request corresponds to a channel within the group-based communication system and wherein the authentication token enables the requested set of permissions for group-based communication system objects only within the channel.

13. The method of claim 8 , further comprising:
receiving a modification request to modify the defined scopes-and-features request for the third-party application;
in response to the modification request to modify the defined scopes-and-features request, generating an updated set of permissions for the third-party application; and
storing, in the group-based communication system repository, updated information related to the updated set of permissions for the third-party application.

14. The method of claim 13 , further comprising:
generating an updated authentication token configured to enable the updated set of permissions for the third-party application; and
transmitting the updated authentication token to the third-party application provider associated with the third-party application.

15. A system comprising at least o

Assignees

• Salesforce Inc

Inventors

• Ranchod Sachin
• O'Neill Brian Stephen
• Shan Amy Dong
• Chen Steven

Classifications

• H04L63/104 Primary

  Grouping of entities · CPC title

• H04L65/403 Primary

  Arrangements for multi-party communication, e.g. for conferences (data switching systems for conference H04L12/18; arrangements for connecting several subscribers to a common circuit, i.e. affording conference facilities H04M3/56; television conferencing systems H04N7/15) · CPC title

• H04L67/53

  using third party service providers · CPC title

• H04L67/01

  Protocols · 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