Skip to content

Make rOCCI aware of the WWW-Authenticate header #50

Closed
ffeldhaus opened this Issue Feb 6, 2013 · 3 comments

3 participants

@ffeldhaus
Gesellschaft für wissenschaftliche Datenverarbeitung mbH Göttingen member

rOCCI should use the information provided by the WWW-Authenticate header to select the appropriate authentication method. With it, we could transparently support keystone authentication to the user even though he just provided a username and password.

@ffeldhaus ffeldhaus was assigned Feb 6, 2013
@arax
Gesellschaft für wissenschaftliche Datenverarbeitung mbH Göttingen member
arax commented Feb 7, 2013

WWW-Authenticate header should already be in place on OpenStack's OCCI

$ curl -v -H -H 'Content-Type: text/occi; charset=utf-8' https://<endpoint>:<port>/-/
(...)
< HTTP/1.1 401 Unauthorized
< Date: Thu, 07 Feb 2013 10:28:04 GMT
< Server: Apache
< WWW-Authenticate: Keystone uri='https://<endpoint>:<port>/'
< Content-Length: 381
< Connection: close
< Content-Type: text/html; charset=UTF-8
(...)

Thanks to Álvaro López García for pointing this out.

@arax arax was assigned Mar 1, 2013
@bhagemeier

Hi guys,

according to an email exchange with Boris, this should already be working in rOCCI, but I cannot find anything in the code.

What's the status?

Cheers,
Björn

@arax
Gesellschaft für wissenschaftliche Datenverarbeitung mbH Göttingen member
arax commented Mar 12, 2013

Hi,

sorry, I forgot to reference this issue in the pull request (should be fixed now, although in a different commit). I will merge the pull request shortly and then release 3.1.0.beta.3 for testing purposes.

Cheers

@arax arax added a commit that closed this issue Mar 12, 2013
@arax arax Partially fixes #50, impl in b351c09
* Updated docs
* See b351c09 for OS Keystone impl
* See dabab25 for updated tests
408beca
@arax arax closed this in 408beca Mar 12, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Something went wrong with that request. Please try again.