LDAP user interaction method, device and medium based on IPPBX

By authenticating and synchronizing the LDAP server in the IPPBX system, the problem of connecting IPPBX and LDAP servers is solved, and the interaction and information synchronization of LDAP users in the IPPBX system is realized, and the single sign-in and call functions are realized.

CN118573777BActive Publication Date: 2024-11-15XIAMEN XINGZONG DIGITAL TECH CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411016705.2
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2024-07-29
Publication Date
2024-11-15
Estimated Expiration
2044-07-29

AI Technical Summary

Technical Problem

No technical solution to connect IPPBX with LDAP servers has been found in the prior art, which has resulted in the inability of LDAP users to effectively interact and synchronize information in the IPPBX system.

Method used

The IPPBX administrator inputs configuration information and sends an authentication request to the LDAP server, obtains the structure information and user information of the group or organization, and binds the extension number based on the extracted attribute field content, so as to realize the binding between the LDAP user and the IPPBX extension, allowing LDAP to be allowed Users interact with other users in the same group or organization.

Benefits of technology

It realizes that LDAP users can view and call other user information in the same group or organization after logging in to IPPBX, and realizes single sign-in and information synchronization.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN118573777B_ABST
    Figure CN118573777B_ABST
Patent Text Reader

Abstract

The present invention relates to an LDAP user interaction method, device and medium based on IPPBX, the method comprising: sending an identity authentication request to an LDAP server, obtaining the structure information and user information of the group or organization to be synchronized from the LDAP server after the identity authentication request is passed; after obtaining the user information, extracting the corresponding content from the user information based on the configured attribute field, and binding the extension with the extracted content as the extension number to the corresponding LDAP user; after the LDAP user logs in to the bound IPPBX extension, he can interact with other users in his group or organization. The present invention can view the user information of other users in the same group or organization through IPPBX, and make calls through the extension.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of communication technology, and in particular to an LDAP user interaction method, device and medium based on IPPBX. Background Art

[0002] IPPBX is an enterprise telephone system based on Internet protocol. It can integrate multiple communication methods and has new working methods such as remote office and mobile office. The full name of LDAP protocol is Lightweight Directory Access Protocol, and its predecessor is X.500. X.500 is a set of standards developed by the International Telecommunication Union (ITU-T) to describe the framework of directory services. Directory services are an information storage and retrieval system that can be used to store, organize and provide information about network resources and objects. These resources and objects can include users, organizations, devices and applications. At present, no technical solution has been found to use IPPBX for docking with LDAP servers. Summary of the invention

[0003] In order to solve the above problems, the present invention proposes an LDAP user interaction method, device and medium based on IPPBX.

[0004] The specific plan is as follows:

[0005] An LDAP user interaction method based on IPPBX includes the following steps:

[0006] The IPPBX sends an authentication request to the LDAP server based on the configuration information entered by the administrator for interfacing with the LDAP server. After the authentication is successful, the IPPBX obtains the structure information and user information of the group or organization that needs to be synchronized from the LDAP server.

[0007] After obtaining the user information, the IPPBX extracts the content of the corresponding attribute field from the user information based on the attribute field that needs to be used when the configured LDAP user binds the IPPBX extension, and binds the extension with the extracted content as the extension number to the corresponding LDAP user;

[0008] After an LDAP user logs in to the IPPBX extension to which he is bound, he can interact with other users in his group or organization.

[0009] Furthermore, the configuration information includes: LDAP server IP, transmission protocol, directory node, login account and login password.

[0010] Furthermore, the identity authentication request sent by IPPBX is bindRequest, which includes three fields, among which the first field is used to fill in the version of LDAP protocol; the second field is used to fill in the login account in the configuration information; the third field is used to fill in the authentication rule, and the login password in the configuration information is attached after the authentication rule.

[0011] Furthermore, when the identity authentication fails, the IPPBX searches for the corresponding failure reason based on the value of resultCode in the received bindResponse and displays it.

[0012] Furthermore, both the architecture information and the user information are obtained through SearchRequest;

[0013] When obtaining the organization's architecture information and user information, first obtain the organization's architecture information through SearchRequest, and then obtain the user information of each user contained in each node through SearchRequest based on the directory address of each node contained in the architecture information;

