# US 2018/0026984 A1 · Access authentication for cloud-based shared content

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

- Number: US 2018/0026984 A1
- Document ID: US20180026984A1
- Status: Published application
- Kind: A1
- Application number: 15/656,943
- Filed: 2017-07-21
- Published: 2018-01-25
- Earliest claimed: 2016-07-22
- Assignees: Box, Inc.
- Applicants: Box, Inc.
- Inventors: Varun Maker; Aniket Shivajirao Patil; Reshma Ananthakrishnan; Drew Branden
- Web page: https://patentgrep.com/patent/US20180026984A1

## CPC

- H04L 63/0884: {by delegation of authentication, e.g. a proxy authenticates an entity to be authenticated on behalf of this entity vis-à-vis an authentication entity}
- H04L 63/083: {using passwords (cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226)}
- H04L 63/102: {Entity profiles}
- H04L 67/10: in which an application is distributed across nodes in the network (software deployment G06F8/60; multiprogramming arrangements G06F9/46)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

Systems for managing content in a cloud-based service platform. Embodiments operate using a server in a cloud-based environment. The server is configured to interface with one or more storage devices that store content objects. The server is further configured to carry out a protocol between the server and a user interface that supports access to the storage devices. In example configurations, the server is capable of processing at least three different access requests types that are raised from a user interface. A first access type corresponds to an access request type by a registered user. A second access type corresponds to an access request type to permit an application that is invoked by operation of the user interface to be run on the server and to produce further content objects. A third access type corresponds to an access request type that uses an inherited user profile to run a microservice.

## Claims

### Claim 1

A method comprising:
identifying a server in a cloud-based environment, wherein the server is configured to interface with one or more storage devices that store content objects; and
configuring the server to carry out a protocol between the server and a user interface that supports access to the one or more storage devices, the server being capable of processing at least three different access requests types by,
processing a first access request type using a first credential corresponding to a first user,
processing a second access request type issued to an application that is invoked by operation of the user interface, and
processing a third access request type based at least in part on at least a portion of an inherited user profile, wherein the inherited user profile corresponds to a user that is different from the first user.

### Claim 2 (depends on 1)

The method of claim 1,
wherein the first access request type comprises a username and password pair of the first user to authorize a first access scope, and
wherein the second access request type invokes the application to authorize a second access scope, and
wherein the third access request type invokes a microservice to authorize a third access scope.

### Claim 3 (depends on 2)

The method of claim 2,
wherein the first access scope comprises to at least a first set of files hosted on the server,
wherein the second access scope comprises access to a second set of files, at least some of the second set of files being different from the first set of files, and
wherein the third access scope comprises access to a third set of files, at least some of the third set of files being different from the first set of files and at least some of the third set of files being different from the second set of files.

### Claim 4 (depends on 2)

The method of claim 2,
wherein the first access scope comprises user-owned content,
wherein the second access scope comprises application-produced content, and
wherein the third access scope comprises microservice-produced content.

### Claim 5 (depends on 2)

The method of claim 2, wherein at least one of, the first access scope, the second access scope, or the third access scope, comprises at least one of, a set of content, or a set of APIs.

### Claim 6 (depends on 1)

The method of claim 1, further comprising registering the application as being associated with an enterprise.

### Claim 7 (depends on 1)

The method of claim 1, further comprising registering microservice.

### Claim 8 (depends on 7)

The method of claim 7, further comprising generating at least one token associated with the microservice.

### Claim 9 (depends on 8)

The method of claim 8, wherein the token is at least one of, a primary token, or a secondary token.

### Claim 10

A computer program, embodied in a non-transitory computer readable medium, the non-transitory computer readable medium having stored thereon a sequence of instructions which, when stored in memory and executed by one or more processors causes the one or more processor to perform a set of acts, the acts comprising:
identifying a server in a cloud-based environment, wherein the server is configured to interface with one or more storage devices that store content objects; and
configuring the server to carry out a protocol between the server and a user interface that supports access to the one or more storage devices, the server being capable of processing at least three different access requests types by,
processing a first access request type using a first credential corresponding to a first user,
processing a second access request type issued to an application that is invoked by operation of the user interface, and
processing a third access request type based at least in part on at least a portion of an inherited user profile, wherein the inherited user profile corresponds to a user that is different from the first user.

### Claim 11 (depends on 10)

The computer readable medium of claim 10,
wherein the first access request type comprises a username and password pair of the first user to authorize a first access scope, and
wherein the second access request type invokes the application to authorize a second access scope, and
wherein the third access request type invokes a microservice to authorize a third access scope.

### Claim 12 (depends on 11)

The computer readable medium of claim 11,
wherein the first access scope comprises to at least a first set of files hosted on the server,
wherein the second access scope comprises access to a second set of files, at least some of the second set of files being different from the first set of files, and
wherein the third access scope comprises access to a third set of files, at least some of the third set of files being different from the first set of files and at least some of the third set of files being different from the second set of files.

### Claim 13 (depends on 11)

The computer readable medium of claim 11,
wherein the first access scope comprises user-owned content,
wherein the second access scope comprises application-produced content, and
wherein the third access scope comprises microservice-produced content.

### Claim 14 (depends on 11)

The computer readable medium of claim 11, wherein at least one of, the first access scope, the second access scope, or the third access scope, comprises at least one of, a set of content, or a set of APIs.

### Claim 15 (depends on 10)

The computer readable medium of claim 10, further comprising instructions which, when stored in memory and executed by the one or more processors causes the one or more processors to perform acts of registering the application as being associated with an enterprise.

### Claim 16 (depends on 10)

The computer readable medium of claim 10, further comprising instructions which, when stored in memory and executed by the one or more processors causes the one or more processors to perform acts of registering microservice.

### Claim 17 (depends on 16)

The computer readable medium of claim 16, further comprising instructions which, when stored in memory and executed by the one or more processors causes the one or more processors to perform acts of generating at least one token associated with the microservice.

### Claim 18 (depends on 17)

The computer readable medium of claim 17, wherein the token is at least one of, a primary token, or a secondary token.

### Claim 19

A system comprising:
a storage medium having stored thereon a sequence of instructions; and
one or more processors that execute the instructions to cause the one or more processors to perform a set of acts, the acts comprising,
identifying a server in a cloud-based environment, wherein the server is configured to interface with one or more storage devices that store content objects; and
configuring the server to carry out a protocol between the server and a user interface that supports access to the one or more storage devices, the server being capable of processing at least three different access requests types by,
processing a first access request type using a first credential corresponding to a first user,
processing a second access request type issued to an application that is invoked by operation of the user interface, and
processing a third access request type based at least in part on at least a portion of an inherited user profile, wherein the inherited user profile corresponds to a user that is different from the first user.

### Claim 20 (depends on 19)

The system of claim 19,
wherein the first access request type comprises a username and password pair of the first user to authorize a first access scope, and
wherein the second access request type invokes the application to authorize a second access scope, and
wherein the third access request type invokes a microservice to authorize a third access scope.
