S3 connector - Continuous alerting if SSL certificate is valid for only bucket adresses
We have an installation of S3 server in which each bucket is targeted with an address like .
The SSL certificate is valid for "*.s3.company.com", but the root is not tought to be accessible from outside and its address (from inside company's network) is "s3.company.com", which is not valid for the wildcard certificate .
The result is that each time a request is done (open a folder, upload or download a file, etc.) a dozen of alerts is shown, with a message like
After clicking "Yes" on all promtped warnings, normally the operations conludes successfully, but all that clicking makes WinSCP unusable...
bucket.s3.company.com
The SSL certificate is valid for "*.s3.company.com", but the root is not tought to be accessible from outside and its address (from inside company's network) is "s3.company.com", which is not valid for the wildcard certificate
*.s3.company.com
The result is that each time a request is done (open a folder, upload or download a file, etc.) a dozen of alerts is shown, with a message like
, locking all the opened sessions until you click "Yes" dozens of time for each operation.The server certificate is unknown. There are no warranties that the server is who declares to be [...] if you trust it and want to store the certificate click [Yes]
After clicking "Yes" on all promtped warnings, normally the operations conludes successfully, but all that clicking makes WinSCP unusable...
- winscp-error.png (16.89 KB)
