Differences

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

--- devel:documentation:systems:dev:remote-connector [2019/10/17 08:28]
urbanl
+++ — (current)
@@ Line 1: / Line 1: @@
-====== Remote connector server ======
-{{tag> system connector configuration }}
-===== Why use remote connector server? =====
-System CzechIdM has available only certain types of connectors. If we want to use another connectors, such as **Active Directory** or **Google Apps**, we need to use a remote connector server with other connectors.
-===== How does a remote connector server works in CzechIdM? =====
-The remote server connector configuration form behaves just like the local connector form - this means that definition is stored in the EAV attributes for system which it belongs. As a key to EAV attributes are used the system name, connector name, and connector version. Therefore, it is possible to have multiple connectors with different version on the remote connector server.
-===== Connector server setup =====
-We need [[https://connid.atlassian.net/wiki/display/BASE/Downloads|download remote connector server]] from connid. Now is recommended **use version 1.4.3** of remote connector server. Create a new root folder for the connector server. In this folder create two new subfolders:
-  * **bundles** - folder for connectors,
-  * **lib** - folder for external libraries.
-To folder **bundles** download all connector you need. Download from this [[http://repo1.maven.org/maven2/net/tirasa/connid/bundles/|url]]. Now you go to root folder **bundles** and copy all files from archive folder: ''connector-server-zip-1.4.3.0.zip/connid-connector-server/lib/framework/''.
-Now we need only configuration properties, this file we will found in jar, path:''connector-server-zip-1.4.3.0.zip/connid-connector-server/lib/framework/connector-framework-internal.jar/org/identityconnectors/framework/server/connectorserver.properties''.
-==== Start remote connector server - Linux ====
-All commands execute in root folder of remote connector server.
-Generate password for the remote connector server. For creating password, use something like ''pwgen -1 12''. This password is necessary to fill in the system/connector configuration form in the IdM.
-<code>
-java -cp "connector-framework.jar:connector-framework-internal.jar:groovy-all.jar" org.identityconnectors.framework.server.Main -setKey -key 123456 -properties connectorserver.properties
-</code>
-Run connector server:
-<code>
-java -cp "connector-framework.jar:connector-framework-internal.jar:groovy-all.jar" org.identityconnectors.framework.server.Main -run -properties connectorserver.properties
-</code>
-Run connector server at background:
-<code>
-java -cp "connector-framework.jar:connector-framework-internal.jar:groovy-all.jar" org.identityconnectors.framework.server.Main -run -properties connectorserver.properties &
-</code>
-Another settings (such as log) will be found at configurations file: **connectorserver.properties**
-==== Start remote connector - Windows ====
-All commands execute in root folder of remote connector server.
-===== How to set up a remote connector server? =====
-On the system tab we will create a new system. In the detail of this system, check option **"Use remote connector server"** and fill everything form field that system needed to connect to the remote system. For connection it is necessary to fill the host and port on which the connector is available on remote server. If server is secured by password you will need fill the password for connect to remote connector server. Password for connect will be stored in local confidential storage.
-After saving all the necessary information to the remote connector of the server, we will go to the **"Configurations"** tab. From now will be available only connectors on the remote connector server.
-The functionality of the remote connector server can be verified as well as the functionality of the local connector - using the **"Test connector"**.