[0014] When obtaining the architecture information and user information of a group, first obtain the architecture information of the group through SearchRequest, and then obtain the user information of each user contained in each group through SearchRequest based on the directory address of each group contained in the architecture information.

[0015] Furthermore, when binding with the corresponding LDAP user, a search is performed based on the extracted content to determine whether the content exists in the locally stored extension number. If so, the found extension number is bound to the corresponding LDAP user; otherwise, an extension with the content as the extension number is created and bound to the corresponding LDAP user.

[0016] Furthermore, after the binding is completed, the user information of the LDAP user corresponding to each newly bound extension is stored.

[0017] Furthermore, there are two ways for LDAP users to log in to their bound IPPBX extensions. In method one, the account and password used for login are the bound extension number and the login password configured in the configuration file respectively; in method two, the account and password used for login are the account and password used by the user to log in to the LDAP server; when verification is performed through method two, an authentication request is generated based on the account and password and sent to the LDAP server, and the verification result returned by the LDAP server is used as the login result.

[0018] An LDAP user interaction terminal device based on IPPBX includes a processor, a memory, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the steps of the method described above in the embodiment of the present invention are implemented.

[0019] A computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the method described above in an embodiment of the present invention are implemented.

[0020] The present invention adopts the above technical solution. When an LDAP user logs in to the IPPBX, he can view the user information of other users in the same group or organization and talk with other users in the same group or organization through an extension. BRIEF DESCRIPTION OF THE DRAWINGS

[0021] Figure 1 Shown is a flow chart of a method according to a first embodiment of the present invention. DETAILED DESCRIPTION

[0022] To further illustrate various embodiments, the present invention provides drawings. These drawings are part of the disclosure of the present invention, which are mainly used to illustrate the embodiments and can be used in conjunction with the relevant descriptions in the specification to explain the operating principles of the embodiments. With reference to these contents, ordinary technicians in this field should be able to understand other possible implementations and advantages of the present invention.

[0023] The present invention will now be further described with reference to the accompanying drawings and specific implementation methods.

[0024] Embodiment 1:

[0025] The embodiment of the present invention provides an LDAP user interaction method based on IPPBX, such as Figure 1 As shown, the method comprises the following steps:

[0026] S1: The IPPBX sends an authentication request to the LDAP server based on the configuration information entered by the administrator for interfacing with the LDAP server. After the authentication is successful, the IPPBX obtains the schema information and user information of the group or organization that needs to be synchronized from the LDAP server.

[0027] The identity authentication request sent in this embodiment is a bindRequest. In this embodiment, an LDAP server docking button is constructed in the interface of the IPPBX. After the administrator user logs in to the IPPBX, by clicking the LDAP server docking button, a configuration interface for filling in configuration information pops up. After the administrator user completes and saves the information, the IPPBX constructs a bindRequest based on the filled in configuration information and sends it to the corresponding LDAP server.

[0028] In this embodiment, the configuration information set includes LDAP server IP, transmission protocol, directory node, login account and login password, where the LDAP server IP is used to identify the connected LDAP server; the transmission protocol includes LDAP and LDAPS, and the administrator user can choose one to fill in; the directory node is used to identify the starting point of the search; the login account and login password are used to log in to the LDAP server, and the administrator user needs to register in advance.

[0029] The bindRequest is a binding request, which is essentially an identity verification (that is, authentication) operation. The bindRequest constructed in this embodiment includes three fields. The first field is used to fill in the version of the LDAP protocol; the second field is used to fill in the login account in the configuration information; the third field is used to fill in the authentication rule. The authentication rules include SASL and SimpleAuthentication. You can choose any one of them in use. In addition, when filling in the authentication rule, you also need to attach the login password in the configuration information.

[0030] The LDAP server performs authentication based on the login account and login password in the received bindRequest, and returns a bindResponse after the authentication is completed.

[0031] The bindResponse includes two fields. The first field is resultCode, whose value indicates the authentication result. When the authentication is successful, resultCode=0; when the authentication fails, resultCode is not 0, and different values ​​correspond to different failure reasons; the second field is errorMessage, which is the failure reason (empty if successful).

