That would do it! Glad you found your problem.
I'll be working on improving the docs for building your service catalog
pretty soon; common issues like this are useful to know about.
-Dolph
On Fri, Mar 30, 2012 at 11:03 PM, Pete Zaitcev zait...@redhat.com wrote:
On Sat, 31 Mar 2012 10:26:10
Greetings:
It seems that I am unable to authenticate against the current Keystone,
and I am not sure if it is a bug or a local misconfiguration. So, before
I file in Launchpad, I'd like someone to verify that I am doing the
right thing.
The problem looks like this:
[zaitcev@kvm-rei zaitcev]$
First:Make sure you have not set SERVICE_TOKEN and SERVICE_ENDPOINT env since keystone client honours token auth over user/password way.Second: you can use keystone --debug user-list to show what http message sent to serveralso you can see the request body from server log, just like
On Sat, 31 Mar 2012 10:26:10 +0800
Yong Sheng Gong gong...@cn.ibm.com wrote:
also you can see the request body from server log, just like this:
2012-03-31 10:16:44DEBUG [keystone.common.wsgi]
REQUEST BODY
2012-03-31 10:16:44DEBUG
On Sat, 31 Mar 2012 10:26:10 +0800
Yong Sheng Gong gong...@cn.ibm.com wrote:
Second: you can use keystone --debug user-list to show what http message sent
to server
As it turned out, I omitted 's' after the format, because I redone my
old Keystone population script, which did not have any of
5 matches
Mail list logo
