# US 2014/0156684 A1 · Schema and query abstraction for different ldap service providers

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

- Number: US 2014/0156684 A1
- Document ID: US20140156684A1
- Status: Published application
- Kind: A1
- Application number: 13/692,457
- Filed: 2012-12-03
- Published: 2014-06-05
- Earliest claimed: 2012-12-03
- Assignees: Red Hat Israel, Ltd.
- Applicants: Red Hat Israel, Ltd.
- Inventors: Yair Zaslavsky; Roy Golan; Oved Ourfalli
- Web page: https://patentgrep.com/patent/US20140156684A1

## CPC

- G06F 16/242: Query formulation
- G06F 16/258: {Data format conversion from or to a database}
- G06F 16/282: {Hierarchical databases, e.g. IMS, LDAP data stores or Lotus Notes}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)

## Abstract

A lightweight directory access (LDAP) broker receives user information associated with a query for information in an LDAP repository. The query may be in an abstraction format. The LDAP broker determines a computing domain in view of the user information and retrieves a configuration file associated with the computing domain. The configuration file comprises a mapping for the query between an abstraction format and a vendor specific format. The LDAP broker converts the query to the vendor specific format in view of the mapping in the configuration file.

## Claims

### Claim 1

A method comprising:
receiving user information associated with a query for information in a lightweight directory access protocol (LDAP) repository, the query received in an abstraction format;
determining a computing domain in view of the user information;
retrieving, by a processing device, a configuration file associated with the computing domain, the configuration file comprising a mapping for the query between an abstraction format and a vendor specific format; and
converting the query to the vendor specific format in view of the mapping in the configuration file.

### Claim 2 (depends on 1)

The method of claim 1, wherein the mapping in the configuration file comprises at least one of LDAP schema, LDAP query syntax, or an LDAP authentication protocol.

### Claim 3 (depends on 1)

The method of claim 1, wherein determining the computing domain comprises comparing a user identifier in the user information to a list of authorized user identifiers associated with the computing domain.

### Claim 4 (depends on 1)

The method of claim 1, wherein the computing domain comprises a directory server, an authentication server, and the LDAP repository.

### Claim 5 (depends on 4)

The method of claim 4, wherein the configuration file is stored in the LDAP repository.

### Claim 6 (depends on 1)

The method of claim 1, further comprising:
determining whether a syntax of the query matches a vendor specific syntax for the computing domain; and
if the syntax of the query does not match the vendor specific syntax, converting the syntax of the query to the vendor specific syntax in view of the mapping in the configuration file.

### Claim 7 (depends on 1)

The method of claim 1, further comprising:
determining whether object and attribute names in the query match a vendor specific schema for the computing domain; and
if the object and attribute names in the query do not match the vendor specific schema, converting the object and attribute names in the query to the vendor specific schema in view of the mapping in the configuration file.

### Claim 8

A system comprising:
a processing device; and
a memory coupled to the processing device; and
a lightweight directory access protocol (LDAP) broker, executable by the processing device from the memory, to:
receive user information associated with a query for information in a lightweight directory access protocol (LDAP) repository, the query received in an abstraction format;
determine a computing domain in view of the user information;
retrieve a configuration file associated with the computing domain, the configuration file comprising a mapping for the query between an abstraction format and a vendor specific format; and
convert the query to the vendor specific format in view of the mapping in the configuration file.

### Claim 9 (depends on 8)

The system of claim 8, wherein the mapping in the configuration file comprises at least one of LDAP schema, LDAP query syntax, or an LDAP authentication protocol.

### Claim 10 (depends on 8)

The system of claim 8, wherein to determine the computing domain, the LDAP broker to compare a user identifier in the user information to a list of authorized user identifiers associated with the computing domain.

### Claim 11 (depends on 8)

The system of claim 8, wherein the computing domain comprises a directory server, an authentication server, and the LDAP repository.

### Claim 12 (depends on 11)

The system of claim 11, wherein the configuration file is stored in the LDAP repository.

### Claim 13 (depends on 8)

The system of claim 8, the LDAP broker further to:
determine whether a syntax of the query matches a vendor specific syntax for the computing domain; and
if the syntax of the query does not match the vendor specific syntax, convert the syntax of the query to the vendor specific syntax in view of the mapping in the configuration file.

### Claim 14 (depends on 8)

The system of claim 8, the LDAP broker further to:
determine whether object and attribute names in the query match a vendor specific schema for the computing domain; and
if the object and attribute names in the query do not match the vendor specific schema, convert the object and attribute names in the query to the vendor specific schema in view of the mapping in the configuration file.

### Claim 15

A non-transitory machine-readable storage medium storing instructions which, when executed, cause a processing device to perform a operations comprising:
receiving user information associated with a query for information in a lightweight directory access protocol (LDAP) repository, the query received in an abstraction format;
determining a computing domain in view of the user information;
retrieving, by a processing device, a configuration file associated with the computing domain, the configuration file comprising a mapping for the query between an abstraction format and a vendor specific format; and
converting the query to the vendor specific format in view of the mapping in the configuration file.

### Claim 16 (depends on 15)

The non-transitory machine-readable storage medium of claim 15, wherein the mapping in the configuration file comprises at least one of LDAP schema, LDAP query syntax, or an LDAP authentication protocol.

### Claim 17 (depends on 15)

The non-transitory machine-readable storage medium of claim 15, wherein determining the computing domain comprises comparing a user identifier in the user information to a list of authorized user identifiers associated with the computing domain.

### Claim 18 (depends on 15)

The non-transitory machine-readable storage medium of claim 15, wherein the computing domain comprises a directory server, an authentication server, and the LDAP repository.

### Claim 19 (depends on 18)

The non-transitory machine-readable storage medium of claim 18, wherein the configuration file is stored in the LDAP repository.

### Claim 20 (depends on 15)

The non-transitory machine-readable storage medium of claim 15, further comprising:
determining whether a syntax of the query matches a vendor specific syntax for the computing domain; and
if the syntax of the query does not match the vendor specific syntax, converting the syntax of the query to the vendor specific syntax in view of the mapping in the configuration file.

### Claim 21 (depends on 15)

The non-transitory machine-readable storage medium of claim 15, further comprising:
determining whether object and attribute names in the query match a vendor specific schema for the computing domain; and
if the object and attribute names in the query do not match the vendor specific schema, converting the object and attribute names in the query to the vendor specific schema in view of the mapping in the configuration file.