[0032] The IPPBX saves the configuration information when the authentication is successful. By saving the configuration information, you do not need to configure it again the next time you connect to the LDAP server.

[0033] When the IPPBX fails to verify, it will display the reason for the failure. In this embodiment, the method of displaying the reason for the failure is: the IPPBX stores the mapping relationship between the resultCode value and the reason for the failure, and when the bindResponse is received, the mapped reason for the failure is searched based on the value of the resultCode and displayed. For example, resultCode=10 indicates that the login account is wrong.

[0034] When obtaining the schema information and user information of a synchronized group or organization from the LDAP server, you need to obtain the schema information first and then obtain the user information. Both the schema information and the user information are obtained through SearchRequest.

[0035] SearchRequest contains four fields. The first field is used to fill in the starting point of the search; the second field is used to fill in the search coverage; the third field is used to fill in the filtering conditions to filter out the entries that meet the conditions; and the fourth field is used to fill in the attribute information that needs to be returned.

[0036] The IPPBX first sends a SearchRequest to the LDAP server to search for the schema information of a group or organization.

[0037] When SearchRequest is used to obtain the organizational structure information, the starting point of the search is filled in with the directory node in the configuration information, and the filtering condition is filled in with (objectCategory=organizationalUnit). The attribute information that needs to be returned includes the directory address of each node in the organization (such as DN) and other custom node attribute information, such as the Chinese name, English name, ID, etc. of the node.

[0038] When SearchRequest is used to obtain the architectural information of a group, the starting point of the search is filled in with the directory node in the configuration information, and the filtering condition is filled in with (objectCategory=group). The attribute information that needs to be returned includes the directory address of each group in the organization (such as DN) and other custom attribute information, such as the Chinese name, English name, ID, etc. of the group.

[0039] The LDAP server searches for the schema information of the group or organization based on the received SearchRequest. After the search is completed, the LDAP server returns the schema information of the searched group or organization through SearchEntry, and returns SearchResDone when the search is completed to indicate the end of the response.

[0040] The IPPBX builds a complete group or organization structure based on the received SearchEntry and stores it to achieve synchronization of the group or organization structure.

[0041] After receiving the structure information of the group or organization, the IPPBX sends a SearchRequest to the LDAP server for searching the user information of the group or organization.

[0042] When SearchRequest is used to obtain user information of an organization, the starting point of the search is filled in with the directory address of the node contained in the returned SearchEntry; the filtering condition is filled in with (&(objectCategory=person)(objectClass=user)); the attribute information that needs to be returned includes customized user attribute information, such as the user's Chinese name, English name, extension number, etc.

[0043] When SearchRequest is used to obtain user information of a group, the directory node in the configuration information is filled in as the starting point of the search; the filtering condition is filled in as (&(&(objectCategory=person)(objectClass=user))(|(memberOf=CN=Administrators,CN=Builtin,DC=ymtest2012r2,DC=com))(memberOf=CN=Group Policy Creator Owners,CN=Users,DC=ymtest2012r2,DC=com))), where CN=Administrators,CN=Builtin,DC=ymtest2012r2,DC=com and CN=Group Policy CreatorOwners,CN=Users,DC=ymtest2012r2,DC=com belong to two groups; the attribute information that needs to be returned includes customized user attribute information, such as the user's Chinese name, English name, extension number, etc.

[0044] It should be noted that when obtaining the user information of an organization, the user information included in multiple nodes needs to be obtained through multiple SearchRequests; when obtaining the user information of a group, the user information included in all groups is obtained through only one SearchRequest.

[0045] Furthermore, after obtaining the structure information of the group or organization, the administrator user can select some groups or nodes therein to obtain user information as needed, instead of obtaining all of them.

[0046] In other embodiments, the administrator user can fill in the filtering conditions recognizable by the LDAP server to obtain user information as needed, such as configuring the filtering condition to be (&(objectCategory=person)(objectClass=user)) to synchronously search all users under the directory (i.e., the directory node in the configuration information).

[0047] S2: After obtaining the user information, the IPPBX extracts the content of the corresponding attribute field from the user information based on the attribute field that needs to be used when the configured LDAP user binds the IPPBX extension, and binds the extension with the extracted content as the extension number to the corresponding LDAP user.

