IP Library Granted Patent US 11,184,345
Granted Patent B2
US 11,184,345 · App. 16/369,492 · Granted Nov 23, 2021

Workflow service back end integration

Inventors: Daniel E. Zeck (Roswell, GA); David Shaw (Buford, GA); Robert Worsnop (Dunwoody, GA); John Ryan Bard (Smyrna, GA)
Assignee: VMWARE, INC.
H04L63/0815G06F3/0482G06F3/04817H04L63/166H04L67/16H04L67/34
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 11,184,345
App. No.
16/369,492
Granted
Nov 23, 2021
Kind
B2
Abstract

Disclosed are various approaches for workflow service back end integration. In some examples, a service request is identified. The service request is associated with a network service. A single sign-on (SSO) token is received. The SSO token represents a user account authenticated with an identity manager. Authentication data for the network service is identified based on the SSO token. A hosting location of a connector for the network service is identified based on the authentication data. An authentication header is appended to the service request. The service request with the authentication header is transmitted to the connector.

Claims (64)

1. A system, comprising:

a computing device comprising at least one processor and at least one memory; and

machine-readable instructions stored in the at least one memory that, when executed by the at least one processor, cause the computing device to at least:

receive, by a workflow service from a client device, a service request associated with a network service;

receive, by the workflow service, a single sign-on (SSO) token, the SSO token representing a user account authenticated with an identity manager;

identify, by the workflow service, authentication data for the network service based on the SSO token;

determine, by the workflow service, based on the authentication data, a connector type corresponding to a hosting location of a connector for the network service;

append, by the workflow service, an authentication header to the service request, wherein the workflow service appends the authentication header to include authentication information selected based on the connector type indicating local hosting or external hosting of the connector with respect to the workflow service, the authentication information comprising:

a service credential that the connector uses for authentication with the network service in an instance in which the connector type indicates local hosting of the connector with respect to the workflow service, or

instructions for the connector to retrieve the service credential from a server external to a local computing environment of the computing device in an instance in which the connector type indicates external hosting of the connector with respect to the workflow service; and

transmit, by the workflow service to the connector, the service request comprising the authentication header.

2. The system of claim 1 , wherein the instructions, when executed by the at least one processor, cause the computing device to at least:

determine that the hosting location of the connector is an external hosting location based on the hosting location being external to a local computing environment of the computing device; and

include, in the authentication header, the instructions for the connector to retrieve the service credential from the server external to the local computing environment.

3. The system of claim 2 , wherein the instructions for the connector to retrieve the service credential comprise a network address for the server.

4. The system of claim 1 , wherein the instructions, when executed by the at least one processor, cause the computing device to at least:

determine that the hosting location of the connector is a local hosting location based on the hosting location being within a local computing environment of the computing device; and

include the service credential in the authentication header.

5. The system of claim 1 , wherein the hosting location of the connector is determined based on a network address of the connector.

6. The system of claim 1 , wherein the instructions, when executed by the at least one processor, cause the computing device to at least:

retrieve, based on the service request, data from the network service, wherein an authentication with the network service is completed based on the service credential.

7. The system of claim 6 , wherein the instructions, when executed by the at least one processor, cause the computing device to at least:

provide, to the client device, the data retrieved from the network service.

8. A non-transitory computer-readable medium comprising machine-readable instructions, wherein the instructions, when executed by at least one processor, cause a computing device to at least:

receive, by a workflow service from a client device, a service request associated with a network service;

receive, by the workflow service, a single sign-on (SSO) token, the SSO token representing a user account authenticated with an identity manager;

identify, by the workflow service, authentication data for the network service based on the SSO token;

determine, by the workflow service, based on the authentication data, a connector type corresponding to a hosting location of a connector for the network service;

append, by the workflow service, an authentication header to the service request, wherein the workflow service appends the authentication header to include authentication information selected based on the connector type indicating local hosting or external hosting of the connector with respect to the workflow service, the authentication information comprising:

a service credential that the connector uses for authentication with the network service in an instance in which the connector type indicates local hosting of the connector with respect to the workflow service, or

