Skip to content

v2.2.2: better handling of multi-org syncs
Compare
Choose a tag to compare
@adobeDan adobeDan released this 20 Nov 01:11
· 1791 commits to v2 since this release
v2.2.2
15e8616
This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
GPG key ID: 4AEE18F83AFDEB23
Expired
Verified
Learn about vigilant mode.

These release notes apply to v2.2.2 of 2017-11-19.

New Features

#294: Show statistics about users added to secondaries.

Bug Fixes

#283: Don't import keyring unless needed.

#286: Allow specifying attributes for Adobe IDs.

#288: Escape special characters in user input to LDAP queries.

#293: Don't crash when existing users are added to secondaries.

#301: User Sync fails when adding more than 10 groups to a user.

Compatibility with Prior Versions

There are no interface changes from prior versions.

Known Issues

Because the release on Windows is built with a pre-compiled version of pyldap, we have to specify a specific version to be used in each release (see the setup.py file for the specific version). This may not always be the latest version.

On the Win64 platform, there are very long pathnames embedded in the released build artifact user-sync.pex, which will cause problems unless you are on Windows 10 and are either running Python 3.6 or have enabled long pathnames system-wide (as described in this Microsoft Dev Center article). To work around this issue on older platforms, set the PEX_ROOT environment variable (as described in the docs here) to be a very short path (e.g., set PEX_ROOT=C:\pex).

Each release on each platform is built with a specific version of Python. Typically this is the latest available for that platform (from the OS vendor, if they provide one, from python.org otherwise). In general, and especially on Windows, you should use the same Python to run User Sync as it was built with.

Assets 12
Loading