openstack team mailing list archive

[Axel Christiansen <axel.christiansen@xxxxxxxxxxxx>]

Thanks for your configs!


Am 05.06.13 15:20, schrieb Matthieu Huin:
> With the config I've sent, the v1 API is accessible at a URL looking like this: http://endpoint:5000/v1.0
> 
> What do you get in the keystone logs when you send a cURL request like
> 
> curl -H "x-auth-user: tenant:user" -H "x-auth-key: password" http://endpoint:5000/v1.0
> 
> ?


When using valid credentials the promt just appears again. No output.
2013-06-05 15:39:54,114 INFO sqlalchemy.engine.base.Engine INSERT INTO
token (id, expires, extr ......

When using invalid credentials:
{"error": {"message": "Invalid user / password", "code": 401, "title":
"Not Authorized"}}




When using Cyberduck the keystone seems not to get touched at all.

This ist what appears in the proxy.log wehen trying to login via Cyberduck:

Jun  5 15:47:03 ns-proxy01 swift-proxy Calling Swift3 Middleware (txn:
tx439bd9050f054697b722c4b0db5a4219)
Jun  5 15:47:03 ns-proxy01 swift-proxy {'headers': {'Accept-Encoding':
'gzip,deflate', 'Host': 'backend', 'X-Auth-User': 'demo:admin',
'User-Agent': 'Cyberduck/4.3 (Mac OS X/10.8.3) (i386)', 'Connection':
'close', 'X-Auth-Key': 'XZ5OOQSKWSNJ', 'Content-Type': None}, 'environ':
{'SCRIPT_NAME': '', 'HTTP_X_AUTH_KEY': 'XZ5OOQSKWSNJ', 'REQUEST_METHOD':
'GET', 'PATH_INFO': '/auth/v1.0', 'SERVER_PROTOCOL': 'HTTP/1.0',
'wsgi.url_scheme': 'http', 'HTTP_USER_AGENT': 'Cyberduck/4.3 (Mac OS
X/10.8.3) (i386)', 'HTTP_CONNECTION': 'close', 'REMOTE_PORT': '41624',
'SERVER_NAME': '10.42.44.101', 'REMOTE_ADDR': '10.42.44.5',
'eventlet.input': <eventlet.wsgi.Input object at 0x1fe4c10>,
'HTTP_X_AUTH_USER': 'demo:admin', 'SERVER_PORT': '8888', 'wsgi.input':
<swift.common.utils.InputProxy object at 0x1fe4c90>, 'HTTP_HOST':
'backend', 'swift.cache': <swift.common.memcached.MemcacheRing object at
0x28c30d0>, 'wsgi.multithread': True, 'eventlet.posthooks': [],
'wsgi.version': (1, 0), 'RAW_PATH_INFO': '/auth/v1.0',
'GATEWAY_INTERFACE': 'CGI/1.1', 'wsgi.run_once': False, 'wsgi.errors':
<swift.common.utils.LoggerFileObject object at 0x188c450>,
'wsgi.multiprocess': False, 'swift.trans_id':
'tx439bd9050f054697b722c4b0db5a4219', 'CONTENT_TYPE': None,
'HTTP_ACCEPT_ENCODING': 'gzip,deflate'}}
Jun  5 15:47:03 ns-proxy01 swift-proxy Authorizing as anonymous (txn:
tx439bd9050f054697b722c4b0db5a4219)
Jun  5 15:47:03 ns-proxy01 swift-proxy 10.42.44.5 10.42.44.5
05/Jun/2013/13/47/03 GET /auth/v1.0 HTTP/1.0 401 -
Cyberduck/4.3%20%28Mac%20OS%20X/10.8.3%29%20%28i386%29 - - 131 -
tx439bd9050f054697b722c4b0db5a4219 - 0.0008 -



