Audience: ClassLink Administrator
- Destination: Cross-Domain Uniqueness
- New Source Type: Active Directory
- User List: Reset Password
- User List: Configurable Column
- User List: Single User Dry Run
- Exports: Sync Changes and Sync All
- New Relation: Does Not Contain
Destination: Cross-Domain Uniqueness
We've added a new username setting to prevent duplicate usernames across different domains and destinations. For each username type in a destination, you can set uniqueness checks in the Username Settings menu in the Cross-Domain Uniqueness tab.
1. Navigate to the username settings for the desired username type.
2. Click the blue plus icon to add a check.
This consists of the target destination and the username type that you want to check against.
For example, in a GSuite destination, you can check that the primaryEmail for each user does not match any usernames in an Active Directory destination. You can check against sAMAccountName, userPrincipalName, or both. If a match is found between the two destinations, the export will fail to prevent duplicate usernames between the two destinations. If no match is found, the export will succeed. If multiple checks are added, the export will fail if a duplicate is found for at least one check. You can prevent these exports from failing by either enabling auto-resolve in the Username Resolutions tab, or by adding alternate username formulas in Username Rules.
Exports will succeed in uniqueness checks that compare usernames with two different domains. When comparing to sAMAccountName (as the Target Username) in a non-Active Directory destination, the username's domain will be excluded from the check. When comparing for sAMAccountName in an Active Directory destination, you must include the domain(s) of the target username type that you are comparing to.
New Source Type: Active Directory
We've added a new source type: Active Directory. While creating an Active Directory source, you will be prompted for your credentials: username, password, domain, base path, protocol, and port.
1. Once you've connected to your Active Directory, you can proceed to the Source Mappings tab where you can filter users to be imported.
2. Click Filter By OUs to select the specific OUs from which users are to be imported.
User List: Reset Password
You can now reset a user's password for any applicable destination from the user list.
1. In the user list page -> click the sandwich menu (...) next to the desired user
2. Click Change Password.
3. Select the desired destination.
4. Enter the new password.
5. Click the blue Change Password button.
This will queue an export of the action type "ResetPassword". You can view the logs for more details. This action can be performed for Active Directory, GSuite, and Azure destination types.
User List: Single User Dry Run
You can now initiate dry runs for a single user from the user list.
1. In the user list page -> click the sandwich menu (...) next to the desired user.
2. Click Export User (Dry).
If any changes are detected for the user, it will be exported in a dry run to the applicable destinations.
User List: Configurable Column
You can now configure the user list to display a selected OneSync field for all users within your user list. Once you've selected a OneSync field, you can search and filter the user list based on that field.
Exports: Sync Changes and Sync All
Full Sync has been split into Sync Changes and Sync All.
Sync Changes will detect any changes in users, collections, or a destination and queue those changes for exports.
Sync All will export all data regardless of whether or not there are changes.
New Relation: Does Not Contain
We've added a new relation that you can use when defining conditions in OneSync: Does Not Contain. The value will equal a string that the OneSync field should not contain. You can view this new relationship when defining collections, or conditions for custom mappings, groups, and events & triggers.