Windows Connector

Windows Connector



This connector implements the LDAPS protocol and it is used to connect the Sync-Server with every server that allows this communication protocol.

Managed System

This connector has been performed to connect to the Active Directory system, it's a fork of our LDAP Connector with custom features.

For more information to check if your system may be synchronized with this connector you do not hesitate to contact us through our Contact form


To enable LDAPS in your Active Directory, please read the following guide: SSL access to Active Directory.

It is needed an Active Directory user with full administrator access.

Download and Install

This addon is located in the Connectors section and its name is Windows (including Active Directory).

For more information about the installation process you can visit the Addons Getting started page.

Agent Configuration


Generic parameters

After the installation of the addon, you may create and configure agent instances.

This addon has 5 available agents:

For more information about how you may configure the generic parameters of the agent, see the following link: Agents configuration

Custom parameters

Below there are the specific parameters for this agent implementation, "Active Directory"




Host name of the server

LDAP base DN

LDAP Base name

Principal name

User name in DN format, including base name if needed


Password for the user to connect.

Enable debug

Two options: [ Yes / No ].

When it is enabled more log traces are printed in the Synchronization Server log

Accepted certificates

Two options: [ Only trusted certificates / Any (insecure) ]

Follow referrals

Two options: [ Don't / Yes ]

If you select the Yes option, Soffid could follow the references to other systems if Soffid has the proper permissions.

Manage child domains

Two options: [ No / Yes ]

If you select the Yes option, Soffid will manage the domain referrals.

Create OUs when needed

Two options: [ No / Yes ]

If you select the Yes option and the OUs do not exist, these OUs will be created in the Active Directory. 

Real time load last login attribute

Two options: [ No / Yes ]

Real time load identity changes

Two options: [ No / Yes ]

You can check this option to synchronize the identities when Soffid is the authoritative data source.

You must enable periodic synchronization.

Attribute mapping

Active Directory connector could manage Users and Groups by using LDAPS protocol.


Some agents require to configure some custom attributes, you will use the properties section to do that.

To enable it, add the following properties to each object mapping:




AD agent will always map account and group names to the SAMAccount attribute. BaseDN and cn can be calculated based on user attributes. AD agent is able to move and rename AD objects. If you don't desire users or groups to be renamed or moved, an object property named "rename" with the value "false" can be added to some object mappings.


You can configure it if you want the reconciliation process to search accounts on a directory subtree other than AD root, put a searchBase property with the relative tree to look for.


The AD attribute works as the primary key. Usually, it's the sAMAccountName and can be omitted.


Set to true if you want the connector to create disabled accounts in the active directory. By default, disabled accounts are not created until enabled.

For instance:



You can customize attribute mappings, you only need to select system objects and the Soffid objects related, manage their attributes, and make either inbound or outbound attribute mappings.

Using a windows connector you can map users, groups, and role objects. Active Directory membership is automatically managed based on user and group mappings.

Any object mapping must have the following system attributes:

System attribute



Active Directory object class. The following values mostly used "user", "group" or "organizationalUnit"


Active Directory container where user or group should be created. Its value should be absolute, containing Active Directory DC parts


Active Directory container where user or group should be created. Its value should be relative to Active Directory DC parts.


Object name

There is a bunch of AD special attributes that need some special treatment:

System attribute



Is automatically mapped. It is internally mapped to role name or account name, without further customization


Sets the last date (in nanoseconds since 1600) in which the account will be valid. A common mapping expression is:

if ( attributes {"expirationDate"} == null)
   return 9223372036854775807L;
   return attributes{"expirationDate"}.getTime() * 10000L + 116445528000000000L;


Can be used to identify distribution lists. A value of 268435457 or 268435456 means the AD group is a distribution list group rather than a security group.


The attribute can be used to get the last time an account was used. Soffid attribute is named lastLogin and the right mapping could be the following one. Mind when you make a reference to lastLogon attribute, every domain controller is queried about this attribute, as its value is not replicated across AD controllers:

if ( lastLogon == null || lastLogon == void) return null;
Long v = Long.decode(lastLogon);
v = v / 10000000L;
return new Date(v*1000);



This is a virtual attribute that can be used to indicate if a user can or cannot change the password. You can't assign this permission by directly modifying the UserAccountControl attribute. 

For more information about how you may configure attribute mapping, see the following link: Soffid Attribute Mapping Reference

For instance:




You can define BeanShell scripts that will be triggered when data is loaded into the target system (outgoing triggers). The trigger result will be a boolean value, true to continue or false to stop.

Triggers can be used to validate or perform a specific action just before performing an operation or just after performing an operation on target objects. 

To view some examples, visit the Outgoing triggers examples page.

Avoid incremental load authoritative

The Customizable Active Directory connector has an incremental load authoritative process. 

When this process is executed, it requests the changes to Active Directory after the uSNChanged

The value of this field is saved in Soffid in the parameter soffid.sync.authoritative.change.NAME_OF_THE_AGENT

If you want to launch a complete load authoritative process, remove this parameter first. At the end of the process, the parameter will be generated automatically.

For more information, go to the Soffid Parameters page.

HOWTO SSL access to Active Directory

Table of Contents


This howto will show you how to install the Certificate Services in Windows Acive Directory Servers.

Before beginning, make sure the Internet Information Server (IIS) is installed in your server.

Installing the Certificate Services

1. Click Start, select Control Panel and click Add or Remove Programs.

WIN Connector - Installing 1.png

2. In the Add or Remove Programs window, click Add/Remove Windows Components, check the Certificate Services and click Next.

WIN Connector - Installing 2.png

3. Click Next in the CA Type page.

WIN Connector - Installing 3.png

4. Fill up the Common name for this CA and click Next.

WIN Connector - Installing 4.png

5. Click Next in the Certificate Database Settings page.

WIN Connector - Installing 5.png

6. The Certificate Services will now be installed.

WIN Connector - Installing 6.png

7. Click Finish and restart your server.

WIN Connector - Installing 7.png

Configuring Automatic Certificate Request for Domain Controllers

1. Click Start, select Administrative Tools and click Domain Controller Security Policy.

WIN Connector - Configuring 1.png

2. In the Default Domain Controller Security Settings window, click the Public Key Policies folder.

WIN Connector - Configuring 2.png

3. Right click Automatic Certificate Request Settings, select New and click Automatic Certificate Request.