[0048] The attribute field that needs to be used when the configured LDAP user binds to the IPPBX extension should contain the attribute information that needs to be returned when the SearchRequest is used to obtain the user information of the organization.

[0049] When binding, based on the extracted content, a search is performed to determine whether the content exists in the locally stored extension number. If so, the extension number is bound to the corresponding LDAP user. Otherwise, an extension number with the content as the extension number is created and bound to the corresponding LDAP user.

[0050] Furthermore, after the binding is completed, the present embodiment also includes storing user information of the LDAP user corresponding to each newly bound extension.

[0051] S3: After an LDAP user logs in to the IPPBX extension to which it is bound, he or she can interact with other users in his or her group or organization.

[0052] This embodiment provides two ways for LDAP users to log in to their bound IPPBX extensions. When logging in, you need to enter the account and password used for logging in in the IPPBX interface.

[0053] Method 1: The account uses the bound extension number, and the password uses the login password configured in the configuration file.

[0054] Method 2: The account and password used by the user to log in to the LDAP server.

[0055] When the IPPBX receives the account and password entered by the user, it first verifies through method 1, that is, verifies whether the extension number exists and verifies whether the password is the login password in the configuration file. If the verification is successful, you can directly log in to the bound extension and talk to other users in the group or organization through the bound extension. If the verification fails, it verifies through method 2 again, generates an authentication request based on the account and password and sends it to the LDAP server, and waits for the verification result returned by the LDAP server. When the verification result returned by the LDAP server is verification passed, it searches for the extension number bound to the LDAP and logs in. If the verification result returned by the LDAP server is verification failed, it reminds you that the account and password are wrong.

[0056] In this embodiment, IPPBX supports multiple terminals, such as Webclient (browser terminal of IPPBX), Linkus pc (computer terminal of IPPBX), Linkus mobile (mobile terminal of IPPBX), etc.

[0057] Through the method of this embodiment, the organizational structure and user information on the LDAP server can be displayed on the IPPBX. When an LDAP user logs in to the IPPBX, he can view the user information of other users in the same group or organization, and talk with other users in the same group or organization through an extension, thus realizing single sign-on.

[0058] Embodiment 2:

[0059] The present invention also provides an LDAP user interaction terminal device based on IPPBX, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the steps in the above method embodiment of the first embodiment of the present invention are implemented.

[0060] Further, as an executable solution, the LDAP user interaction terminal device implemented based on IPPBX can be a computing device such as a desktop computer, a notebook, a PDA, and a mobile phone. The LDAP user interaction terminal device implemented based on IPPBX can include, but is not limited to, a processor and a memory. Those skilled in the art can understand that the composition structure of the above-mentioned LDAP user interaction terminal device implemented based on IPPBX is only an example of the LDAP user interaction terminal device implemented based on IPPBX, and does not constitute a limitation on the LDAP user interaction terminal device implemented based on IPPBX. It can include more or less components than the above-mentioned components, or combine certain components, or different components. For example, the LDAP user interaction terminal device implemented based on IPPBX can also include input and output devices, network access devices, buses, etc., and the embodiments of the present invention do not limit this.

[0061] Further, as an executable solution, the processor may be a central processing unit (CPU) or other general-purpose processors. The general-purpose processor may be a microprocessor or any conventional processor, etc. The processor is the control center of the LDAP user interaction terminal device based on IPPBX, and uses various interfaces and lines to connect various parts of the entire LDAP user interaction terminal device based on IPPBX.

[0062] The memory can be used to store the computer program and / or module. The processor realizes various functions of the LDAP user interaction terminal device based on IPPBX by running or executing the computer program and / or module stored in the memory and calling the data stored in the memory. The memory can mainly include a program storage area and a data storage area, wherein the program storage area can store an operating system and at least one application required for a function; the data storage area can store data created according to the use of the mobile phone, etc. In addition, the memory can include a high-speed random access memory, and can also include a non-volatile memory, such as a hard disk, a memory, a plug-in hard disk, a smart memory card (Smart MediaCard, SMC), a secure digital (Secure Digital, SD) card, a flash card (Flash Card), at least one disk storage device, a flash memory device, or other volatile solid-state storage devices.

[0063] The present invention also provides a computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps of the above method in the embodiment of the present invention are implemented.

