Skip to content
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

Authentication failure with ec2-credentials #7754

Closed
cyberduck opened this issue Jan 22, 2014 · 7 comments
Closed

Authentication failure with ec2-credentials #7754

cyberduck opened this issue Jan 22, 2014 · 7 comments

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Jan 22, 2014

ebe32ff created the issue

https://svn.cyberduck.ch/trunk/profiles/Openstack%20Swift%20(Keystone%20HTTP).cyberduckprofile

I downloaded this profile so I could connect to our internal swift POC installation but the profile is not connecting.

My settings are:

  • auth server is:
server:10.68.240.191
port:5000 (swift on 8888)
  • keystone ec2-credentials-list gives me:
usrname: f03ec1aa7ed443e7bbb4af9c5ab75b59:e4725694a1d841e28b083084abb821ae
secretkey: XXXXXXXXXX
  • also tried these options
path: NULL, /v2.0, /v2.0/tokens

can anyone suggest where I am going wrong?


Attachments

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jan 23, 2014

@dkocher commented

We currently default to a passwordCredentials request for keystone authentication which explains why the request is failing with 403 given the secret key. We should make this configurable and default to the method used by a default installation stack.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jan 23, 2014

ebe32ff commented

So I am a bit confused. Please note that this is the Openstack Swift (Keystone HTTP) profile and not the Openstack Swift (Keystone) profile which uses https. The profile calls for:

  • server and port - should I use keystoneip/keystoneport (10.x.x.x:5000) or swiftproxyip:swiftproxyport (10.x.x.x:8888)
  • username [TennantID:AccessKey] - should I use TennantID:EC2AccessID or username or userid
  • password [SecretKey] - you suggest passwordCredentials so should I use the user password instead of the EC2SecretKey

an example or corresponding screenshot would help if you have some instruction to follow

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jan 23, 2014

@dkocher commented

Yes, try to use the password instead of the secret key as in

  • Username tenant:username
  • Password password

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jan 24, 2014

ebe32ff commented

This worked fine, thank you

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Mar 26, 2014

@dkocher commented

You do not need to give the authentication context in the Path option.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Mar 26, 2014

@dkocher commented

We are supporting multiple authentication strategies as of f1f2faf. Please update to the latest snapshot build available.

@cyberduck cyberduck closed this Mar 26, 2014
@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Mar 26, 2014

@dkocher commented

You can either provide

  • (Tenant ID:)Username and Password
  • (Tenant Name:)Username and Password
  • (Tenant ID:)Access Key and secret key

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants