Thats My Shell

PowerShell TLS 1.2 Only

Ever try to communicate with a remote API or URL only to receive an error message?  Reviewing the code is usually the first step in troubleshooting. 

tls_error
PowerShell Error

However, as administrators in a large enterprise we have to understand the ever-growing changes in security framework requirements.  SSL 3.0 and TLS 1.0 have already all become deprecated. TLS 1.1 will become end of life on March 31, 2020. This has triggered most enterprises to start disabling this functionality in their server infrastructure.

As an administrator, you can validate the security ciphers that PowerShell is currently utilizing with the following command

[Net.ServicePointManager]::SecurityProtocol

This will generate the following output.

PowerShell validation

To update the default communication cipher that PowerShell will utilize to communicate with a remote server, execute the following command:

[Net.ServicePointManager]::SecurityProtocol = [Net.SecurityProtocolType]::Tls12

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

%d bloggers like this: