# US 2020/0007549 A1 · Service-to-Service Role Mapping Systems and Methods

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

- Number: US 2020/0007549 A1
- Document ID: US20200007549A1
- Status: Published application
- Kind: A1
- Application number: 16/022,493
- Filed: 2018-06-28
- Published: 2020-01-02
- Earliest claimed: 2018-06-28
- Assignees: Elasticsearch B.V.
- Applicants: Elasticsearch B.V.
- Inventors: Clinton Gormley
- Web page: https://patentgrep.com/patent/US20200007549A1

## CPC

- H04L 63/102: {Entity profiles}
- G06F 16/9535: Search customisation based on user profiles and personalisation
- H04L 63/104: {Grouping of entities}
- H04L 63/105: {Multiple levels of security}
- H04L 63/20: {for managing network security; network security policies in general (filtering policies H04L63/0227)}
- 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

Service-to-service role mapping systems and methods are disclosed herein. An example role mapping service is positioned between a directory service and a search engine service, the directory service managing user information and permissions for users, the role mapping service mapping one or more search engine service roles to a user based on the user information and permissions received from the directory service.

## Claims

### Claim 1

A method, comprising:
establishing a plurality of roles for a first service;
mapping a role of the plurality of roles to a user based on metadata of the user received from a second service, the metadata being indicative of permissions granted to the user within the second service as well as information that is indicative of the user within the second service; and
assigning the role to the user.

### Claim 2 (depends on 1)

The method according to claim 1, wherein the first service comprises a search engine service and the second service comprises a directory service.

### Claim 3 (depends on 1)

The method according to claim 1, wherein the mapping of the role is defined by a domain-specific language having parameters that match with one or more of the permissions granted to the user from the second service.

### Claim 4 (depends on 3)

The method according to claim 3, further comprising creating a role-mapping expression for each of the plurality of roles, the role-mapping expression comprising:
a field rule that defines one or more field and value pairs; and
a user field that is indicative of a distinguished name of the user or any group to which the user belongs.

### Claim 5 (depends on 1)

The method according to claim 1, further comprising receiving an access request for the first service from a computing device associated with the user, prior to the step of assigning.

### Claim 6 (depends on 1)

The method according to claim 1, further comprising generating a mapping request comprising:
a designation if a mapping is enabled or disabled;
a list of the plurality of roles granted to users that match role-mapping rules; and
rules that determine the users matched by the role-mapping rules.

### Claim 7 (depends on 6)

The method according to claim 6, wherein the mapping request further comprises optional metadata that additionally defines roles assigned to the users.

### Claim 8

A system, comprising:
a role mapping service configured to:
establish roles for a first service, the roles defining permissions granted to a user for the first service;
map one or more roles to the user based on metadata of the user received from a second service, the metadata being indicative of permissions granted to the user by the second service; and
assign the one or more roles to the user.

### Claim 9 (depends on 8)

The system according to claim 8, wherein the role mapping service is distinct from and communicatively coupled to the first service and the second service.

### Claim 10 (depends on 8)

The system according to claim 8, wherein the role mapping service is configured to function as an application programming interface between the first service and the second service, the role mapping service providing role mapping and assignment of the roles to users.

### Claim 11 (depends on 8)

The system according to claim 8, wherein the metadata from the second service further comprises information that is indicative of the user within the second service.

### Claim 12 (depends on 8)

The system according to claim 8, wherein the first service comprises a search engine service and the second service comprises a directory service of a network protocol layer.

### Claim 13 (depends on 8)

The system according to claim 8, wherein the role mapping service employs a domain-specific language having parameters that matched with one or more of the permissions granted to the user from the second service.

### Claim 14 (depends on 13)

The system according to claim 13, wherein the role mapping service creates a role-mapping expression for each of the roles, the role-mapping expression comprising any one or more of the following:
a field rule that defines one or more field and value pairs; or
a user field that is indicative of a distinguished name of the user or any group to which the user belongs, or other information that is indicative of an individual or user.

### Claim 15 (depends on 8)

The system according to claim 8, wherein the role mapping service is further configured to receive an access request for the first service from a computing device associated with the user, prior to role assignment.

### Claim 16 (depends on 8)

The system according to claim 8, wherein the role mapping service is further configured to receive a mapping request comprising:
a designation if a mapping is enabled or disabled;
a list of the roles granted to users that match role-mapping rules; and
rules that determine the users matched by the role-mapping rules.

### Claim 17 (depends on 16)

The system according to claim 16, wherein the mapping request further comprises optional metadata that additionally defines roles assigned to the users.

### Claim 18

A system, comprising:
a role mapping service positioned between a directory service and a search engine service, the directory service managing user information and permissions for users, the role mapping service mapping one or more search engine service roles to a user based on the user information and permissions received from the directory service.

### Claim 19 (depends on 18)

The system according to claim 18, wherein the one or more search engine service roles define document level permissions for users for documents found using the search engine service.