instructions for the connector to retrieve the service credential from a server external to a local computing environment of the computing device in an instance in which the connector type indicates external hosting of the connector with respect to the workflow service; and

transmit, by the workflow service to the connector, the service request comprising the authentication header.

9. The non-transitory computer-readable medium of claim 8 , wherein the instructions, when executed by the at least one processor, cause the computing device to at least:

determine that the hosting location of the connector is an external hosting location based on the hosting location being external to a local computing environment of the computing device; and

include, in the authentication header, the instructions for the connector to retrieve the service credential from the server external to the local computing environment.

10. The non-transitory computer-readable medium of claim 9 , wherein the instructions for the connector to retrieve the service credential comprise a network address for the server.

11. The non-transitory computer-readable medium of claim 8 , wherein the instructions, when executed by the at least one processor, cause the computing device to at least:

determine that the hosting location of the connector is a local hosting location based on the hosting location being within a local computing environment of the computing device; and

include the service credential in the authentication header.

12. The non-transitory computer-readable medium of claim 8 , wherein the hosting location of the connector is determined based on a network address of the connector.

13. The non-transitory computer-readable medium of claim 8 , wherein the instructions, when executed by the at least one processor, cause the computing device to at least:

retrieve, based on the service request, data from the network service, wherein an authentication with the network service is completed based on the service credential.

14. The non-transitory computer-readable medium of claim 13 , wherein the instructions, when executed by the at least one processor, cause the computing device to at least:

provide, to the client device, the data retrieved from the network service.

15. A method, comprising:

receiving, by a workflow service from a client device, a service request associated with a network service;

receiving, by the workflow service, a single sign-on (SSO) token, the SSO token representing a user account authenticated with an identity manager;

identifying, by the workflow service, authentication data for the network service based on the SSO token;

determining, by the workflow service, based on the authentication data, a connector type corresponding to a hosting location of a connector for the network service;

appending, by the workflow service, an authentication header to the service request, wherein the workflow service appends the authentication header to include authentication information selected based on the connector type indicating local hosting or external hosting of the connector with respect to the workflow service, the authentication information comprising:

a service credential that the connector uses for authentication with the network service in an instance in which the connector type indicates local hosting of the connector with respect to the workflow service, or

instructions for the connector to retrieve the service credential from a server external to a local computing environment of the computing device in an instance in which the connector type indicates external hosting of the connector with respect to the workflow service; and

transmitting, by the workflow service to the connector, the service request comprising the authentication header.

16. The method of claim 15 , further comprising:

determining that the hosting location of the connector is an external hosting location based on the hosting location being external to a local computing environment of the computing device; and

including, in the authentication header, the instructions for the connector to retrieve the service credential from the server external to the local computing environment.

17. The method of claim 15 , further comprising:

determining that the hosting location of the connector is a local hosting location based on the connector hosting location being within a local computing environment of the computing device; and

including the service credential in the authentication header.

18. The method of claim 15 , wherein the hosting location of the connector is determined based on a network address of the connector.

19. The method of claim 15 , further comprising:

retrieving, based on the service request, data from the network service, wherein an authentication with the network service is completed based on the service credential.

20. The method of claim 19 , further comprising:

providing, to the client device, the data retrieved from the network service.

Assignments (4)
PATENT ASSIGNMENT Recorded Aug 5, 2024
From: VMWARE LLC
To: OMNISSA, LLC
Reel/Frame 068327/0365 →
SECURITY INTEREST Recorded Jul 3, 2024
From: OMNISSA, LLC
To: UBS AG, STAMFORD BRANCH
Reel/Frame 068118/0004 →
CHANGE OF NAME Recorded Apr 15, 2024
From: VMWARE, INC.
To: VMWARE LLC
Reel/Frame 067102/0314 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 9, 2019
From: ZECK, DANIEL E.; SHAW, DAVID; WORSNOP, ROBERT; BARD, JOHN RYAN
To: VMWARE, INC.
Reel/Frame 048827/0567 →
Continuity (1)
Related Publication 20200314086A1 · Oct 1, 2020