[0064] If the module / unit integrated in the LDAP user interaction terminal device based on IPPBX is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the present invention implements all or part of the processes in the above-mentioned embodiment method, and can also be completed by instructing the relevant hardware through a computer program. The computer program can be stored in a computer-readable storage medium. When the computer program is executed by the processor, the steps of the above-mentioned method embodiments can be implemented. Among them, the computer program includes computer program code, and the computer program code can be in source code form, object code form, executable file or some intermediate form. The computer-readable medium may include: any entity or device that can carry the computer program code, recording medium, U disk, mobile hard disk, disk, optical disk, computer memory, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory) and software distribution medium, etc.

[0065] Although the present invention has been specifically shown and described in conjunction with the preferred embodiments, it should be understood by those skilled in the art that various changes may be made to the present invention in form and details without departing from the spirit and scope of the present invention as defined by the appended claims, all of which are within the scope of protection of the present invention.

Claims

1. A LDAP user interaction method based on IPPBX. It is characterized in that The following steps are involved: The IPPBX sends an authentication request to the LDAP server based on the configuration information entered by the administrator for interfacing with the LDAP server. After the authentication is successful, the IPPBX obtains the structure information and user information of the group or organization that needs to be synchronized from the LDAP server. After obtaining the user information, the IPPBX extracts the content of the corresponding attribute field from the user information based on the attribute field that needs to be used when the configured LDAP user binds the IPPBX extension, and binds the extension with the extracted content as the extension number to the corresponding LDAP user; After an LDAP user logs in to the IPPBX extension to which he is bound, he can interact with other users in his group or organization.

2. The LDAP user interaction method based on IPPBX according to claim 1, Features: Configuration information includes: LDAP server IP, transmission protocol, directory node, login account and login password.

3. The LDAP user interaction method based on IPPBX according to claim 1, Features: The authentication request sent by IPPBX is bindRequest, which includes three fields. The first field is used to fill in the version of LDAP protocol; the second field is used to fill in the login account in the configuration information; the third field is used to fill in the authentication rule, and the login password in the configuration information is attached after the authentication rule.

4. The LDAP user interaction method based on IPPBX according to claim 1, Features: When the IPPBX fails in identity authentication, it searches for the corresponding failure reason based on the value of resultCode in the received bindResponse and displays it.

5. The LDAP user interaction method based on IPPBX according to claim 1, Features: Both architecture information and user information are obtained through SearchRequest; When obtaining the organization's architecture information and user information, first obtain the organization's architecture information through SearchRequest, and then obtain the user information of each user contained in each node through SearchRequest based on the directory address of each node contained in the architecture information; When obtaining the architecture information and user information of a group, first obtain the architecture information of the group through SearchRequest, and then obtain the user information of each user contained in each group through SearchRequest based on the directory address of each group contained in the architecture information.

6. The LDAP user interaction method based on IPPBX according to claim 1, Features: When binding with the corresponding LDAP user, based on the extracted content, it is searched whether the content exists in the locally stored extension number, and if so, the extension number found is bound to the corresponding LDAP user; Otherwise, create an extension with the content as the extension number and bind it to the corresponding LDAP user.

7. The LDAP user interaction method based on IPPBX according to claim 1, Features: After the binding is completed, the user information of the LDAP user corresponding to each newly bound extension is also stored.

8. The LDAP user interaction method based on IPPBX according to claim 1, Features: There are two ways for LDAP users to log in to their bound IPPBX extensions. In method one, the account and password used for login are the bound extension number and the login password configured in the configuration file respectively; in method two, the account and password used for login are the account and password used by the user to log in to the LDAP server; when authentication is performed through method two, an authentication request is generated based on the account and password and sent to the LDAP server, and the authentication result returned by the LDAP server is used as the login result.

9. An LDAP user interaction terminal device based on IPPBX, Features: The method comprises a processor, a memory, and a computer program stored in the memory and running on the processor, wherein the processor implements the steps of the method according to any one of claims 1 to 8 when executing the computer program.

10. A computer-readable storage medium storing a computer program. Features: When the computer program is executed by a processor, the steps of the method as claimed in any one of claims 1 to 8 are implemented.