CN109344159B - Lookup method and device for LDAP (lightweight directory Access protocol), electronic equipment and storage medium - Google Patents
Lookup method and device for LDAP (lightweight directory Access protocol), electronic equipment and storage medium Download PDFInfo
- Publication number
- CN109344159B CN109344159B CN201811196888.5A CN201811196888A CN109344159B CN 109344159 B CN109344159 B CN 109344159B CN 201811196888 A CN201811196888 A CN 201811196888A CN 109344159 B CN109344159 B CN 109344159B
- Authority
- CN
- China
- Prior art keywords
- index
- ldap
- searched
- user
- tree structure
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 25
- 238000004891 communication Methods 0.000 abstract description 7
- 238000010586 diagram Methods 0.000 description 7
- 230000006870 function Effects 0.000 description 4
- 230000008520 organization Effects 0.000 description 2
- 230000001133 acceleration Effects 0.000 description 1
- 238000007792 addition Methods 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 238000005516 engineering process Methods 0.000 description 1
- 238000012986 modification Methods 0.000 description 1
- 230000004048 modification Effects 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000003909 pattern recognition Methods 0.000 description 1
- 238000006467 substitution reaction Methods 0.000 description 1
- 230000000007 visual effect Effects 0.000 description 1
Images
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a lookup method and device for LDAP, electronic equipment and a storage medium, and relates to the technical field of communication. The lookup method for the LDAP comprises the following steps: establishing an index corresponding to the tree structure; acquiring a target OU attribute value in the index according to the user name RDN to be searched; obtaining the DN of the user name to be searched according to the search user name RDN and the target OU attribute value; and searching the user to be searched in the tree structure according to the DN of the user name to be searched. The method achieves the purpose of greatly improving the efficiency of accurately searching the users under the condition that the LDAP stores a large number of users.
Description
Technical Field
The present disclosure relates to the field of communications technologies, and in particular, to a lookup method and apparatus for LDAP, an electronic device, and a storage medium.
Background
Ldap (lightweight Directory Access protocol) is a lightweight Directory Access protocol. The LDAP directory stores data by using a tree structure, and is suitable for the situation that user information is stored once and inquired for many times. The related information of the characteristics of an organization structure can be effectively and definitely described. LDAP directories are special databases, different from relational databases, and are not, strictly speaking, databases but protocols for accessing information stored in information directories. The entry of LDAP is the basic object of LDAP processing.
Disclosure of Invention
In the prior art, LDAP search is to give a search node (under which node to search), a search range and a filter condition to traverse and search nodes meeting the condition. Under the condition of a tree structure, traversal search is needed, and when the data volume is large, the efficiency of accurately searching user information is low.
In view of the above, the present disclosure provides a lookup method, apparatus, electronic device and storage medium for LDAP, which at least partially solve the problems in the prior art.
In a first aspect, the present disclosure provides a lookup method for LDAP, including: establishing an index corresponding to the tree structure; acquiring a target OU attribute value in the index according to the user name RDN to be searched; obtaining the DN of the user name to be searched according to the search user name RDN and the target OU attribute value; and searching the user to be searched in the tree structure according to the DN of the user name to be searched.
As a specific implementation manner of the embodiment of the present disclosure, the index is a planar structure in which all user nodes are under the same node.
As a specific implementation manner of the embodiment of the present disclosure, the obtaining a DN of a user name to be searched according to a search user name RDN and the target OU attribute value specifically includes: and splicing the RDN of the user name to be searched with the attribute value of the target OU so as to obtain the DN of the user name to be searched.
As a specific implementation manner of the embodiment of the present disclosure, the establishing an index corresponding to a tree structure includes: acquiring a user node in a tree structure; and establishing an index, so that the user nodes in the index correspond to the user nodes in the tree structure one to one.
As a specific implementation manner of the embodiment of the present disclosure, the establishing an index corresponding to a tree structure further includes: when the user nodes are added and deleted in the tree structure, the corresponding user nodes are added and deleted in the index.
As a specific implementation manner of the embodiment of the present disclosure, the index stores RDN and OU attribute values that are consistent with the user nodes in the tree structure.
As a specific implementation manner of the embodiment of the present disclosure, a part in the RDN and a part in the OU attribute value that are consistent with the user node in the tree structure are stored in the index.
In a second aspect, the present disclosure further provides a lookup apparatus for LDAP, including: an index establishing module: used for building an index corresponding to the tree structure; an OU acquisition module: the index is used for acquiring a target OU attribute value in the index according to the user name RDN to be searched; a DN acquisition module: the DN is used for obtaining the DN of the user name to be searched according to the search user name RDN and the target OU attribute value; a searching module: and searching the user to be searched in the tree structure according to the DN of the user name to be searched.
In a third aspect, the present disclosure also provides an electronic device, including: at least one processor; and a memory communicatively coupled to the at least one processor; wherein the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the lookup method for LDAP of any of the first aspects.
In a fourth aspect, the disclosed embodiments also provide a non-transitory computer-readable storage medium storing computer instructions for causing a computer to perform the lookup method for LDAP as claimed in any one of the first aspects.
The embodiment of the disclosure provides an image deformation method, an image deformation device, an electronic device and a non-transitory computer readable storage medium, wherein the method for searching LDAP comprises the following steps: the index corresponding to the tree structure is established, the target OU attribute value is obtained from the index, the DN of the user name to be searched is obtained according to the search user name RDN and the target OU attribute value, then the accurate searching is carried out in the tree structure according to the DN of the search user name, and the efficiency of obtaining the target OU attribute value in the index is high, so that the purpose of greatly improving the efficiency of accurately searching the user is achieved under the condition that a large number of users are stored by LDAP.
Drawings
Fig. 1 is a flowchart of a lookup method for LDAP according to an embodiment of the present disclosure;
FIG. 2 is a schematic block diagram of a lookup apparatus for LDAP according to an embodiment of the present disclosure;
fig. 3 is a functional block diagram of an electronic device provided by an embodiment of the present disclosure;
FIG. 4 is a schematic diagram of a computer-readable storage medium provided by an embodiment of the present disclosure;
fig. 5 is a schematic block diagram of a terminal according to an embodiment of the present disclosure.
Detailed Description
In order to solve the problems in the prior art, the present invention provides a lookup method, apparatus, electronic device and storage medium for LDAP, and the present invention is described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the invention and do not limit the invention.
In the following description, specific details are provided to provide a thorough understanding of the examples. However, it will be understood by those skilled in the art that the aspects may be practiced without these specific details.
LDAP: lightweight Directory Access Protocol.
DN: unique distinguished names in all entries in an LDAP directory. DN consists of two parts: relative dn (rdn) and location in the LDAP directory.
RDN: in contrast to the DN, a node is a unique distinguishable name under the parent node.
OU: the name of the organization unit, and the location of the record node in the LDAP directory tree structure.
Tree structure: the user nodes are respectively under different nodes (the father nodes are not consistent) so as to be convenient for management.
And (3) plane structure: all user nodes are under the same node (parent node consistent).
The first embodiment is as follows:
as shown in fig. 1, the present embodiment provides a lookup method for LDAP, including:
step S101: establishing an index corresponding to the tree structure;
preferably, the index is a planar structure with all user nodes under the same node.
The main role of the flat structure is to assist in performing the search in the case where the LDAP stores a large number of users.
Preferably, the creating of the index corresponding to the tree structure includes:
acquiring a user node in a tree structure;
and establishing an index, so that the user nodes in the index correspond to the user nodes in the tree structure one to one.
And establishing a plane structure, namely enabling user nodes in the tree structure under different nodes to correspond to the user nodes of the plane structure under the same node one by one.
Preferably, when a user node is added or deleted in the tree structure, the corresponding user node is added or deleted in the index. When a user node is newly added in the tree structure, the corresponding user node is added in the index, and when the user node is deleted in the tree structure, the corresponding node in the index is deleted.
Preferably, the index stores the RDN and OU attribute values consistent with the user nodes in the tree structure. The RDN and OU attribute values of the user nodes in the index are the same as those of the user nodes in the corresponding tree structure.
Preferably, the index stores the part in the RDN and the part in the OU attribute value consistent with the user node in the tree structure. The RDN and OU attribute values stored in the index are only part of the RDN and part of the OU attribute values of the user nodes in the tree structure, all of the RDN and all of the OU attribute values of the user nodes in the tree structure do not need to be stored, only the key parts which can be searched need to be stored, and if the RDN of the user nodes in the tree structure is composed of A + B and the OU attribute values are composed of C + D, only A and C need to be stored in the index.
Step S102: acquiring a target OU attribute value in the index according to the user name RDN to be searched;
the user name RDN is the only distinguishable name of the node under the father node, so the node has uniqueness, and the target user node corresponding to the RDN is found in the index according to the user name RDN to be searched, so that the target OU attribute value stored by the target user node can be obtained.
In a preferred embodiment, a target user node corresponding to a user name RDN to be searched is found in a planar structure according to the RDN, and a target OU attribute value stored by the target user node is acquired.
Step S103: obtaining the DN of the user name to be searched according to the search user name RDN and the target OU attribute value;
and splicing the user name RDN to be searched with the target OU attribute value to obtain the DN (DN is RDN + OU) of the user name to be searched.
Step S104: and searching the user to be searched in the tree structure according to the DN of the user name to be searched.
And accurately searching the user to be searched in the tree structure according to the DN of the user name to be searched.
Example two:
as shown in fig. 2, an embodiment of the present disclosure further provides a lookup apparatus for LDAP, including:
the index creation module 201: used for building an index corresponding to the tree structure;
preferably, the index is a planar structure with all user nodes under the same node.
The main role of the flat structure is to assist in performing the search in the case where the LDAP stores a large number of users.
And establishing a plane structure, namely enabling user nodes in the tree structure under different nodes to correspond to the user nodes of the plane structure under the same node one by one.
Preferably, when a user node is added or deleted in the tree structure, the corresponding user node is added or deleted in the index. When a user node is newly added in the tree structure, the corresponding user node is added in the index, and when the user node is deleted in the tree structure, the corresponding node in the index is deleted.
Preferably, the index stores the RDN and OU attribute values consistent with the user nodes in the tree structure. The RDN and OU attribute values of the user nodes in the index are the same as those of the user nodes in the corresponding tree structure.
Preferably, the index stores the part in the RDN and the part in the OU attribute value consistent with the user node in the tree structure. The RDN and OU attribute values stored in the index are only part of the RDN and part of the OU attribute values of the user nodes in the tree structure, all of the RDN and all of the OU attribute values of the user nodes in the tree structure do not need to be stored, only the key parts which can be searched need to be stored, and if the RDN of the user nodes in the tree structure is composed of A + B and the OU attribute values are composed of C + D, only A and C need to be stored in the index.
The OU acquisition module 202: the index is used for acquiring a target OU attribute value in the index according to the user name RDN to be searched;
the user name RDN is the only distinguishable name of the node under the father node, so the node has uniqueness, and the target user node corresponding to the RDN is found in the index according to the user name RDN to be searched, so that the target OU attribute value stored by the target user node can be obtained.
In a preferred embodiment, a target user node corresponding to a user name RDN to be searched is found in a planar structure according to the RDN, and a target OU attribute value stored by the target user node is acquired.
DN acquisition module 203: the DN is used for obtaining the DN of the user name to be searched according to the search user name RDN and the target OU attribute value;
and splicing the user name RDN to be searched with the target OU attribute value to obtain the DN (DN is RDN + OU) of the user name to be searched.
The search module 204: and searching the user to be searched in the tree structure according to the DN of the user name to be searched.
And accurately searching the user to be searched in the tree structure according to the DN of the user name to be searched.
Example three:
fig. 3 is a hardware block diagram illustrating an electronic device according to an embodiment of the present disclosure. As shown in fig. 3, an electronic device 30 according to an embodiment of the present disclosure includes a memory 31 and a processor 32.
The memory 31 is used to store non-transitory computer readable instructions. In particular, memory 31 may include one or more computer program products that may include various forms of computer-readable storage media, such as volatile memory and/or non-volatile memory. The volatile memory may include, for example, Random Access Memory (RAM), cache memory (cache), and/or the like. The non-volatile memory may include, for example, Read Only Memory (ROM), hard disk, flash memory, etc.
The processor 32 may be a Central Processing Unit (CPU) or other form of processing unit having data processing capabilities and/or instruction execution capabilities, and may control other components in the electronic device 30 to perform desired functions. In one embodiment of the present disclosure, the processor 32 is configured to execute the computer readable instructions stored in the memory 31, so that the electronic device 30 performs all or part of the aforementioned steps for lookup of LDAP according to the embodiments of the present disclosure.
Those skilled in the art should understand that, in order to solve the technical problem of how to obtain a good user experience, the present embodiment may also include well-known structures such as a communication bus, an interface, and the like, and these well-known structures should also be included in the protection scope of the present disclosure.
For the detailed description of the present embodiment, reference may be made to the corresponding descriptions in the foregoing embodiments, which are not repeated herein.
Example four:
fig. 4 is a schematic diagram illustrating a computer-readable storage medium according to an embodiment of the present disclosure. As shown in fig. 4, a computer-readable storage medium 40, having non-transitory computer-readable instructions 41 stored thereon, in accordance with an embodiment of the present disclosure. The non-transitory computer readable instructions 41, when executed by a processor, perform all or a portion of the steps of the lookup for LDAP of the embodiments of the present disclosure previously described.
The computer-readable storage medium 40 includes, but is not limited to: optical storage media (e.g., CD-ROMs and DVDs), magneto-optical storage media (e.g., MOs), magnetic storage media (e.g., magnetic tapes or removable disks), media with built-in rewritable non-volatile memory (e.g., memory cards), and media with built-in ROMs (e.g., ROM cartridges).
For the detailed description of the present embodiment, reference may be made to the corresponding descriptions in the foregoing embodiments, which are not repeated herein.
Example five:
fig. 5 is a diagram illustrating a hardware structure of a terminal device according to an embodiment of the present disclosure. As shown in fig. 5, the terminal 50 includes the above-described embodiment of the lookup apparatus for LDAP.
The terminal device may be implemented in various forms, and the terminal device in the present disclosure may include, but is not limited to, mobile terminal devices such as a mobile phone, a smart phone, a notebook computer, a digital broadcast receiver, a PDA (personal digital assistant), a PAD (tablet computer), a PMP (portable multimedia player), a navigation apparatus, a vehicle-mounted terminal device, a vehicle-mounted display terminal, a vehicle-mounted electronic rear view mirror, and the like, and fixed terminal devices such as a digital TV, a desktop computer, and the like.
The terminal 50 may also include other components as an equivalent alternative embodiment. As shown in fig. 5, the terminal 50 may include a power supply unit 51, a wireless communication unit 52, an a/V (audio/video) input unit 53, a user input unit 54, a sensing unit 55, an interface unit 56, a controller 57, an output unit 58, a storage unit 59, and the like. Fig. 5 shows a terminal having various components, but it is to be understood that not all of the shown components are required to be implemented, and that more or fewer components may alternatively be implemented.
The wireless communication unit 52 allows, among other things, radio communication between the terminal 50 and a wireless communication system or network. The a/V input unit 53 is for receiving an audio or video signal. The user input unit 54 may generate key input data to control various operations of the terminal device according to a command input by a user. The sensing unit 55 detects a current state of the terminal 50, a position of the terminal 50, presence or absence of a touch input of the terminal 50 by a user, an orientation of the terminal 50, acceleration or deceleration movement and direction of the terminal 50, and the like, and generates a command or signal for controlling an operation of the terminal 50. The interface unit 56 serves as an interface through which at least one external device is connected to the terminal 50. The output unit 58 is configured to provide output signals in a visual, audio, and/or tactile manner. The storage unit 59 may store software programs or the like for processing and controlling operations performed by the controller 57, or may temporarily store data that has been output or is to be output. The storage unit 59 may include at least one type of storage medium. Also, the terminal 50 may cooperate with a network storage device that performs a storage function of the storage unit 59 through a network connection. The controller 57 generally controls the overall operation of the terminal device. In addition, the controller 57 may include a multimedia module for reproducing or playing back multimedia data. The controller 57 may perform a pattern recognition process to recognize a handwriting input or a picture drawing input performed on the touch screen as a character or an image. The power supply unit 51 receives external power or internal power and supplies appropriate power required to operate the respective elements and components under the control of the controller 57.
The various embodiments presented in this disclosure for lookup of LDAP may be implemented using a computer-readable medium, such as computer software, hardware, or any combination thereof. For a hardware implementation, the various embodiments of lookup for LDAP presented by the present disclosure may be implemented using at least one of an Application Specific Integrated Circuit (ASIC), a Digital Signal Processor (DSP), a Digital Signal Processing Device (DSPD), a Programmable Logic Device (PLD), a Field Programmable Gate Array (FPGA), a processor, a controller, a microcontroller, a microprocessor, an electronic unit designed to perform the functions described herein, and in some cases, the various embodiments of lookup for LDAP presented by the present disclosure may be implemented in the controller 57. With respect to software implementations, the various embodiments presented in this disclosure for lookup of LDAP may be implemented with separate software modules that allow for performing at least one function or operation. The software codes may be implemented by software applications (or programs) written in any suitable programming language, which may be stored in the storage unit 59 and executed by the controller 57.
Although the preferred embodiments of the present invention have been disclosed for illustrative purposes, those skilled in the art will appreciate that various modifications, additions and substitutions are possible, and the scope of the invention should not be limited to the embodiments described above.
Claims (10)
1. A lookup method for LDAP comprising:
establishing an index corresponding to the tree structure;
acquiring a target OU attribute value in the index according to the user name RDN to be searched;
obtaining the DN of the user name to be searched according to the search user name RDN and the target OU attribute value;
and searching the user to be searched in the tree structure according to the DN of the user name to be searched.
2. The lookup method for LDAP as claimed in claim 1 wherein said index is a flat structure with all user nodes under the same node.
3. The lookup method for LDAP according to claim 1, where the obtaining of the DN of the username to be searched according to the search username RDN and the target OU attribute value specifically includes:
and splicing the RDN of the user name to be searched with the attribute value of the target OU so as to obtain the DN of the user name to be searched.
4. The lookup method for LDAP according to claim 1, 2 or 3, wherein said establishing an index corresponding to a tree structure comprises:
acquiring a user node in a tree structure;
and establishing an index, so that the user nodes in the index correspond to the user nodes in the tree structure one to one.
5. The lookup method for LDAP according to claim 4, wherein said building an index corresponding to a tree structure further comprises:
when the user nodes are added and deleted in the tree structure, the corresponding user nodes are added and deleted in the index.
6. The lookup method for LDAP as claimed in claim 4 wherein RDN and OU attribute values consistent with user nodes in said tree structure are stored in said index.
7. The lookup method for LDAP according to claim 4 wherein parts in RDN and parts in OU attribute values that are consistent with user nodes in said tree structure are stored in said index.
8. A lookup apparatus for LDAP, comprising:
an index establishing module: used for building an index corresponding to the tree structure;
an OU acquisition module: the index is used for acquiring a target OU attribute value in the index according to the user name RDN to be searched;
a DN acquisition module: the DN is used for obtaining the DN of the user name to be searched according to the search user name RDN and the target OU attribute value;
a searching module: and searching the user to be searched in the tree structure according to the DN of the user name to be searched.
9. An electronic device, characterized in that the electronic device comprises:
at least one processor; and the number of the first and second groups,
a memory communicatively coupled to the at least one processor; wherein,
the memory stores instructions executable by the at least one processor to enable the at least one processor to perform the lookup method for LDAP as claimed in any one of claims 1 to 7.
10. A non-transitory computer readable storage medium storing computer instructions for causing a computer to perform the lookup method for LDAP according to any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811196888.5A CN109344159B (en) | 2018-10-15 | 2018-10-15 | Lookup method and device for LDAP (lightweight directory Access protocol), electronic equipment and storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811196888.5A CN109344159B (en) | 2018-10-15 | 2018-10-15 | Lookup method and device for LDAP (lightweight directory Access protocol), electronic equipment and storage medium |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109344159A CN109344159A (en) | 2019-02-15 |
| CN109344159B true CN109344159B (en) | 2022-03-11 |
Family
ID=65310178
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811196888.5A Active CN109344159B (en) | 2018-10-15 | 2018-10-15 | Lookup method and device for LDAP (lightweight directory Access protocol), electronic equipment and storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109344159B (en) |
Families Citing this family (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115858551B (en) * | 2023-01-31 | 2023-11-14 | 天津南大通用数据技术股份有限公司 | Memory management method, device, equipment and storage medium based on LDAP |
Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6408306B1 (en) * | 1999-12-14 | 2002-06-18 | International Business Machines Corporation | Method and system for automated distinguished name lookup |
| CN101232515A (en) * | 2008-02-25 | 2008-07-30 | 浪潮电子信息产业股份有限公司 | Distributed type colony management control system based on LDAP |
| CN101482873A (en) * | 2008-12-18 | 2009-07-15 | 华为技术有限公司 | Method and device for data access |
| CN101707522A (en) * | 2009-09-29 | 2010-05-12 | 北京星网锐捷网络技术有限公司 | Method and system for authentication and connection |
| CN102073644A (en) * | 2009-11-19 | 2011-05-25 | 华为技术有限公司 | Method for querying database, server and system |
| CN102279853A (en) * | 2010-06-12 | 2011-12-14 | 陈健华 | Rapid data access method based on LDAP (Lightweight Directory Access Protocol) |
| CN103714080A (en) * | 2012-09-29 | 2014-04-09 | 北京百度网讯科技有限公司 | Spatial index structure tree based method and device for providing results of searching spatial objects |
| CN107103034A (en) * | 2017-03-22 | 2017-08-29 | 南京理工大学 | TFAS data directory information method of servicing based on LDAP |
Family Cites Families (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6983269B2 (en) * | 2000-12-19 | 2006-01-03 | International Business Machines Corporation | Apparatus for indirect directory searches and method therefor |
| US7020662B2 (en) * | 2001-05-29 | 2006-03-28 | Sun Microsystems, Inc. | Method and system for determining a directory entry's class of service based on the value of a specifier in the entry |
| US7188094B2 (en) * | 2002-07-08 | 2007-03-06 | Sun Microsystems, Inc. | Indexing virtual attributes in a directory server system |
| US8160998B2 (en) * | 2004-06-04 | 2012-04-17 | Vitalsource Technologies, Inc. | System, method and computer program product for providing content based upon a representation of the same |
| US7672935B2 (en) * | 2006-11-29 | 2010-03-02 | Red Hat, Inc. | Automatic index creation based on unindexed search evaluation |
| CN103902700A (en) * | 2014-04-01 | 2014-07-02 | 浙江大学 | Tree structure data processing method |
-
2018
- 2018-10-15 CN CN201811196888.5A patent/CN109344159B/en active Active
Patent Citations (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US6408306B1 (en) * | 1999-12-14 | 2002-06-18 | International Business Machines Corporation | Method and system for automated distinguished name lookup |
| CN101232515A (en) * | 2008-02-25 | 2008-07-30 | 浪潮电子信息产业股份有限公司 | Distributed type colony management control system based on LDAP |
| CN101482873A (en) * | 2008-12-18 | 2009-07-15 | 华为技术有限公司 | Method and device for data access |
| CN101707522A (en) * | 2009-09-29 | 2010-05-12 | 北京星网锐捷网络技术有限公司 | Method and system for authentication and connection |
| CN102073644A (en) * | 2009-11-19 | 2011-05-25 | 华为技术有限公司 | Method for querying database, server and system |
| CN102279853A (en) * | 2010-06-12 | 2011-12-14 | 陈健华 | Rapid data access method based on LDAP (Lightweight Directory Access Protocol) |
| CN103714080A (en) * | 2012-09-29 | 2014-04-09 | 北京百度网讯科技有限公司 | Spatial index structure tree based method and device for providing results of searching spatial objects |
| CN107103034A (en) * | 2017-03-22 | 2017-08-29 | 南京理工大学 | TFAS data directory information method of servicing based on LDAP |
Non-Patent Citations (2)
| Title |
|---|
| "LDAP-based authentication for Samba";Robertson K.;《ibm developerWorks》;20061231;第1-32页 * |
| "基于LDAP的高可用目录服务器的设计与实现";王松;《软件》;20151231;第1-4页 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109344159A (en) | 2019-02-15 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10739958B2 (en) | Method and device for executing application using icon associated with application metadata | |
| EP3066816B1 (en) | Method and device for the management of applications | |
| CN109471838B (en) | Directory document operation method and device, electronic equipment and readable storage medium | |
| CN114090575A (en) | Data storage method and retrieval method based on key value database and corresponding devices | |
| US20190057072A1 (en) | Method, device and electronic equipment for switching name of desktop icon folder | |
| US20160092441A1 (en) | File Acquiring Method and Device | |
| US11455117B2 (en) | Data reading method, apparatus, and system, avoiding version rollback issues in distributed system | |
| CN105574211A (en) | File querying system and method based on time axis | |
| CN114546460A (en) | Firmware upgrading method and device, electronic equipment and storage medium | |
| CN113301203A (en) | Method and device for updating historical information data based on address book | |
| CN112235433A (en) | Domain name access method and device | |
| CN109344159B (en) | Lookup method and device for LDAP (lightweight directory Access protocol), electronic equipment and storage medium | |
| CN108874495B (en) | Theme resource conversion method and device and electronic equipment | |
| CN114817657A (en) | To-be-retrieved data processing method, data retrieval method, electronic device and medium | |
| CN112559913B (en) | Data processing method, device, computing equipment and readable storage medium | |
| CN112487009B (en) | Data updating method, device, equipment, storage medium and program product | |
| WO2019228009A1 (en) | Lsm tree optimization method and device and computer equipment | |
| CN117056383A (en) | Searching method and electronic equipment | |
| CN110019863B (en) | Object searching method and device, terminal equipment and storage medium | |
| CN117472852A (en) | Log data query method, device, equipment and medium | |
| CN113918246B (en) | Function control method, function control device, storage medium, and electronic apparatus | |
| CN111352993A (en) | Cross-platform data synchronization method and device and electronic equipment | |
| CN112100132B (en) | Deleted file type identification method and device, electronic equipment and storage medium | |
| CN114154031A (en) | Paging display method, device, equipment and storage medium for tree-shaped folding table | |
| CN113707145A (en) | Display device and voice search method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |