Re: .Net assembly S3 connection issue : "Authentication failed.The request signature we calculated.....
Please attach session log files both from the GUI and the code.
- martin
Post a reply
Before posting, please read how to report bug or request support effectively.
Bug reports without an attached log file are usually useless.
Topic review
- jsytniak
.Net assembly S3 connection issue : "Authentication failed.The request signature we calculated.....
I have encountered S3 connection issues with the .Net assembly. The WinSCP GUI on the surface does not appear to have S3 connection issues.
An examination of logs between scripts using the .Net assembly and GUI logs seems to indicate that the GUI also has a similar connection issue but some workaround has been coded into the GUI to overcome the connection issue. There appears to be a series of retries that occurs with the GUI connection.
Until this is worked out in the .Net assembly, usage for scripting S3 operations is not an option for me.
Of note... I pivoted to making use of the AWS SDK .Net assemblies and initially would get the same connection issue... Identical error message..... "Authentication failed.The request signature we calculated does not match the signature you provided. Check your key and signing method.". Upon using the AWS SDK S3 request method that use stored creds, I was able to overcome the auth issue.
An examination of logs between scripts using the .Net assembly and GUI logs seems to indicate that the GUI also has a similar connection issue but some workaround has been coded into the GUI to overcome the connection issue. There appears to be a series of retries that occurs with the GUI connection.
Until this is worked out in the .Net assembly, usage for scripting S3 operations is not an option for me.
Of note... I pivoted to making use of the AWS SDK .Net assemblies and initially would get the same connection issue... Identical error message..... "Authentication failed.The request signature we calculated does not match the signature you provided. Check your key and signing method.". Upon using the AWS SDK S3 request method that use stored creds, I was able to overcome the auth issue.