Controlling public access of resources in a secure distributed storage system
AssigneePure Storage, Inc.
InventorsLuis Pablo Pabon, Grant William Griffiths
Life of this patent
Estimating the term…
Abstract
A method for controlling public access of resources in a secure distributed storage system using an API level model. A request to access a volume is checked for authentication. If the request does not include an authentication token ID, a guest role is created and assigned to the requestor. The guest role can only access public volumes or owned volumes that specifically allow public access. The guest role can be updated using API management.
Claims20
A method comprising:
- receiving a request, from a user, to access a volume;
- determining, via an authentication module, that the request does not include a valid token ID;
- in response to determining that the request does not include a valid token ID, creating a user info object with a role of “guest” and setting a guest Boolean to “true”;
- determining, via an authorization module, that the role of guest is allowed to access the volume in the manner presented in the request;
- in response to determining that the role of guest is allowed to access the volume, determining whether the volume is owned or public;
- in response to determining that the volume is owned, giving access to the volume for the role of guest only if the volume is specified by the owner to give public access, otherwise denying the request;
- in response to determining that the volume is public, giving access to the volume only if the role of guest is allowed to access the volume in the manner presented in the request, otherwise denying the request.
A computing system comprising:
- a processor;
- and
- memory, the memory storing instructions to cause the processor to perform a method, the method comprising:
- receiving a request, from a user, to access a volume;
- checking, via an authentication module, whether the request includes a valid token ID;
- if the request does not include a valid token ID, creating a user info object with a role of “guest” and setting a guest Boolean to “true”;
- determining, via an authorization module, whether the role of guest is allowed to access the volume in the manner presented in the request;
- if the request passes the authorization module, determining whether the volume is owned or public;
- if the volume is owned, giving access to the volume for the guest role only if the volume is specified by the owner to give public access, otherwise denying the request;
- if the volume is public, giving access to the volume only if the role of guest is allowed to access the volume in the manner presented in the request, otherwise denying the request;
- if the request does not pass the authorization module, denying the request to access the volume.
One or more non-transitory machine-readable media having instructions stored thereon for performing a method, the method comprising:
- receiving a request, from a user, to access a volume;
- checking, via an authentication module, whether the request includes a valid token ID;
- if the request does not include a valid token ID, creating a user info object with a role of “guest” and setting a guest Boolean to “true”;
- determining, via an authorization module, whether the role of guest is allowed to access the volume in the manner presented in the request;
- if the request passes the authorization module, determining whether the volume is owned or public;
- if the volume is owned, giving access to the volume for the guest role only if the volume is specified by the owner to give public access, otherwise denying the request;
- if the volume is public, giving access to the volume only if the role of guest is allowed to access the volume in the manner presented in the request, otherwise denying the request;
- if the request does not pass the authorization module, denying the request to access the volume.
Dependencies are inferred from the claim text.