Difference between revisions of "LDAP Module"
(→Setup) |
|||
| (5 intermediate revisions by 2 users not shown) | |||
| Line 10: | Line 10: | ||
There is no need of installing this module, as it is already included within Tactic services. | There is no need of installing this module, as it is already included within Tactic services. | ||
= Setup = | = Setup = | ||
For using this module the users need to enable it by using an administrator account. The menu options for activating this module are: '''Home –> Setup – > Module'''. The users then need to click on '''Activate'''. The modules will be activated after completing this step. | For using this module the users need to enable it by using an administrator account. The menu options for activating this module are: '''Home –> Setup – > Module'''. The users then need to click on '''Activate'''. The modules will be activated after completing this step. The settings icon {{#fas:cog}} will be visible at the end of the module box, the users can click in that to access further setup for this module for accessing the functionalities in a better way. | ||
[[File:LDAP_1.PNG|center|link=]] | |||
= Using LDAP Module = | = Using LDAP Module = | ||
The steps of using LDAP module are: | The steps of using LDAP module are: | ||
| Line 19: | Line 23: | ||
* Creating resemblance between Tactic and LDAP fields | * Creating resemblance between Tactic and LDAP fields | ||
* Upon clicking the option of '''Test Synchronize''' the users will be able to test the establishment of LDAP connection | * Upon clicking the option of '''Test Synchronize''' the users will be able to test the establishment of LDAP connection | ||
= Usage of LDAP = | |||
After synchronisation the users do not have to perform any more set up activities for LDAP. All of the changes that are made in Tactic will be saved in LDAP as well. If there is any error in the way of the synchronization, Tactic transaction will be ceased. However, LDAP returned messages are not always correct. Hence, if there is any issues regarding understanding the error messages the users need to check the “Errors” chapter. | |||
= Errors = | |||
The users can easily find the ldap/temp/ldapinput.in file, which will be created automatically in Tactic document directory. Upon opening the file the users can find full ldap command, which can be emulated by the same action that PHP sent to LDAP server. The users need to run this command and upon analysing the result the users will be able to generate more information on error and its source. | |||
Latest revision as of 09:01, 21 November 2022
Introduction
The LDAP module should be used for synchronizing Tactic entities with the help of a LDAP database. There entities that Tactic allows to be synchronized are:
Contact (Module Third parties) -> LDAP Group (Module Users) -> LDAP LDAP -> User (Module Users) Member (Module Foundations) -> LDAP User (Module Users) -> LDAP
If the users do not have an LDAP server then they need to install and configure the same.
Installation
There is no need of installing this module, as it is already included within Tactic services.
Setup
For using this module the users need to enable it by using an administrator account. The menu options for activating this module are: Home –> Setup – > Module. The users then need to click on Activate. The modules will be activated after completing this step. The settings icon will be visible at the end of the module box, the users can click in that to access further setup for this module for accessing the functionalities in a better way.
Using LDAP Module
The steps of using LDAP module are:
- Choosing the database that the users need to synchronize
- Filling the data in LDAP server information
- The users can check their LDAP connection by testing the LDAP connection
- Entering organization in LDAP tree
- Creating resemblance between Tactic and LDAP fields
- Upon clicking the option of Test Synchronize the users will be able to test the establishment of LDAP connection
Usage of LDAP
After synchronisation the users do not have to perform any more set up activities for LDAP. All of the changes that are made in Tactic will be saved in LDAP as well. If there is any error in the way of the synchronization, Tactic transaction will be ceased. However, LDAP returned messages are not always correct. Hence, if there is any issues regarding understanding the error messages the users need to check the “Errors” chapter.
Errors
The users can easily find the ldap/temp/ldapinput.in file, which will be created automatically in Tactic document directory. Upon opening the file the users can find full ldap command, which can be emulated by the same action that PHP sent to LDAP server. The users need to run this command and upon analysing the result the users will be able to generate more information on error and its source.
