# US 2015/0033365 A1 · External platform extensions in a multi-tenant environment

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

- Number: US 2015/0033365 A1
- Document ID: US20150033365A1
- Status: Published application
- Kind: A1
- Application number: 14/032,474
- Filed: 2013-09-20
- Published: 2015-01-29
- Earliest claimed: 2013-07-25
- Assignees: Oracle International Corporation
- Applicants: Oracle International Corporation
- Inventors: David R. Mellor; Andrew H. Jones; Charles Lattimer
- Web page: https://patentgrep.com/patent/US20150033365A1

## CPC

- H04L 63/102: {Entity profiles}
- G06F 8/65: Updates (security arrangements therefor G06F21/57)
- G06F 8/71: Version control (security arrangements therefor G06F21/57); Configuration management
- G06F 16/113: {Details of archiving (lifecycle management in storage systems G06F3/0649; point-in-time backing up or restoration of persistent data G06F11/1446)}
- G06F 16/1756: {based on delta files}
- G06F 16/211: {Schema design and management}
- G06F 16/83: Querying
- G06F 16/835: Query processing
- G06F 21/604: {Tools and structures for managing or administering access control systems}
- G06F 21/62: Protecting access to data via a platform, e.g. using keys or access control rules
- G06F 21/6209: {to a single file or object, e.g. in a secure envelope, encrypted and accessed using a key, or with access control rules appended to the object itself}
- G06F 21/6218: {to a system of files or objects, e.g. local or distributed file system or database}
- H04L 41/0803: Configuration setting
- H04L 63/101: {Access control lists [ACL]}
- H04L 67/1001: for accessing one among a plurality of replicated servers
- G06F 8/658: Incremental updates; Differential updates
- G06F 9/44505: {Configuring for program initiating, e.g. using registry, configuration files}
- G06F 2221/2141: Access rights, e.g. capability lists, access control lists, access tables, access matrices
- 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

Enforcing access control to individual extensions of services in a multi-tenant cloud environment by initializing objects for the extension based on public and private configuration files with service access rules that are merged is described. This allows third party vendors to specify payment rules for their own extensions while securely keeping the core extension configuration files. Tenants of the multi-tenant cloud environment can pick and choose which services to purchase, and the cloud environment automates the process of accessing the service using the third-party developer's tenant access list rules.

## Claims

### Claim 1

A method to allow third-party developers to enforce tenant access to their features in a multi-tenant cloud environment, the method comprising:
delivering, to a third-party developer, a copy of a config file that is compatible with a file schema, the file schema defining an element, child element, and attribute;
receiving, from the third-party developer, an archive file including a delta file created from the third-party developer editing the copy of the config file, the delta file including one or more configurations for class definitions for a feature of a service on a multi-tenant cloud environment, the delta file including a tenant access list rule for the feature, the delta file being compatible with the file schema;
merging, in a multi-tenant cloud environment using at least one processor operatively coupled with a memory, the delta file with the config file to create an executable code config file having the service feature and tenant access list rule, the executable code config file being compatible with the file schema;
instantiating objects for the service feature based on the executable code config file;
granting access to the service feature for a tenant in accordance with the tenant access list rule in the executable code config file.

### Claim 2 (depends on 1)

The method of claim 1 further comprising:
blocking access to the service feature for a tenant in accordance with the service access rule in the executable code config file.

### Claim 3 (depends on 2)

The method of claim 2 wherein the blocking is in accordance with a number-of-seats maximum in the tenant access list.

### Claim 4 (depends on 1)

The method of claim 1 further comprising:
incrementing a counter in the multi-tenant cloud environment based upon the granting of access.

### Claim 5 (depends on 1)

The method of claim 1 further comprising:
automatically transferring money between accounts based on the granting of access.

### Claim 6 (depends on 1)

The method of claim 1 further comprising:
automatically sending a message to the third-party developer based on the granting of access.

### Claim 7 (depends on 1)

The method of claim 1 wherein the message includes an email, instant message, online post, short message service (SMS) text message, or multimedia messaging service (MMS) message.

### Claim 8 (depends on 1)

The method of claim 1 further comprising:
automatically sending a message to a tenant based on the instantiating of objects, advising of an update to the service.

### Claim 9 (depends on 1)

The method of claim 1 further comprising:
creating the delta file by tracking changes to the copy of the config file.

### Claim 10 (depends on 1)

The method of claim 1 further comprising:
creating the delta file by comparing a the copy of the config file to the edited copy of the config file.

### Claim 11 (depends on 1)

The method of claim 1 wherein the delivered copy of the config file has no child elements.

### Claim 12 (depends on 1)

The method of claim 1 wherein the archive is a MAR file.

### Claim 13 (depends on 1)

The method of claim 1 wherein merging the delta file with the config file includes merging a layered customization MAR file with a configuration file.

### Claim 14 (depends on 1)

The method of claim 1 wherein the config file schema includes an extensible markup language (XML) schema.

### Claim 15 (depends on 1)

The method of claim 1 wherein the empty copy of the config file is in an ADF library jar file.

### Claim 16 (depends on 1)

The method of claim 1 wherein the service includes a Java service.

### Claim 17 (depends on 1)

A machine-readable tangible medium embodying information indicative of instructions for causing one or more machines to perform the operations of claim 1.

### Claim 18 (depends on 1)

A computer system executing instructions, the system comprising:
at least one processor;
a memory operatively coupled with the at least one processor, the processor executing computer code stored in the memory for performing the operations of claim 1.

### Claim 19

A method to allow third-party developers to enforce tenant access to their features in a multi-tenant cloud environment, the method comprising:
receiving a copy of a config file, the config file being compatible with an extensible markup language (XML) file schema that defines an element, child element, and attribute;
editing the copy of the config file to add configurations for class definitions for a feature of a service in a multi-tenant cloud environment;
editing the copy of the config file to list one or more tenant rules authorizing access to the service;
packaging the edited copy of the config file in a metadata archive (MAR) file;
delivering the MAR file to the multi-tenant cloud environment;
triggering, using at least one processor operatively coupled with a memory, the multi-tenant cloud environment to instantiate objects based on the class definitions and automatically grant the one or more tenants access to the service.

### Claim 20 (depends on 19)

The method of claim 19 wherein the packaging includes packaging the edited copy of the config file in a MAR file along with a shared library of class files.
