About inWebo Directory Sync (IWDS)

IWDS is a Java application allowing any inWebo service administrator to do bulk creation, modification and deletion of inWebo users and groups, based on input data taken from an LDAP directory or a .csv file.

IWDS also works in batch mode. In this case, it is installed on a server and launched periodically, using a Task Scheduler (Linux cron or Windows Task Scheduler).

Important: IWDS will not write anything in your LDAP directory. It will only read.

IWDS is developed by inWebo to allow you to synchronize your user's between inWebo administration console and a directory (AD, LDAP, .csv...). It is available on Windows in GUI mode. It supports:

  • Active Directory

  • LDAP

  • User listing file in csv format

Contact inWebo for more information

Four steps synchronization

If group synchronization is not activated, the steps are:

  1. Getting inWebo users

  2. Getting LDAP users

  3. Computing a “Diff” between LDAP user list and inWebo user list. This outputs a list of transactions required to synchronize your LDAP server(s) with inWebo

  4. Synchronizing (apply diff): executing the transactions created by the “Diff”

If group synchronization is activated, the steps are:

  1. Getting inWebo objects (users, roles, groups and group memberships)

  2. Getting LDAP objects (users, groups and group memberships)

  3. Computing a diff between LDAP users and inWebo users and between LDAP group memberships and inWebo group memberships. “This outputs” a list of transactions required to synchronize your LDAP server(s) with inWebo

  4. Synchronizing (apply diff): executing the transactions created by the “Diff”

If group synchronization is activated, it is mandatory:

  • to set the mapping between LDAP groups and inWebo groups before computing the diff and synchronize. Otherwise IWDS is not able to determine which inWebo group LDAP users should be added to. This mapping can be set either using IWDS GUI or by adding the appropriate file in the configuration directory (see Configuration File Format section below).

Topics

IWDS Release Notes

Click here to see all inWebo Directory Sync (IWDS) Release Notes

IWDS 2.4

January 25, 2022

  • Multi-source: each instance of IWDS can define a provisioningId. Default is 1. (more information)

  • Update for Log4j vulnerability

  • Account deletion limit parameter (default 25) is applied to GUI in addition to command-line mode (more information)

  • Interface rebranded with current inWebo logo

  • Alternative login is renamed login2 in the interface

  • Fixed an issue that caused unnecessary sync of the entire user list

  • Update to support OpenJDK from 8 to current version

  • Fixed an issue with the result file that did not show login2

  • Updated IWDS user agent to provide version, Java version and system

  • Fixed help broken link

  • Fixed an issue with the data source test

IWDS 2.1.17

June 11, 2021

  • Sync of new field “alternative login”

Previous release notes

  • 2.1.15 and 2.1.16 are internal releases - not published.

  • 2.1.14: minor bug fixes and enhancements. inWebo status is now kept for all users including administrators. Extended email format support (including simple quotes in user name part of email address)

  • 2.1.13: updated IWDS to support email addresses defined on domains with long extensions (example: john.doe@mycompany.security)

  • 2.1.12: fixing a bug where IWDS in batch mode could crash when launched after a fresh installation or with a user different from the one that installed the software

  • 2.1.11: fixing a bug where the synchronization result screen could not be displayed in GUI mode

  • 2.1.10: fixing a bug where the group membership operations were not added to the synchronization task for expired users being recreated

  • 2.1.9: fixing a bug where the utf-8 charset encoding was not properly applied when IWDS was launched in batch mode

  • 2.1.8: modification of the encoding of the product from iso-8859-1 to utf-8

  • 2.1.7: fixing a bug where an activation email was not re-sent to pending activation users when option was checked in synchronization rule

  • 2.1.6: fixing a bug where the group synchronization could fail when using several LDAP sources having a group mapping defined

  • 2.1.5: fixing a bug where IWDS could fail to operate in batch mode

  • 2.1.4: fixing a bug where IWDS could fail while retrieving inWebo user group memberships

  • 2.1.3: minor bug fixes and enhancements

  • 2.1.2: management of inWebo services in "machine" mode

  • 2.1.1: optimizing the query retrieving inWebo groupe memberships. Minor bug fixes and enhancements