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

Support v1.0 Auth requests #49

Closed
clayg opened this issue Jan 9, 2014 · 6 comments
Closed

Support v1.0 Auth requests #49

clayg opened this issue Jan 9, 2014 · 6 comments
Milestone

Comments

@clayg
Copy link

@clayg clayg commented Jan 9, 2014

Keystone pretty quickly moved to v2.0 auth requests, but tempauth [1] never supported it, and with alternative swift auth systems like swauth [2] - v1.0 auth requests have always been the lowest common denominator.

I've seen a few swift clients that have options to support v1.0 and v2.0 auth requests (e.g. swiftly [3], python-swiftclient [4])

I wonder how or where @robert-bor would like to see something like that added to JOSS?

  1. https://github.com/openstack/swift/blob/master/swift/common/middleware/tempauth.py
  2. https://github.com/gholt/swauth
  3. https://github.com/gholt/swiftly/blob/master/swiftly/client/standardclient.py#L205
  4. https://github.com/openstack/python-swiftclient/blob/master/swiftclient/client.py#L265
@robert-bor
Copy link
Contributor

@robert-bor robert-bor commented Jan 10, 2014

Great, thanks for the writeup! I'll study the material during the weekend

@clayg
Copy link
Author

@clayg clayg commented Jan 10, 2014

Should have included the link to the v1.0 auth request docs:

http://docs.openstack.org/api/openstack-object-storage/1.0/content/authentication-object-dev-guide.html#d6e234

I appreciate your interest! I look forward to your thoughts.

@robert-bor
Copy link
Contributor

@robert-bor robert-bor commented Jan 12, 2014

I have read the documentation. Do you happen to have access to a server that works this way? It would help hugely if I can write something and check immediately if it works on that server.

@clayg
Copy link
Author

@clayg clayg commented Jan 12, 2014

@robert-bor sent email, lemme know if you got it ;)

@robert-bor
Copy link
Contributor

@robert-bor robert-bor commented Jan 13, 2014

Yep, got it. Thanks.

I think the best approach would be the following:

  • add an authentication command, effectively resulting in two: Basic authentication and Keystone authentication
  • make sure to have Keystone authentication as the default to ensure backward compatibility
  • allow the Account object to be instantiated with the preferred authentication mechanism

This would also work for the other authentication mechanisms.

What do you think of this approach?

@clayg
Copy link
Author

@clayg clayg commented Jan 13, 2014

Love it! 👏

robert-bor added a commit that referenced this issue Jan 19, 2014
…be Keystone. BASIC authentication can be set by calling setAuthenticationMethod(AuthenticationMethod.BASIC) on the configuration object.
@robert-bor robert-bor closed this Jan 19, 2014
katta pushed a commit to twxkit/joss that referenced this issue Oct 6, 2014
…ll still be Keystone. BASIC authentication can be set by calling setAuthenticationMethod(AuthenticationMethod.BASIC) on the configuration object.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.