# US 2021/0067504 A1 · Authentication of plugins in a virtualized computing environment

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

- Number: US 2021/0067504 A1
- Document ID: US20210067504A1
- Status: Published application
- Kind: A1
- Application number: 16/554,565
- Filed: 2019-08-28
- Published: 2021-03-04
- Earliest claimed: 2019-08-28
- Assignees: VMware, Inc.
- Applicants: VMware, Inc.
- Inventors: Tony GANCHEV; Tihomir MATEEV
- Web page: https://patentgrep.com/patent/US20210067504A1

## CPC

- H04L 63/0807: {using tickets, e.g. Kerberos (cryptographic mechanisms or cryptographic arrangements for entity authentication using tickets or tokens H04L9/3213)}
- G06F 21/44: Program or device authentication
- G06F 9/44526: {Plug-ins; Add-ons}
- G06F 9/45541: {Bare-metal, i.e. hypervisor runs directly on hardware}
- G06F 9/45545: {Guest-host, i.e. hypervisor is an application program itself, e.g. VirtualBox}
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Plugins are authenticated for purposes of accessing and using application program interfaces (APIs) of a management service of a virtualized computing environment. In an authentication process, each plugin is associated with a session ticket that is unique to the plugin. The session ticket may be in the form of a single-use token that has a finite duration, and which may be used by the plugin to establish a session with the APIs of the management service. Because of the single-use and finite duration constraints of the token, the plugin is unable to use the token for other sessions and other plugins are also unable to use the same token to conduct their own sessions with the management service.

## Claims

### Claim 1

A method to authenticate a plugin to enable the plugin to interact with a management service in a virtualized computing environment, the method comprising:
obtaining a session identification (ID) that is uniquely associated with the plugin;
using, by a plugin server, the session ID to request a session ticket from a management server, for the virtualized computing environment, that provides the management service;
obtaining, by the plugin server from the management server, the requested session ticket, wherein the session ticket is uniquely associated with the plugin and has a finite duration; and
using, by the plugin server, the session ticket to establish a session between the plugin and the management service, wherein the session is conducted within the finite duration of the session ticket.

### Claim 2 (depends on 1)

The method of claim 1, wherein the session includes interactions between the plugin and one or more application program interfaces (APIs) of the management service.

### Claim 3 (depends on 1)

The method of claim 1, wherein obtaining the session ID includes obtaining, by the plugin server, the session ID from a user device that received the session ID from the management server.

### Claim 4 (depends on 1)

The method of claim 1, wherein the finite duration of the session ticket is configured based on one or more of: a time-based duration, a number of application program interface (API) calls permitted to be made by the plugin during the session, or a duration of the session.

### Claim 5 (depends on 1)

The method of claim 1, further comprising obtaining, by the plugin in server, an identification of the management server in addition to the session ID, so as to enable the plugin server to determine which instance of the management server is in communication with the plugin.

### Claim 6 (depends on 1)

The method of claim 1, further comprising obtaining, by the plugin server, multiple session IDs and multiple session tickets that are uniquely associated with respective multiple plugins that reside at the plugin server.

### Claim 7 (depends on 1)

The method of claim 1, wherein either or both of the session ID and the session ticket comprise tokens.

### Claim 8

A non-transitory computer-readable medium having instructions stored thereon, which in response to execution by one or more processors, cause the one or more processors to perform or control performance of operations to authenticate a plugin to enable the plugin to interact with a management service in a virtualized computing environment, the operations comprising:
obtaining a session identification (ID) that is uniquely associated with the plugin;
using, by a plugin server, the session ID to request a session ticket from a management server, for the virtualized computing environment, that provides the management service;
obtaining, by the plugin server from the management server, the requested session ticket, wherein the session ticket is uniquely associated with the plugin and has a finite duration; and
using, by the plugin server, the session ticket to establish a session between the plugin and the management service, wherein the session is conducted within the finite duration of the session ticket.

### Claim 9 (depends on 8)

The non-transitory computer-readable medium of claim 8, wherein the session includes interactions between the plugin and one or more application program interfaces (APIs) of the management service.

### Claim 10 (depends on 8)

The non-transitory computer-readable medium of claim 8, wherein obtaining the session ID includes obtaining, by the plugin server, the session ID from a user device that received the session ID from the management server.

### Claim 11 (depends on 8)

The non-transitory computer-readable medium of claim 8, wherein the finite duration of the session ticket is configured based on one or more of: a time-based duration, a number of application program interface (API) calls permitted to be made by the plugin during the session, or a duration of the session.

### Claim 12 (depends on 8)

The non-transitory computer-readable medium of claim 8, wherein the operations further comprise:
obtaining, by the plugin in server, an identification of the management server in addition to the session ID, so as to enable the plugin server to determine which instance of the management server is in communication with the plugin.

### Claim 13 (depends on 8)

The non-transitory computer-readable medium of claim 8, wherein the operations further comprise:
obtaining, by the plugin server, multiple session IDs and multiple session tickets that are uniquely associated with respective multiple plugins that reside at the plugin server.

### Claim 14 (depends on 8)

The non-transitory computer-readable medium of claim 8, wherein either or both of the session ID and the session ticket comprise tokens.

### Claim 15

A system, comprising:
a plugin server, having a plugin resident thereon, usable to authenticate the plugin to enable the plugin to interact with a management service in a virtualized computing environment, wherein the plugin server is configured to:
obtain a session identification (ID) that is uniquely associated with the plugin;
use the session ID to request a session ticket from a management server, for the virtualized computing environment, that provides the management service;
obtain, from the management server, the requested session ticket, wherein the session ticket is uniquely associated with the plugin and has a finite duration; and
use the session ticket to establish a session between the plugin and the management service, wherein the session is conducted within the finite duration of the session ticket.

### Claim 16 (depends on 15)

The system of claim 15, wherein the session includes interactions between the plugin and one or more application program interfaces (APIs) of the management service.

### Claim 17 (depends on 15)

The system of claim 15, wherein the plugin server is configured to obtain the session ID from a user device that received the session ID from the management server.

### Claim 18 (depends on 15)

The system of claim 15, wherein the finite duration of the session ticket is configured based on one or more of: a time-based duration, a number of application program interface (API) calls permitted to be made by the plugin during the session, or a duration of the session.

### Claim 19 (depends on 15)

The system of claim 15, wherein the plugin server is further configured to obtain an identification of the management server in addition to the session ID, so as to enable the plugin server to determine which instance of the management server is in communication with the plugin.

### Claim 20 (depends on 15)

The system of claim 15, wherein the plugin server is further configured to obtain multiple session IDs and multiple session tickets that are uniquely associated with respective multiple plugins that reside at the plugin server.

### Claim 21 (depends on 15)

The system of claim 15, wherein either or both of the session ID and the session ticket comprise tokens.
