# US 2025/0094615 A1 · Automated authorization management of database accounts

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

- Number: US 2025/0094615 A1
- Document ID: US20250094615A1
- Status: Published application
- Kind: A1
- Application number: 18/883,343
- Filed: 2024-09-12
- Published: 2025-03-20
- Earliest claimed: 2023-09-19
- Assignees: State Farm Mutual Automobile Insurance Company
- Applicants: State Farm Mutual Automobile Insurance Company
- Inventors: Clete Rivers Blackwell, II; Hairong Liu
- Web page: https://patentgrep.com/patent/US20250094615A1

## CPC

- G06F 21/6218: {to a system of files or objects, e.g. local or distributed file system or database}
- G06F 16/27: Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
- G06F 2221/2113: Multi-level security, e.g. mandatory access control
- G06F 2221/2141: Access rights, e.g. capability lists, access control lists, access tables, access matrices
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

Techniques described herein relate to automated management of database accounts within cloud environments and other large-scale computing environments. In such environments, an identity provider service for an organization may maintain the various roles for the users associated with the organization. As described herein, a database account synchronization system may synchronize the user accounts within the database systems of the organization based on the corresponding roles stored within the identity provider. In some examples, the database account synchronization system may periodically query the identity provider to retrieve user-role mappings for the various user groups defined by the identity provider. For each user group, the database account synchronization system may query the organization database systems, compare the user permissions of each database to the user-role mappings within the identity provider, and update the database user accounts to synchronize the databases with the identity provider.

## Claims

### Claim 1

A computer system, comprising:
one or more processors; and
one or more non-transitory computer-readable media storing computer-executable instructions that, when executed by the one or more processors, cause the one or more processors to perform operations comprising:
receiving a database account synchronization request associated with a cloud service provider;
accessing an identity provider service of the cloud service provider to determine a mapping of a first resource access role to a first user identity;
receiving, from the identity provider service, a web token associated with the first user identity;
logging into the cloud service provider using the web token associated with the first user identity;
receiving, from the cloud service provider, and based on successfully logging into the cloud service provider using the web token, first credentials associated with the first user identity;
accessing a first database system associated with the cloud service provider, using the first credentials, to determine a first database user corresponding to the first user identity; and
modifying the first database user within the first database system, based at least in part on the mapping.

### Claim 2 (depends on 1)

The computer system of claim 1, wherein receiving the database account synchronization request is based on a periodic time-based synchronization trigger.

### Claim 3 (depends on 1)

The computer system of claim 1, the operations further comprising, in response to receiving the database account synchronization request:
accessing a plurality of database systems associated with the cloud service provider, including the first database system and a second database system, wherein the first database system is implemented using first database management architecture, and the second database system is implemented using different second database management architecture;
determining, within the second database system, a second database user corresponding to the first user identity; and
modifying the second database user within the second database system, based at least in part on the mapping.

### Claim 4 (depends on 1)

The computer system of claim 1, the operations further comprising:
accessing the identity provider service to determine a second mapping of a second resource access role to the first user identity, wherein modifying the first database user is further based at least in part on the second mapping.

### Claim 5 (depends on 1)

The computer system of claim 1, wherein determining the mapping of the first resource access role to the first user identity comprises:
invoking an application programming interface of the identity provider service; and
receiving, via the application programming interface, a first listing of user identities associated with the first resource access role.

### Claim 6 (depends on 5)

The computer system of claim 5, wherein determining the first database user corresponding to the first user identity comprises:
determining a prefix associated with the first resource access role;
querying the first database system to retrieve a second listing of database users associated with the prefix; and
comparing the first listing of user identities to the second listing of database users.

### Claim 7 (depends on 1)

The computer system of claim 1, wherein accessing the first database system comprises initiating a connection to the first database system, wherein the connection is not made through a proxy.

### Claim 8

A method, comprising:
receiving a database account synchronization request;
accessing an identity provider service to determine a mapping of a first resource access role to a first user identity;
accessing a first database system associated with the identity provider service to determine a first database user corresponding to the first user identity; and
modifying the first database user within the first database system, based at least in part on the mapping.

### Claim 9 (depends on 8)

The method of claim 8, wherein receiving the database account synchronization request is based on a periodic time-based synchronization trigger.

### Claim 10 (depends on 8)

The method of claim 8, further comprising, in response to receiving the database account synchronization request:
accessing a plurality of database systems associated with the identity provider service, including the first database system and a second database system, wherein the first database system is implemented using first database management architecture, and the second database system is implemented using different second database management architecture;
determining, within the second database system, a second database user corresponding to the first user identity; and
modifying the second database user within the second database system, based at least in part on the mapping.

### Claim 11 (depends on 8)

The method of claim 8, further comprising:
accessing the identity provider service to determine a second mapping of a second resource access role to the first user identity, wherein modifying the first database user is further based at least in part on the second mapping.

### Claim 12 (depends on 8)

The method of claim 8, wherein determining the mapping of the first resource access role to the first user identity comprises:
invoking an application programming interface of the identity provider service; and
receiving, via the application programming interface, a first listing of user identities associated with the first resource access role.

### Claim 13 (depends on 12)

The method of claim 12, wherein determining the first database user corresponding to the first user identity comprises:
determining a prefix associated with the first resource access role;
querying the first database system to retrieve a second listing of database users associated with the prefix; and
comparing the first listing of user identities to the second listing of database users.

### Claim 14 (depends on 8)

The method of claim 8, further comprising:
receiving, from the identity provider service, a web token associated with the first user identity; and
using the web token to log in to a cloud provider.

### Claim 15 (depends on 14)

The method of claim 14, further comprising:
receiving, in response to a successful login using the web token, first credentials from the cloud provider,
wherein modifying the first database user within the first database system is performed using the first credentials from the cloud provider.

### Claim 16 (depends on 8)

The method of claim 8, wherein accessing the first database system comprises initiating a connection to the first database system, wherein the connection is not made through a proxy.

### Claim 17

One or more non-transitory computer-readable media storing instructions executable by a processor, wherein the instructions, when executed by the processor, cause the processor to perform operations comprising:
determining, based at least in part on a periodic time-based trigger, a database account synchronization time;
in response to reaching the database account synchronization time, accessing an identity provider service to determine a mapping of a first resource access role to a first user identity;
accessing a first database system associated with the identity provider service to determine a first database user corresponding to the first user identity; and
modifying the first database user within the first database system, based at least in part on the mapping.

### Claim 18 (depends on 17)

The one or more non-transitory computer-readable media of claim 17, the operations further comprising:
receiving, from the identity provider service, a web token associated with the first user identity; and
using the web token to log in to a cloud service provider.

### Claim 19 (depends on 18)

The one or more non-transitory computer-readable media of claim 18, the operations further comprising:
receiving, in response to a successful login using the web token, first credentials from the cloud service provider,
wherein modifying the first database user within the first database system is performed using the first credentials from the cloud service provider.

### Claim 20 (depends on 17)

The one or more non-transitory computer-readable media of claim 17, wherein accessing the first database system comprises initiating a connection to the first database system, wherein the connection is not made through a proxy.
