New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for authentication with Keystone v3 API #8813
Comments
Reference in Identity API v3. |
|
You will need to create a custom connection profile with the authentication path |
@dkocher thanks for the fast reply. Is there a way to test with this code now? Or if not, when will v4.8 be available? |
Please confirm if this works as we haven't done any integration testing with a Keystone v3 deployment. |
Test Results on Cyberduck Version 4.8 (17513) .Tried out Version 4.8 (17513) with 2 different Profiles for HTTP without success -Profile Keystone v3 HTTP(/v3/tokens)*
-Log output (/v3/tokens)*
-Profile Keystone v3 HTTP(/v3/auth/tokens)* -Note: We may need a Placeholder to support domain*
-Log output (/v3/auth/tokens)*
|
@dkocher we are still not able to connect to keystone v3 using cyberduck (17608). Any suggestions on how to debug further? |
@dkocher -Log output:*
|
Fix upstream in 3db505511c1bc100baeb2ee1d862fa4d89c860e1. |
I would like to try the fix, but I am not able to find the build for this change. The latest nightly build for windows is Cyberduck-Installer-4.8.17726.exe, and by trying Preference ->Update ->Snapshot Builds it says "You're up to date!" with User-Agent: Cyberduck/4.8.17726 (Windows 7/6.1) (x86). |
Replying to [comment:19 ariday]:
|
Replying to [comment:20 dkocher]:
Tested Build 4.7.1.17798. Now I do not see any Error Message, but the connection is not established. Log output:
|
|
There seems to be a confusion with naming the |
We can find no example at (http://docs.openstack.org/developer/keystone/api_curl_examples.html) with a object-store type in the service catalog result set. |
Can you provide a temporary integration testing environment? |
@dkocher - can we schedule a joint debug session? We can share screen/conference call to debug. If this works, let me know a day / time that would be convenient. |
@dkocher hi, still want to see if we can set up a meeting with shared screen to debug. Would that work? What time zone are you in? |
Is it possible for you to provide the HTTP response body (JSON formatted) the server sends possibly using the Swift command line tools? |
Log file for Swift Keystonev3 Connection not established 4.7.2 despite HTTP/1.1 200 OK
|
Connection successful with V3 but when trying to create containers a 401 response is shown\
|
Replying to [comment:35 danizar]:
|
Replying to [comment:36 dkocher]:
|
Hi together, Not sure about the current state of this. But besides the region, the profile should also contain an option to specify the used domain (ideally separating user domain and project domain). Many Thanks in advance, |
I would be more than happy to provide you with a test account for a public cloud with Openstack Swift and Identity v3 with domains and projects. Who should I send it to? |
Replying to [comment:39 stenstad]:
|
We have been sending requests with a domain identified by
should instead be
|
Reference upstream changeset. |
A sample profile for zetta.io.
|
Fix in da4aa75f81b. |
Hi. Great news. Would it be possible to have a nightly build with this fix included? |
Replying to [comment:46 Falk Reimann]:
New snapshot builds will become available this week. |
Version 4.8.0.18437 is now available as a snapshot build. |
Hi. I did a quick check with Cyberduck connecting to a OpenStack devstack with keystone v3 enabled. It is still not working for me. I think the main issue is, that Cyberduck uses the UserID as Auth Token instead of the X-Subject-Token after issuing an token from keystone and therefore Swift will not authorize the request. I attached the main information from the log drawer. Can you please revisit this? Token issued from keystone:
Token provided to Swift:
User Id:
Log Drawer output (truncated):
And the user details I used for connection:
|
The documentation documentation has to say
|
In 18867. |
Replying to [comment:53 dkocher]:
Many thanks for the quick response. |
I am using Cyberduck and am able to connect to OpenStack deployments that use keystone v2, but not keystone v3. Is keystone v3 api supported, and if not when is it expected?
Attachments
17608.jpg
(33.5 KiB)cyberduck.log
(216.0 KiB)The text was updated successfully, but these errors were encountered: