|Functionality||Deprecated (if favor of SSH Connector)|
|Support provided by||Evolveum|
|Target systems||Microsoft Windows Server 2012R2|
|Notes||Only scripting operations are supported|
Specialized connector that provides PowerShell scripting capabilities.
|Native attribute names||NO|
|Scripting||YES||Command execution and Powershell by using WinRM (WS-MAN)|
This connector was "separated" from Active Directory Connector (LDAP) version 2.4.
This connector is part of the LDAP Connector bundle. It is distributed together with LDAP Connector and eDirectory Connector.
|Bundled with midPoint|
|1.0||Evolveum||3 Apr 2020||184.108.40.206||None|
|1.1||Evolveum||21 July 2020||220.127.116.11||None|
Option to disable certificate checks.
|1.1.1||Evolveum||6 August 2020||18.104.22.168||None|
Fixing disableCertificateChecks: allowing FQDN and CN mismatch.
Following versions of Windows servers are supported:
This connector is deprecated. The Win-RM services proved to be very problematic and unstable while using this connector. Fortunatelly, recent Windows servers have an option to install SSH servers. Use of SSH instead of Win-RM is strongly recommended. Please use SSH Connector instead of this connector whenever possible.
Connector is supported only in Java 11 environment.
Technically, this connector can be used to provision Microsoft Exchange servers in a indirect way by using PowerShell scripts.
Firstly, the Exchange attributes are accessible in Active Directory when the Exchange software is installed. The Active Directory Connector (LDAP) is needed to manage those attributes.
Secondly, this connector can be used to execute powershell scripts remotely using the WinRM interface. This feature can be used to manage Exchange mailboxes and additional settings. Please see Powershell Support in AD/LDAP Connector page for more details.
However, support for MS Exchange is not included in standard support for this connector (see below).
This connector was deprecated in favor of SSH Connector.
This connector is still supported (but it is not bundled with midPoint support, it has to be purchased separately). However, there are limitations:
The connector itself is available under the terms of Apache License 2.0. We are not using any Microsoft library or any other component that might be subject to Microsoft licensing. To our best knowledge no extra license is needed to use the connector with Windows servers. However the Microsoft license texts are not entirely clear and we are not lawyers. Therefore it is recommended for each user to make his own analysis of the licensing issues. Please use your Microsoft support program and contact Microsoft with the licensing question when in doubt.