Managed LDAP entries

Patent metadata

Field	Value
Publication number	US-10375012-B2
Application number	US-201715614546-A
Country	US
Kind code	B2
Filing date	Jun 5, 2017
Priority date	Oct 26, 2010
Publication date	Aug 6, 2019
Grant date	Aug 6, 2019

Abstract

A method and apparatus for maintaining in a Lightweight Directory Access Protocol (LDAP) repository entries that are managed by an LDAP directory server. An LDAP directory server receives a client request to add a specified entry to an LDAP repository, determines, based on a managed entry configuration, that the specified entry requires a managed entry operation, and adds the specified entry to the LDAP repository. The LDAP directory server further adds a managed entry to the LDAP repository in accordance with the managed entry operation, where the managed entry is added to the LDAP repository without receiving any client request specifying the managed entry.

First claim

What is claimed is:

1. A method comprising:
receiving, at a Light Weight Directory Access Protocol (LDAP) directory server, a client request from a client device to add a specified entry to a LDAP repository;
adding the specified entry to the LDAP repository;
storing, at the LDAP repository, a managed entry configuration in one or more configuration information entries of the LDAP repository, the managed entry configuration comprising a definition of an entry type triggering a managed entry operation, and template information for a managed entry;
determining, based on the managed entry configuration, that the specified entry has the entry type that triggers the managed entry operation involving the managed entry, the template information for the managed entry specifying one or more static attributes to be included in the managed entry upon creation of the managed entry;
creating the managed entry as a new entry that is separate from the specified entry and that comprises the one or more static attributes specified in the template information for the managed entry; and
adding, by a processing device of the LDAP directory server, the created managed entry to the LDAP repository separate from the specified entry, wherein the managed entry is added in accordance with the managed entry operation and wherein the managed entry is managed by the LDAP directory server without any client interaction.

2. The method of claim 1 wherein:
the managed entry is created using an identifier of the specified entry, and at least one of the one or more static attributes or one or more mapped attributes linked to corresponding attributes of the specified entry; and
adding the created managed entry to the LDAP repository comprises:
upon a successful addition of the managed entry to the LDAP repository, adding an identifier of the managed entry to the specified entry.

3. The method of claim 1 further comprising:
receiving a client request for an operation pertaining to the managed entry, the operation comprising any one of a deletion of the managed entry, a modification of the managed entry or a renaming of the managed entry;
refraining from performing the requested operation; and
notifying the client device that the managed entry is to be manually unlinked prior to performing the requested operation.

4. The method of claim 1 wherein the managed entry is of a different type than the specified entry.

5. The method of claim 1 further comprising:
receiving a second client request of the client device for an operation pertaining to the specified entry from the LDAP repository;
determining, based on the managed entry configuration, that the specified entry has the entry type that triggers the managed entry operation involving the managed entry;
performing the requested operation for the specified entry from the LDAP repository; and
performing the managed entry operation for the corresponding managed entry from the LDAP repository.

6. The method of claim 5 wherein the operation pertaining to the specified entry is a deletion of the specified entry, and the managed entry operation is a deletion of the corresponding managed entry; and wherein the method further comprises:
upon deleting the specified entry, determining whether the managed entry is present;
in response to the managed entry being present, deleting the managed entry from the LDAP repository; and
in response to the managed entry not being present, recording an error in an error log.

7. The method of claim 5 wherein:
the operation pertaining to the specified entry is a modification of the specified entry; and
the managed entry operation is a modification of attributes of the corresponding managed entry that are mapped to modified attributes of the specified entry.

8. The method of claim 5 wherein:
the operation pertaining to the specified entry is a renaming of the specified entry; and
performing the managed entry operation comprises:
determining whether the renaming affects a scope of the managed entry configuration; and
if the renaming does not affect the scope of the managed entry configuration, renaming the corresponding managed entry.

9. The method of claim 8 further comprising:
determining that the renaming is moving the specified entry outside of the scope of the managed entry configuration;
deleting the corresponding managed entry from the LDAP repository; and
updating the specified entry to unlink the corresponding managed entry from the specified entry.

10. The method of claim 8 further comprising:
determining that the renaming is moving the specified entry into the scope of the managed entry configuration;
adding the corresponding managed entry to the LDAP repository; and
updating the specified entry to link the corresponding managed entry to the specified entry.

11. The method of claim 1 wherein the entry type is defined by a schema, and the entry type is associated with a set of mandatory attributes and a set of optional attributes.

12. The method of claim 1 wherein the managed entry configuration information comprises parameters to be satisfied to trigger the managed entry operation.

13. The method of claim 1 wherein the template information is stored in the LDAP directory as a separate LDAP template entry.

14. The method of claim 13 wherein the separate LDAP template entry is located in a tree of the LDAP repository.

15. The method of claim 14 wherein the tree is a replicated tree and locating the separate LDAP template entry in the replicated tree ensures that master copies of the LDAP repository use a same template.

16. The method of claim 1 further comprising:
determining that an addition of the specified entry to the LDAP repository was unsuccessful; and
reporting an error to the client device.

17. The method of claim 1 further comprising:
determining that an addition of the managed entry to the LDAP repository was unsuccessful; and
recording an error in an error log.

18. The method of claim 1 further comprising:
receiving a request pertaining to the managed entry;
determining whether the request pertaining to the managed entry is an internal request or a client request;
responsive to determining that the request pertaining to the managed entry is an internal request, performing a requested operation on the managed entry; and
responsive to determining that the request pertaining to the managed entry is a client request, sending a message to the client device that a link between the managed entry and the specified entry is to be removed prior to performing the requested operation.

19. A system for a Light Weight Directory Access Protocol (LDAP) directory server, the system comprising:
a memory comprising an LDAP repository; and
a processor, coupled to the memory, to:
receive a client request from a client device to add a specified entry to the LDAP repository;
add the specified entry to the LDAP repository;
store, at the LDAP repository, a managed entry configuration in one or more configuration information entries of the LDAP repository, the managed entry configuration comprising a definition of an entry type triggering a managed entry operation, and template information for a managed entry;
determine, based on the managed entry configuration, that the specified entry has the entry type that triggers the managed entry operation involving the managed entry, the template information for the managed entry specifying one or more static attributes to be included in the managed entry upon the creation of the

Assignees

• Red Hat Inc

Inventors

• Kinder Nathan G
• Sorce Simo

Classifications

• H04L61/1523 Primary

  Electricity · mapped topic

• H04L61/4523 Primary

  using lightweight directory access protocol [LDAP] · CPC title