> 
> 
> Matthieu Huin 
> 
> mhu@xxxxxxxxxxxx
> 
> ----- Original Message -----
> From: "Axel Christiansen" <axel.christiansen@xxxxxxxxxxxx>
> To: "Matthieu Huin" <matthieu.huin@xxxxxxxxxxxx>
> Cc: openstack@xxxxxxxxxxxxxxxxxxx
> Sent: Wednesday, June 5, 2013 3:10:22 PM
> Subject: Re: [Openstack] grizzly keystone with v1.0 API
> 
> 
> yes, i added these files and they do get compiled and invoked. (added
> some more debug code). At least an object of ProtocolConverter gets
> created, but the converter methods never get called.
> 
> 
> The grizzly keystone tar archive does not come with a
> keystone-paste.ini. What i can tell so fare, the contents of
> keystone-paste.ini is included in keytone.conf. And that should be fine.
> 
> I got myself a devstack now, adopted keystone and its configs into the
> grizzly openstack and still have no luck.
> 
> Axel
> 
> 
> 
> Am 05.06.13 12:23, schrieb Matthieu Huin:
>> Did you add these files to your keystone installation ? https://github.com/AlexYangYu/StackLab-Ketystone/commit/9e126d6716912e8822de3884c32f5b9509ef0994 (you only need the first two files)
>> Then you have to modify keystone-paste.ini and restart keystone.
>>
>> Matthieu Huin 
>>
>> mhu@xxxxxxxxxxxx
>>
>> ----- Original Message -----
>> From: "Axel Christiansen" <axel.christiansen@xxxxxxxxxxxx>
>> To: "Matthieu Huin" <matthieu.huin@xxxxxxxxxxxx>
>> Cc: openstack@xxxxxxxxxxxxxxxxxxx
>> Sent: Wednesday, June 5, 2013 12:14:32 PM
>> Subject: Re: [Openstack] grizzly keystone with v1.0 API
>>
>> Thank you Matthieu,
>>
>>
>> that sounds very interesting. The grizzly i am using comes with an "all
>> in one keystone.conf". I think that is fine and should work.
>>
>> Would you be so kind and send me your "/etc/keystone/keystone.conf" and
>> "/etc/keystone/keystone-paste.ini". I would like to compare these to
>> mine and hope it brings me a lot closer.
>>
>>
>> Yes, thats what i ment on the zmanda-blog.
>>
>>
>> Thnak you!
>>
>>
>> Axel
>>
>>
>>
>> Am 05.06.13 11:30, schrieb Matthieu Huin:
>>> Hello Axel,
>>>
>>> If you refer to this post : http://www.zmanda.com/blogs/?p=1002 , I managed to set it up successfully on a devstack ( that's the trunk version, though, not grizzly ). There is a mistake in the instructions; the config file to modify is not /etc/keystone/keystone.conf but /etc/keystone/keystone-paste.ini .
>>>
>>> Hope that helps.
>>>
>>> Matthieu Huin 
>>>
>>> mhu@xxxxxxxxxxxx
>>>
>>> ----- Original Message -----
>>> From: "Axel Christiansen" <axel.christiansen@xxxxxxxxxxxx>
>>> To: openstack@xxxxxxxxxxxxxxxxxxx
>>> Sent: Wednesday, June 5, 2013 11:23:13 AM
>>> Subject: [Openstack] grizzly keystone with v1.0 API
>>>
>>> Hello List again,
>>>
>>>
>>> on the zmanda-blog is a description to make a swift/keystone setup work
>>> again via the v1.0 API. Had anyone success doing this on grizzly?
>>>
>>> I sadly did not.
>>>
>>>
>>> Regards, Axel
>>>
>>> _______________________________________________
>>> Mailing list: https://launchpad.net/~openstack
>>> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
>>> Unsubscribe : https://launchpad.net/~openstack
>>> More help   : https://help.launchpad.net/ListHelp
>>>
>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~openstack
>> Post to     : openstack@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~openstack
>> More help   : https://help.launchpad.net/ListHelp
>>
>