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.

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.

Abstract: A method and apparatus are disclosed for providing virtual Lightweight Directory Access Protocol (LDAP) attribute subtypes based on metadata associated with a relevant data type. In one embodiment, a computer system receives a request that specifies an LDAP attribute. The computer system identifies metadata corresponding to a data type of the LDAP attribute and identifies, based on the metadata, an attribute subtype of the LDAP attribute.

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.

Abstract: A method and system of a distributing server that encapsulates a client package within a client software repository package. The client software repository package contains at least a portion of a client repository. The client repository is installed at the subscribing server and is associated with one or more clients that are not authorized to access the distributing server. The distributing server transmits the client software repository package to a subscribing server that is authorized to access the distributing server. The subscribing server then serves the client package to the clients through the client repository.

Abstract: Improved Lightweight Directory Access Protocol (“LDAP”) server architectures using dedicated threads to respond to different classes of LDAP requests are described and claimed. Some servers classify an LDAP request from a client, then store the classified request with similarly-classified requests. One of the classified LDAP requests is selected and executed to prepare a corresponding LDAP response. Other arrangements are also described and claimed.

Abstract: A method and apparatus for providing virtual Lightweight Directory Access Protocol (LDAP) attribute subtypes based on metadata associated with a relevant data type. In one embodiment, the method includes receiving a data request indicating an LDAP attribute having one or more attribute values associated with at least one data type. The method further includes determining metadata corresponding to the data type, and identifying attribute subtypes for the attribute based on the metadata corresponding to the data type.

Abstract: An RPM subsystem can be installed on a system that has its own native packaging subsystem. The RPM subsystem is initially delivered as a package wrapped in the non-RPM format of the native packaging system and installed. When an RPM package is installed, the RPM subsystem is also configured to create a stub entry in the native packaging, non-RPM system. The stub entry may contain the normal package information, such as name, version, description, as well as a list of files contained in a package. The stub may also contain uninstallation logic, which serves as a “callback” into the RPM subsystem during package removal and causes the RPM subsystem to remove the package when invoked. Removal of a RPM package via RPM tools also causes the removal of the stub entry.

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.

Abstract: A method and system for automatic extension of a distributed numeric range in a multi-master system are described. In one embodiment, each of a plurality of master servers is provided with a unique range of numeric values that can be assigned to clients. Each master server can dynamically extend its associated range when the range is about to be exhausted. For example, a first master server can send a range request to a second master server to obtain additional numeric values when the number of values in its associated range is below a threshold. After receipt of the additional numeric values from the second master server, the first master server updates its associated range and assigns the additional numeric values to the clients.

Abstract: A database access server includes a network interface device and a processing device coupled to the network interface device via a bus. The network interface device receives a data request. The processing device retrieves data having a first data type. The processing device further reformats the retrieved data to create reformatted data having a second data type, and sends the reformatted data in response to the data request.

Abstract: A method and apparatus for searching data entries in a Lightweight Directory Access Protocol (LDAP) directory is described. At least a portion of an input is received from a user. Entries of a Lightweight Directory Access Protocol (LDAP) directory are searched to identify entries that contain the portion of the input from the user. Information pertaining to the identified entries is returned to the user, wherein the information pertaining to at least one identified entry does not include the portion of the input or a modification of the portion of the input.

Abstract: A method and apparatus for invoking actions on data in a Lightweight Directory Access Protocol (LDAP) repository. In one embodiment, the method includes receiving a request pertaining to data in the LDAP repository. The request indicates at least one action identified in the definition of the LDAP repository. The method further includes causing the action to be performed with respect to one or more data items in the LDAP repository.

Abstract: A method and system for automatic extension of a distributed numeric range in a multi-master system are described. In one embodiment, each of a plurality of master servers is provided with a unique range of numeric values that can be assigned to clients. Each master server can dynamically extend its associated range when the range is about to be exhausted. For example, a first master server can send a range request to a second master server to obtain additional numeric values when the number of values in its associated range is below a threshold. After receipt of the additional numeric values from the second master server, the first master server updates its associated range and assigns the additional numeric values to the clients.

Abstract: Techniques for improving the performance of a Lightweight Directory Access Protocol (“LDAP”) server are described. The server computes the priority of an LDAP request and enqueues it on a priority queue according to the priority. A high-priority LDAP request is removed from the queue to prepare a corresponding LDAP response. Systems and software to implement similar techniques are also described and claimed.

Abstract: A method and system of a distributing server that encapsulates a client package within a client software repository package. The client software repository package contains at least a portion of a client repository. The client repository is installed at the subscribing server and is associated with one or more clients that are not authorized to access the distributing server. The distributing server transmits the client software repository package to a subscribing server that is authorized to access the distributing server. The subscribing server then serves the client package to the clients through the client repository.

Abstract: A database access server includes a network interface device and a processing device coupled to the network interface device via a bus. The network interface device receives a data request that includes a data identifier. The processing device retrieves data having the data identifier. The processing device determines if the retrieved data is compressed. The processing device decompresses the retrieved data if the retrieved data is compressed. The processing device sends the uncompressed retrieved data in response to the data request.

Abstract: A method and apparatus for selective chaining Light Weight Directory Access Protocol (LDAP) servers in response to an LDAP request. In one embodiment, the method comprises receiving, at a directory server, a request pertaining to an LDAP entry, the request indicating a read or write operation for the LDAP entry. The method further determining a destination server based on a forwarding policy that is independent of a suffix of the LDAP entry and the read or write operation. The directory server then forwards the request to the destination server.

Abstract: A method and apparatus for indexing attribute subtypes for Light Weight Directory Access Protocol (LDAP) entries. In one embodiment, the method includes receiving a query specifying a search criterion for a subtype of a base attribute. The base attribute and the subtype are associated with LDAP entries. The method also includes determining a response to the query by looking up a subtype index that points to the LDAP entries having a presence of the subtype.

Abstract: The present invention allows Red Hat Package Manager (RPM) systems to work with non-RPM packages. In particular, the present invention provides for installing an RPM subsystem on a system that has its own native packaging subsystem. The RPM subsystem is initially delivered as a package wrapped in the non-RPM format of the native packaging system and installed. An administrator may then install RPM packages using the RPM tools of the RPM subsystem. When an RPM package is installed, the RPM subsystem is also configured to create a stub entry in the native packaging, non-RPM system. The stub entry may contain the normal package information, such as name, version, description, as well as a list of files contained in a package. The stub may also contain uninstallation logic, which serves as a “callback” into the RPM subsystem during package removal and causes the RPM subsystem to remove the package when invoked. Removal of a RPM package via RPM tools also causes the removal of the stub entry.