David Kocher

> This has been resolved in the latest update (8-5-6), we tested this a couple of days ago. I assume you refer to #13725.

To allow connecting without the need for configuration using AWS CLI we are dependent on proper OIDC support in AWS SSO. > The IAM Identity Center OIDC service currently implements...

> @michael-crawford, this is how we use Cyberduck. > > We have multiple AWS accounts, our Cyberduck users have an AWS config files with the necessary role to assume in...

> I agree with this - if this is needed for these types of profile to work, then it should be a different type of S3 connection, and include that...

Log output from #13343. ``` 2022-07-07 16:46:16,684 [background-16] DEBUG ch.cyberduck.core.sftp.SFTPSession$LoggingSFTPEngine - Sending Request{39;OPENDIR} 2022-07-07 16:46:16,686 [background-15] WARN ch.cyberduck.core.pool.StatelessSessionPool - Keep connection Session{host=Host{protocol=Profile{parent=sftp, vendor=iterate GmbH, description=null, image=null}, port=22, hostname='104.236.120.137', credentials=Credentials{user='master_swvtbadraz', oauth='OAuthTokens{accessToken='null',...

Can you let me know if you can reproduce in 8.6.0.

Disabling _Preferences → Cryptomator → Auto detect and open vault in browser_ will probably display a slightly different error message but the underlying cause seems to be the idle timeout...

> Could you elaborate a bit more on concrete use cases? In what scenarios would the client not be able to persist upload URLs but still be interested in resuming...

My intention was to allow for easier client implementations without the requirement for storage. Looking at the overall picture I agree keeping the protocol lean should probably be the priority...

Not sure how to update the code coverage report with updated results from the force pushed commit.