You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am trying to test cyberduck against my OpenStack Swift instance. The authentication URL for it looks like https://host.name/authenticate. When I am creating a new connection the auth URL appears as expected but login always fails. This happens because cyberduck always uses URL https://host.name/v1.0 for authentication, no matter what I typed in the connection creation dialog.
The text was updated successfully, but these errors were encountered:
My Swift instance uses neither swauth nor devauth (aka standard authentication). It is using external auth service which is also used by other services for some time already. Now I need to integrate Swift so have to use existing URL.
Do not you found it a bit strange to require user to play with hidden variables instead of specifying the URL in the dialog?
The need to tinker with hidden preferences is indeed not desirable. As documented, you can change the context path for the authentication. ~~but if you need to use a different hostname you possibly have to redirect on the server. I have not tested if that works.~~~
The host to use for authentication is what you define as the hostname to connect to in the bookmark setting if you have selected Swift (OpenStack Object Storage) with the context path appended. The storage URL is returned from the server upon successful authentication.
I am trying to test cyberduck against my OpenStack Swift instance. The authentication URL for it looks like https://host.name/authenticate. When I am creating a new connection the auth URL appears as expected but login always fails. This happens because cyberduck always uses URL https://host.name/v1.0 for authentication, no matter what I typed in the connection creation dialog.
The text was updated successfully, but these errors were encountered: