Differences

This shows you the differences between two versions of the page.

--- devel:documentation:wizards [2021/02/26 12:52]
svandav [Certificate]
+++ devel:documentation:wizards [2021/06/25 07:52]
svandav [System wizards]
@@ Line 13: / Line 13: @@
 In the version 10.6.0, a **universal wizard for creating** a system was added.** Since version 10.7.0, we focused on creating specialized wizards** that simplify the configuration of the connector.
-Currently, the following specialized wizards are available in IdM:
+**Currently, the following specialized wizards are available in IdM:**
+|**Name**                                        	        |**More details**  |
+| CSV wizard   |[[devel:documentation:wizards:csv|]] |
+| Database table wizard        	        |[[devel:documentation:wizards:table|]]|
+| MS AD wizard for users         	        |[[devel:documentation:wizards:ad_user|]]
 ===== CSV wizard =====
@@ Line 32: / Line 39: @@
 ===== Microsoft Active Directory (MS AD) wizard =====
-{{tag>MSAD MS wizard}}
-The most ambitious is the wizard for connecting the **Microsoft Active Directory** system (AD). Connecting **AD** within **IdM** is very important and at the same time manual connection can be a relatively complex matter for many and more advanced users.
-The complication starts in communication with AD. Here it is very important to use **secure communication** (SSL), which requires the installation of a **correct** **certificate**. It is also important to verify that our service AD account has sufficient privileges.
-However, the biggest difficulties can occur with many rules that must be followed during the connection (**connector settings**) and especially in the way to correctly map the individual attributes of AD. Just choosing the right attributes to be mapped to AD may not be easy for an ignorant user.
-**This guide therefore solves all the mentioned problems** and is based on **our best experience** of how to effectively manage an AD system.
-==== Connection to an AD system ====
-In the first step, choose the **name of the system** as you want it to **appear in IdM**. Next, fill access data to the connected AD. Ie. **host** name, TCP **port**, **user name** and **password**.
-<note important>In this step, you can choose whether you want to communicate with AD using a secure **LDAPS** connection (SSL). This option is preselected. **We strongly recommend using secure communication**. The reason is not only the **security aspect**, but also the **functional consequences** that can result from the use of an unsecured connection. For example: If you use an insecure connection, you will not be able to **create a new account with a password** (restrictions on the AD side).</note>
-{{ :devel:documentation:wizard_ad_01.png?600 |}}
-==== Certificate ====
-In the second step, the wizard can **download the certificate from the AD** and save it to the server. First, the wizard verifies that your IdM server has the correct certificate installed for communication with AD. Next, the certificate is searched directly in AD. The goal is to **find a certificate issued by the highest possible authority**. The found certificate needs to be inserted into the **trusted certificate store** and the IdM restarted. The reason why we do not recommend using a server certificate directly in the trusted certificate store (it would be functionally sufficient) is its shorter validity (typically only 1 year).
-{{ :devel:documentation:wizard_ad_02.png?600 |}}
-==== Permissions ====
-{{ :devel:documentation:wizard_ad_03.png?600 |}}
-==== Additional data ====
-{{ :devel:documentation:wizard_ad_04.png?600 |}}
-==== Attributes ====
-{{ :devel:documentation:wizard_ad_05.png?600 |}}
-==== Conclusion ====
-{{ :devel:documentation:wizard_ad_06.png?600 |}}