Closed spellingb closed 5 years ago
:x: Build ArmorPowerShell 1.0.318-dlktrrqt failed (commit https://github.com/tlindsay42/ArmorPowerShell/commit/6f21046569 by @brandonspell08)
":x: Build ArmorPowerShell 1.0.318-dlktrrqt failed (commit https://github.com/tlindsay42/ArmorPowerShell/commit/6f21046569 by @brandonspell08)"
:white_check_mark: Build ArmorPowerShell 1.0.333-iecmnbft completed (commit https://github.com/tlindsay42/ArmorPowerShell/commit/0dd3cf9517 by @tlindsay42)
":white_check_mark: Build ArmorPowerShell 1.0.333-iecmnbft completed (commit https://github.com/tlindsay42/ArmorPowerShell/commit/0dd3cf9517 by @tlindsay42)"
Description
Modified Armor.psm1 to enable TLS 1.2 support during import. This is necessary as api.armor.com no longer supports protocols below TLS 1.2
Added test to Module.Tests.ps1 to test TLS 1.2 import
Related Issue
https://github.com/tlindsay42/ArmorPowerShell/issues/153
Motivation and Context
api.armor.com no longer supporst protocols below TLS 1.2. In order to use the ArmorPowerShell Module, a user must first enable TLS 1.2 in their powershell session
This change will enable TLS 1.2 in the user session during the Module import, while not changing the user's pre-existing Protocol settings
Testing Procedure
Screenshots (optional)
Please insert screenshots here.![image](https://user-images.githubusercontent.com/20215364/59645269-9aa0c600-9136-11e9-9379-b227a876d84f.png)
Types of changes
What types of changes does your code introduce? Put an
x
in all the boxes that apply:Checklist
Go over all the following points, and put an
x
in all the boxes that apply. If you're unsure about any of these, don't hesitate to ask. We're here to help!