-
-
Notifications
You must be signed in to change notification settings - Fork 344
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
TfsExportUsersForMappingProcessor: allow matching users by email (#2526)
Our scenario is: - Source server is on-premise TFS 2018 connected to on-premise Active Directory. - Target server is Azure DevOps connected to Azure Entra ID (formerly Azure Active Directory). Even when the users are synchronized between the Active Directiories, the users' display names are often different between the two. So default matchind by display name does not work for us. I implemented the possibility to match users by email (at least for us it works for most cases). This matching is turned off by default. When turned on, it has higher precedence than matching by display name. So first, match by email is looked for and if no match is found, default matching by display name is used. Because of this I expanded properties of the users loaded from server. I still do not use all of them, but I want to keep them for future use (I have another PR prepared). Because of this, I also added mapper ([Riok.Mapperly](https://github.com/riok/mapperly)), so I do not need to copy properties one by one when creating `IdentityItemData` object from `Identity` object.
- Loading branch information
Showing
6 changed files
with
68 additions
and
24 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters