Contains the fix for Domain Join failure of Windows EC2 instance with AWS managed Directory when TLS1.0 is disabled on the OS
Issue #, if available:
Unable to domain join Windows EC2 instance with AWS Directory Service using SSM document when TLS 1.0 is disabled on the OS. The SSM command throws the following error "The client and server cannot communicate, because they do not possess a common algorithm"
Description of changes:
Added the below line of code in AWS.DomainJoin.exe.config file in order to enable .Net based applications (AWS.DomainJoin.exe) to allow the operating system to choose the security protocol
Contains the fix for Domain Join failure of Windows EC2 instance with AWS managed Directory when TLS1.0 is disabled on the OS
Issue #, if available: Unable to domain join Windows EC2 instance with AWS Directory Service using SSM document when TLS 1.0 is disabled on the OS. The SSM command throws the following error "The client and server cannot communicate, because they do not possess a common algorithm"
Description of changes: Added the below line of code in AWS.DomainJoin.exe.config file in order to enable .Net based applications (AWS.DomainJoin.exe) to allow the operating system to choose the security protocol
Microsoft article: https://docs.microsoft.com/en-us/dotnet/framework/network-programming/tls#switchsystemnetdontenablesystemdefaulttlsversions
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.