SyncLDAP (TWL1)

Description

This task synchronizes users, internal directory and external number from LDAP.

Release notes

Show release notes
Version 2.0.7 - Early deployment
  • Feature: support for setting caller id from LDAP attribute (TS-2581)
  • Dependency:
    • LDAP Synchronization Module >= 1.17.4

Version 2.0.4 - Early deployment
  • Bugfix: Convert first and last name from SMP to UTF-8 (TS-268)
  • Bugfix: DDIs no synced any more (TS-277)
  • Dependency:
    • LDAP Synchronization Module >= 1.15.2

Version 2.0.3 - Deprecated
  • Bugfix: Task failed with profile parameter different from Template-User (M24648)
  • Deprecated: DDIs no synced any more (TS-277)
  • Dependency:
    • LDAP Synchronization Module >= 1.4.0

Version 2.0.2 - Deprecated
  • Bugfix: Data from previous imported user, extension, ddi were copied to next entry when template are used (M23224)
  • Bugfix: Import of new user was failing when a template user was configured (M23224)
  • Deprecated: DDIs no synced any more (TS-277)
  • Dependency:
    • LDAP Synchronization Module >= 1.4.0

Version 2.0.1 - Early deployment
  • Improvement: Template extension, ddi and user can now be provided via LDAP (M21560)
  • Dependency:
    • LDAP Synchronization Module >= 1.4.0

Version 2.0.0 - Early deployment
  • Feature: Make Sync ldap compatible with Fusion 4 (M12721)
  • Feature: Add a template user for user's default values on creation (M12721)
  • Dependency:
    • LDAP Synchronization Module >= 1.4.0

Version 1.11.0 - Early deployment
  • Feature: sync primary and secondary phone (M0)
  • Dependency:
    • LDAP Synchronization Module >= 1.11.2

Version 1.10.1 - Early deployment
  • Bugfix: The callflow was not synchronized from LDAP for an existing extension when the current callflow was the same as the default callflow. (M18210)
  • Dependency:
    • LDAP Synchronization Module >= 1.11.0

Version 1.10.0 - Early deployment
  • Feature: when adding records, take defaults from a given "template" extension (M9894)
  • Improvement: Also show owner for deleted extensions in debug output (M0)
  • Feature: Add extension for added, updated and deleted users (M9635)
  • Bugfix: Character encoding issue (M10133)
  • Feature: Make requests timeout configurable (M10670)
  • Improvement: Accurate dry run info (M11637)
  • Bugfix: Fax number synchronization (M12290)
  • Limitation: This task is not compatible with Parameter Sets (M0)
  • Dependency:
    • LDAP Synchronization Module >= 1.11.0

Version 1.9.3 - Early deployment
  • Bugfix: Increase requests timeout (M10670)

Version 1.9.2 - General deployment
  • Bugfix: Due to too much generated debug information, the task could stop due to out-of-memory (M0)

Version 1.9.1 - Deprecated
  • Improvement: Display owner of extension that is modified (M8804)
  • Deprecated: Accidental debug caused out-of-memory (M0)

Version 1.9 - General deployment
  • Bugfix: non-ascii characters get garbled(M00000)

Version 1.8 - General deployment
  • Bugfix: Corrected the visual bug of the report when 'Delete Policy' set to never

Version 1.7 - Deprecated
  • Feature: Added option 'Delete Policy' (M0004505)
  • Deprecated: Visual bug in the report

Version 1.6 - General deployment
  • Bugfix: non-ascii characters not properly displayed in debug output report (M0004461)

Version 1.5 - General deployment
  • Bugfix: users with non-ascii characters in their name are always reported as being updated

Version 1.4 - Deprecated
  • bugfix: updates in user attributes not synced

Version 1.3 - General deployment
  • Improvement: Improved report
  • Improvement: Catch errors if record already exists on SMP with source not LDAP
  • Feature: Dry-run mode
  • Improvement: Improved detection of HA mode

Version 1.2 - General deployment
  • Bugfix: minor corrections

Version 1.1 - General deployment
  • bugfix: populate owner instead of admin
  • bugfix: set group to nothing instead of 1
  • support user_X fields

Version 1.0 - General deployment

Version 0.0.2 - Deprecated
  • Deprecated: Please use version 1.10.0 or higher.
  • Feature: Synchronize the callflow from an ldap attribute (M3299)
  • Improvement: View DDI dump in SyncLDAP debug (M5266)
  • Dependency:
    • LDAP Synchronization module >= 1.10.0 (required only when the callflow is to be synchronized from ldap)

Version 0.0.1 - Deprecated
  • Deprecated: Please use version 1.9.3 or higher.

Version 0.0 - Deprecated
  • Deprecated: Significant improvements have been done in a higher version

Resource configuration interface

GUI unavailable.

Task configuration parameters provided by SMP 5.3+

Warning: Can't find topic CustomerDocs.GenSmpDocCommonTaskParametersRGb55

Resource configuration parameters

  • Report Detail Select the level of detail you want to see in the report.
    • Warning: only show potential problem cases
    • Info: as Warning but also show interesting information, like which records have been added, modified or deleted
    • Debug: as Info, but adds technical debug information. This is intended for Escaux support staff and should generally not be used as it may slow down the process.
  • Set to sop
    • This sop: In cluster mode, extensions and ddis will only be set to this sop and will not be propagated on all sop of the cluster.
    • All: In cluster mode, extensions and ddis will be set to all sops of the cluster.
  • Delete policy
    • Always: when users, extensions or ddi are removed from the LDAP server, they will be removed from the sop during the synchronisation.
    • Never: when users, extension or ddi are removed from the LDAP server, they won't be removed from the sop during the synchronisation. You will have to do it manually or set the Delete policy to 'Always'.
  • Template extension : The extension from which default values will be fetched for new records.
  • Timeout (default 180 s): The maximum time that the task will be waiting for data from the LDAP server. Default is 180 seconds.
  • SMP API: The smp api url to use for api requests (since version 2.0.0). eg. !https://smp.smpXXX.escaux.com/api/v1.
  • Template user: The user from which default values will be fetched for new records (since version 2.0.0).
  • Template DDI: The extension from which mapddi default values will be fetched for new records (since version 2.0.0).
  • Preserve fields when no ldap value: Preserve parameter defined in the directory entry when value coming from LDAP is empty. This setting can contain multiple comma separated parameters (e.g. P_CallerIDNumber,PHONE1) (since version 2.0.5).

Associated application notes

Default values for Fusion 4

Since version 2.0.0, you are able to set default values for extensions, users and ddis by configuring the an extension, a user or a ddi, in source SMP and set them as in the task.
Copyright © Escaux SA