The AUTH command takes a single parameter to define the security mechanism to be negotiated. As the SSL/TLS protocols self-negotiate their levels, there is no need to distinguish between SSL and TLS in the application layer. The mechanism name for negotiating TLS is the character string identified in {TLS-PARM}.
On Aug 5, 2020 TLS 1.1 will no longer be supported. Current versions of Internet Explorer and Edge, FireFox, and Google Chrome support the necessary standards. Other browsers and versions may have difficulties. If you are running older applications, testing is advised. (See link below.) Introducing TLS with Client Authentication May 01, 2017 Configure TLS mutual authentication - Azure App Service
Using FTPWEBREQUEST for FTPS (AUTH TLS)
Introducing TLS with Client Authentication
Please Read: TLS 1.2 *GUN PRODUCTION* Upgrade Information
FTP over TLS - FileZilla Wiki If using explicit FTPS, the client connects to the normal FTP port and explicitly switches into secure (TLS) mode with "AUTH TLS", whereas implicit FTPS is an older style service that assumes TLS mode right from the start of the connection (and normally listens on TCP port 990, rather than 21). TLS Certificate - Auth Methods - HTTP API | Vault by HashiCorp »TLS Certificate Auth Method (API) This is the API documentation for the Vault TLS Certificate authentication method. For general information about the usage and operation of the TLS Certificate method, please see the Vault TLS Certificate method documentation.. This documentation assumes the TLS Certificate method is mounted at the /auth/cert path in Vault. #10378 (AUTH TLS command breaking the login on some FTP ==> "AUTH TLS" command is killing the login process on some FTP server when using "Quick Connect" on FileZilla. TLS should not be enforced on simple ftp:// login, or you should add a checkbox to activate/deactivate TLS, just next to the "Quickconnect" button.