-
-
Notifications
You must be signed in to change notification settings - Fork 345
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
TfsExportUsersForMappingProcessor: export all users in source and tar…
…get server to JSON file (#2527) 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 and also quite a bunch of email addresses are different. So a lot of people are not matched at all and in exported mapping file, the target name is `null`. So the mapping file needs to be manually edited to add missing users. Usually (almost always), the user is in target server, but has different email and display name. To help find the corresponding user, this PR allows to export all users in source and target server into separate JSON. We can than find the user we need and use his correct display name in mapping file. Two properties are added to `TfsExportUsersForMappingProcessorOptions`: - `ExportAllUsers` – turns this feature on. - `UserExportFile` – path to file, where users will be exported. ## Example of export ``` json { "SourceUsers": [ { "Sid": "24b644ca-b413-4bd5-bdea-466534a69c72:Build:1cf84e9e-e068-4a9a-b12e-bf058294c1f5", "DisplayName": "Lorem Ipsum", "Domain": "Build", "AccountName": "lorem", "MailAddress": "lorem@example.com" }, ... "TargetUsers": [ { "Sid": "751af7c1-c13a-4f1b-888e-da6f6db86a01:Build:0132d9af-7fab-4f97-8170-b28466e07427", "DisplayName": "Dolor Sit", "Domain": "Build", "AccountName": "dolor", "MailAddress": "dolor@example.com" }, ... } ```
- Loading branch information
Showing
5 changed files
with
83 additions
and
32 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