Exposing file metadata as LDAP attributes

US9722967B2 · US · B2

Patent metadata
FieldValue
Publication numberUS-9722967-B2
Application numberUS-201213663387-A
CountryUS
Kind codeB2
Filing dateOct 29, 2012
Priority dateAug 31, 2006
Publication dateAug 1, 2017
Grant dateAug 1, 2017

How to read this patent

A practical reading order for non-experts. Skip the full description unless you need deep technical detail.

  1. Title

    What the patent document calls the invention.

  2. Abstract

    A short plain-language summary of the technical disclosure.

  3. Assignees and inventors

    Who owns or filed the patent and who is credited as inventor.

  4. Key dates

    Filing, priority, publication, and grant dates set the timeline.

  5. First independent claim

    The legal scope of protection — read this for what is actually claimed.

  6. CPC / IPC classifications

    Technology tags used to group this patent with similar filings.

  7. Citations and related patents

    Prior art links and similar publications in this corpus.

Abstract

Official abstract text for this publication.

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.

First claim

Opening claim text (preview).

What is claimed is: 1. A computer-implemented method comprising: receiving, by a processor of a directory server, a first request from a client computer via network, the first request specifying a first attribute of a plurality of attributes, first attribute subtype and a first attribute subtype value, and the first attribute having a first data type of a plurality of data types; determining by the processor of the directory server an index for the first attribute does not exist; if the index for the first attribute does not exist, invoking by the processor, in response to the first request, a first plugin of a plurality of plugins coupled to the directory server, wherein the first plugin corresponds to the first data type, wherein the first plugin identifies first metadata that has a first format corresponding to the first data type, wherein the first format of the first metadata comprises a first property, and wherein the first metadata comprises a value of the first property and wherein the invoking of the first plugin comprises passing a first parameter to the first plugin; receiving from the first plugin, a first entry in a repository of the directory server, wherein the first entry matches the first parameter; and providing to the client computer, the first entry including the first attribute subtype and the first attribute subtype value; receiving, by the processor, a second request from the client computer via the network, the second request specifying a second attribute of the plurality of attributes that is different than the first attribute, a second attribute subtype and a second attribute subtype value, and the second attribute having a second data type of the plurality of data types that is different than the first data type; determining by the processor of the directory server an index for the second attribute does not exist; if the index for the second attribute does not exist, invoking by the processor, in response to the second request, a second plugin of the plurality of plugins that is different than the first plugin, wherein the second plugin corresponds to the second data type, and wherein the second plugin identifies second metadata that has a second format corresponding to the second data type, and wherein the second format of the second metadata lacks the first property, and wherein the invoking of the second plugin comprises passing a second parameter to the second plugin; and, receiving from the second plugin, a second entry in the repository of the directory server, wherein the second entry matches the second parameter; and providing to the client computer, the second entry including the second attribute subtype and the second attribute subtype value. 2. The method of claim 1 wherein the first data type is one of a text document type, a binary document type, an image type, a photo type, an audio type, or a video type. 3. The method of claim 1 further comprising creating an attribute subtype in the repository. 4. The method of claim 1 , further comprising providing the first attribute subtype as a virtual attribute. 5. The method of claim 1 , wherein the directory server is a Lightweight Directory Access Protocol (LDAP) server. 6. A directory server comprising: a memory to store a plurality of data types; and a processor operatively coupled to the memory, to: receive, from a client computer via network, a first request that specifies a first attribute of a plurality of attributes, a first attribute subtype and a first attribute subtype value, and the first attribute having a first data type of a plurality of data types; determine an index for the first attribute does not exist; invoke, in response to the first request, a first plugin of a plurality of plugins coupled to the directory server if the index for the first attribute does not exist, wherein the first plugin corresponds to the first data type, wherein the first plugin identifies first metadata that has a first format corresponding to the first data type, wherein the first format of the first metadata comprises a first property, and wherein the first metadata comprises a value of the first property and wherein the invoking of the first plugin comprises passing a first parameter to the first plugin; receive from the first plugin, a first entry in a repository of the directory server, wherein the first entry matches the first parameter; and provide to the client computer, the first entry including the first attribute subtype and the first attribute subtype value; receive a second request from the client computer via the network, the second request specifying a second attribute of the plurality of attributes that is different than the first attribute, a second attribute subtype and a second attribute subtype value, and the second attribute having a second data type of the plurality of data types that is different than the first data type; determine an index for the second attribute does not exist; invoke, in response to the second request, a second plugin of the plurality of plugins that is different than the first plugin if the index for the first attribute does not exist, wherein the second plugin corresponds to the second data type, and wherein the second plugin identifies second metadata that has a second format corresponding to the second data type, and wherein the second format of the second metadata lacks the first property, and wherein the invoking of the second plugin comprises passing a second parameter to the second plugin; and, receive from the second plugin, a second entry in the repository of the directory server, wherein the second entry matches the second parameter; and provide to the client computer, the second entry including the second attribute subtype and the second attribute subtype value. 7. The directory server of claim 6 wherein the first data type is one of a text document type, a binary document type, an image type, a photo type, an audio type, or a video type. 8. The directory server of claim 6 wherein the processor is further to create an attribute subtype in the repository. 9. The directory server of claim 6 , wherein the processor is further to provide the first attribute subtype as a virtual attribute. 10. The directory server of claim 6 , wherein the directory server is a Lightweight Directory Access Protocol (LDAP) server. 11. A non-transitory computer-readable storage medium having instructions stored therein that, when executed by a processor of a directory server, cause the processor to: receive a first request from a client computer via network, the first request specifying a first attribute of a plurality of attributes, a first attribute subtype and a first attribute subtype value, and the first attribute having a first data type of a plurality of data types; determine an index for the first attribute does not exist; invoke, in response to the first request, a first plugin of a plurality of plugins coupled to the directory server if the index for the first attribute does not exist, wherein the first plugin corresponds to the first data type, wherein the first plugin identifies first metadata that has a first format corresponding to the first data type, wherein the first format of the first metadata comprises a first property, and wherein the first metadata comprises a value of the first property and wherein the invoking of the first plugin comprises passing a first parameter to the first plugin; receive from the first plugin, a first entry in a repository of the directory server, wherein the first entry matches the first parameter; and providing to the client computer, the first entry including the first attribute subtype and the first attribute subtype value; rece

Assignees

Inventors

Classifications

  • Electricity · mapped topic

  • Electricity · mapped topic

  • Electricity · mapped topic

  • using lightweight directory access protocol [LDAP] · CPC title

  • Lookup mechanisms between a plurality of directories; Synchronisation of directories, e.g. metadirectories · CPC title

Patent family

Related publications grouped by family.

External sources

Frequently asked questions

Answers are generated from the same data shown on this page.

What does patent US9722967B2 cover?
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…
Who is the assignee on this patent?
Red Hat Inc
What technology area does this patent fall under?
Primary CPC classification H04L61/1523. Mapped technology areas include Electricity.
When was this patent published?
Publication date Tue Aug 01 2017 00:00:00 GMT+0000 (Coordinated Universal Time) (B2). Legal status and post-grant events are not shown on this page.
What related patents are in patentsdb?
We list 8 related publications on this page (citations in our corpus or others sharing the same primary CPC).