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
Copy file name to clipboardExpand all lines: docs/en/user-manual/advanced_configuration.md
-31Lines changed: 0 additions & 31 deletions
Original file line number
Diff line number
Diff line change
@@ -450,37 +450,6 @@ For domains that use username-based login, the `user_username_format` configurat
450
450
451
451
If you are using username-based login, you must still provide a unique email address for every user, and that email address must be in a domain that the organization has claimed and owns. User Sync will not add a user to the Adobe organization without an email address.
452
452
453
-
## Syncing Email-based Users with Different Email Address
454
-
455
-
Some organizations must authenticate users with an internal-facing
456
-
email-type ID such as user principal name, but wish to allow users to
457
-
user their public-facing email address to log into Adobe products and
458
-
use collaboration features.
459
-
460
-
Internally, the Adobe Admin Console maintains a distinction between a
461
-
user's email-type username and their email address. These fields are
462
-
normally set to the same value, but the Admin Console allows the
463
-
email address to differ from the username. The User Management API
464
-
also supports the creation, update, and deletion of users that have
465
-
different usernames and email addresses.
466
-
467
-
**Note:** Any domain used in the email address field **must** be
468
-
claimed and added to an Adobe identity directory.
469
-
470
-
To use this functionality in the Sync Tool, simply specify both the
471
-
`user_email_format`and the `user_username_format` options in
472
-
`connector-ldap.yml`.
473
-
474
-
```yaml
475
-
user_email_format: "{mail}"
476
-
user_username_format: "{userPrincipalName}"
477
-
```
478
-
479
-
In this scenario, the `user_username_format` option must map to a field
480
-
that will always contain an email-type identifier (it does not need
481
-
to be a live, working email address). Users with non-email values
482
-
will fail to be validated and synced.
483
-
484
453
## Protecting Specific Accounts from User Sync Deletion
485
454
486
455
If you drive account creation and removal through User Sync, and want to manually create a few accounts, you may need this feature to keep User Sync from deleting the manually created accounts.
0 commit comments