add warning to NameCom docs about two-step verification setting (#556)

Posh-ACME/Plugins/NameCom.ps1

@@ -122,7 +122,7 @@ function Remove-DnsTxt {
             Write-Verbose "Removing TXT record for $RecordName with value $TxtValue"
             $url = "$apiRoot/domains/$($domainName)/records/$($rec.id)"
             Write-Debug "DELETE $url"
-            Invoke-RestMethod $url -Method Delete @restParams @script:UseBasic -EA Stop | Out-Null
+            Invoke-RestMethod $url -Method Delete @restParams @script:UseBasic | Out-Null
         } catch { throw }
     } else {
         Write-Debug "Record $RecordName with value $TxtValue doesn't exist. Nothing to do."

docs/Plugins/NameCom.md

@@ -8,6 +8,9 @@ This plugin works against the [name.com](https://www.name.com/) domain registrar
 
 First, go to the [Account API Settings](https://www.name.com/account/settings/api) page and create a new API token for your account. Make a note of both the token value and the username associated with the token. If the username is blank immediately following the token creation, try refreshing the page.
 
+!!! warning
+    If you have two-step verification enabled on your account, there is an additional step to allow the API token to be used. Go to the [Security Settings](https://www.name.com/account/settings/security) page and scroll to the bottom. There is a section called `Name.com API Access` with a slider that need to be set to the "on" position which is to the right. It should be green when set properly. Without it, the API will generate errors about two-step verification not being supported by the API.
+
 ## Using the Plugin
 
 The username is used with the `NameComUsername` parameter and the token is used with the `NameComTokenSecure` SecureString parameter. If you are using name.com's API testing environment, you'll also need to include `NameComUseTestEnv=$true` in your plugin arguments.