# US 2025/0097231 A1 · File server managers including api-level permissions examination

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

- Number: US 2025/0097231 A1
- Document ID: US20250097231A1
- Status: Published application
- Kind: A1
- Application number: 18/468,558
- Filed: 2023-09-15
- Published: 2025-03-20
- Earliest claimed: 2023-09-15
- Applicants: Nutanix, Inc.
- Inventors: David Lai; Mausumi Ranasingh; Kalpesh Ashok Bafna
- Web page: https://patentgrep.com/patent/US20250097231A1

## CPC

- H04L 63/102: {Entity profiles}
- H04L 63/105: {Multiple levels of security}
- H04L 67/06: specially adapted for file transfer, e.g. file transfer protocol [FTP]
- H04L 67/561: Adding application-functional data or data for application control, e.g. adding metadata
- H04L 67/63: Routing a service request depending on the request content or context
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Examples of file server managers are described herein. A file server manager may be in communication with one or more virtualized file servers and may be used to provide a single pane of glass management interface to the virtualized file servers. File server managers described herein may include gateways and may examine API-level permissions for received API calls. File server managers may route API calls to target virtualized file servers. Role-based access permissions implemented by file server managers are also described.

## Claims

### Claim 1

A method comprising:
receiving, at a gateway of a management system configured to manage multiple file servers, an API call including an identified target file server;
preparing a request for an API permissions repository based on the identified target file server and a user;
receiving an API permission based on the user and the identified target file server from the permissions repository; and
allowing or declining the API call by the user in accordance with the API permission.

### Claim 2 (depends on 1)

The method of claim 1, wherein said allowing or declining the API call comprises allowing the API call, and wherein the API call is for an action at the target file server.

### Claim 3 (depends on 2)

The method of claim 2, further comprising routing the API call to the target file server based on an identification of the target file server.

### Claim 4 (depends on 3)

The method of claim 3, wherein the identification comprises a URI or URL received with the API call.

### Claim 5 (depends on 1)

The method of claim 1, further comprising storing associations between respective identifications of each of the multiple file servers and operation types expected at each of the multiple file servers.

### Claim 6 (depends on 1)

The method of claim 1, further comprising providing a user interface for updating permissions in the API permissions repository.

### Claim 7 (depends on 6)

The method of claim 6, further comprising:
receiving, through the user interface, a request to provide a first permission to a particular user; and
prompting, through the user interface, for authorization to provide a second permission to the particular user, wherein the first permission utilizes the second permission.

### Claim 8 (depends on 7)

The method of claim 7, wherein the second permission comprises a network permission.

### Claim 9 (depends on 1)

The method of claim 1, wherein the API permission comprises a role-based permission, and wherein the API permissions repository includes an association between the user and a role.

### Claim 10

A system comprising:
a file server manager configured to manage multiple file servers, including a target file server, the file server manager including at least one non-transitory computer-readable media encoded with instructions for a gateway, the gateway configured to receive and route API calls;
the target file server, the target file server configured to provide access to at least one namespace of files; and
an API permissions repository configured to store associations between users, roles, file servers, and permissions for API calls;
wherein the file server manager is further configured to access the API permissions repository to request API permissions associated with a received API call for the target file server, and wherein the file server manager is configured to allow or decline the API call based on permissions information in the API permissions repository.

### Claim 11 (depends on 10)

The system of claim 10, wherein the gateway is configured to route the received API call to the target file server based on identification of the target file server in the API call.

### Claim 12 (depends on 11)

The system of claim 11, wherein the identification of the target file server comprises a URI or URL received with the API call.

### Claim 13 (depends on 10)

The system of claim 10, wherein the API permissions repository includes stored associations between respective identifications of each of the multiple file servers and operation types expected at each of the multiple file servers.

### Claim 14 (depends on 10)

The system of claim 10, wherein the gateway is further configured to provide a user interface for updating permissions in the API permissions repository.

### Claim 15 (depends on 14)

The system of claim 14, wherein the gateway is configured to receive, through the user interface, a request to provide a first permission to a particular user; and prompt, through the user interface, for authorization to provide a second permission to the particular user, wherein the first permission utilizes the second permission.

### Claim 16 (depends on 15)

The system of claim 15, wherein the second permission comprises a network permission.

### Claim 17

At least one non-transitory computer-readable storage medium, the computer-readable storage medium encoded with instructions which, when executed, cause a system to perform operations comprising:
receive an API call including an identified target file server, the identified target file server being one of multiple file servers managed by a file server manager;
prepare a request for an API permissions repository based on the identified target file server and a user;
receive an API permission based on the user and the identified target file server from the permissions repository; and
allow or decline the API call by the user in accordance with the API permission.

### Claim 18 (depends on 17)

The computer-readable storage medium of claim 17, wherein the instructions further configure the system to rout the API call to the target file server based on an identification of the target file server.

### Claim 19 (depends on 18)

The computer-readable storage medium of claim 18, wherein the identification comprises a URI or URL received with the API call.

### Claim 20 (depends on 17)

The computer-readable storage medium of claim 17, wherein the operations further comprise storing associations between respective identifications of each of the multiple file servers and operation types expected at each of the multiple file servers.

### Claim 21 (depends on 17)

The computer-readable storage medium of claim 17, wherein the operations further comprise:
receiving, through a user interface, a request to provide a first permission to a particular user; and
prompt, through the user interface, for authorization to provide a second permission to the particular user, wherein the first permission utilizes the second permission.

### Claim 22 (depends on 21)

The computer-readable storage medium of claim 21, wherein the second permission comprises a network permission.
