You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This version has 2 new required configuration items. If you are using an earlier version, you will need to add the following entires to your main user-sync-config.yaml file:
7
+
8
+
limits:
9
+
max_deletions_per_run: 10 # if --remove-nonexistent-users is specified, this is the most users that will be removed. Others will be left for a later run. A critical message will be logged.
10
+
max_missing_users: 200 # if more than this number of user accounts are not found in the directory, user sync will abort with an error and a critical message will be logged.
11
+
12
+
To update your installation, download the release for your platform and replace the user-sync or user-sync.pex file with the new one. Same the old one in case of problems
13
+
14
+
Because this version contains a more aggressive --process-groups function (a bug fix) you may want to run with --test-only first and make sure nothing unexpected is happening.
15
+
16
+
## New Features
17
+
18
+
1. Ability to specify additional directory attributes to load and specify a code snippet to implement complex mappings from directory information to Adobe user information and group membership. This is covered in more detail in the updated documentastion.
19
+
20
+
2. Releases for different platforms are packaged separately so you only have to download the platform(s) you want. You do have to download the example configuration files and documentation separately.
21
+
22
+
3. User removal limits and guards. There are some new features to prevent user sync from accidentally removing large numbers of users in the event of misconfiguration or changes in the directory which result in users not being returned from queries.
23
+
24
+
25
+
26
+
## Changes in Behavior
27
+
28
+
A bug in --process-groups was fixed. Previously, users present in the Adobe admin console but not in the directory were not removed from groups that were mapped in the user sync configuration file. This is now fixed. A group (user group or product configuration) that is mapped from a directory group is assumed to be under user sync control and any users in such groups that are not in the directory and in groups in the directory mapped to those Adobe groups are removed.
29
+
30
+
This release of user sync should be compatible and have no other behavior changes.
31
+
32
+
## Compatibility with Prior Versions
33
+
34
+
Other than as noted above, existing configuration files and should work and have the same behavior.
# (optional) Default country code to use if directory doesn't provide one for a user [Must be two-letter ISO-3166 code - see https://en.wikipedia.org/wiki/ISO_3166-1]
@@ -45,7 +45,7 @@ directory:
45
45
# dashboard_groups: a list of strings identifying the dashboard groups.
46
46
#
47
47
# a group in dashboard_groups can be qualified with, the first part being
48
-
# the trustee organization name.
48
+
# the accessor organization name.
49
49
# e.g. org1::Default Acrobat Pro DC configuration
50
50
#
51
51
# examples:
@@ -66,6 +66,10 @@ directory:
66
66
# Default is:
67
67
# user_identity_type: enterpriseID
68
68
69
+
limits:
70
+
max_deletions_per_run: 10# if --remove-nonexistent-users is specified, this is the most users that will be removed. Others will be left for a later run. A critical message will be logged.
71
+
max_missing_users: 200# if more than this number of user accounts are not found in the directory, user sync will abort with an error and a critical message will be logged.
72
+
69
73
logging:
70
74
# specifies whether you wish to generate a log file
if (identity_type=='federatedID'anddefault_country_code==Noneanduser_country_code==None):
126
+
mock_rules.logger.error.assert_called_with('User %s cannot be added as it has a blank country code and no default has been specified.','[email protected]')
0 commit comments