Ask Your Question

Not getting Keystone token via http but am getting it thru keystone client

asked 2013-07-15 15:06:38 -0500

kam gravatar image

updated 2013-07-15 15:41:03 -0500

smaffulli gravatar image

Kinda of new to this so it is probably easy but....

I send this

curl -k -X 'POST' -v
-d '{"auth":{"passwordCredentials":{"username": "admin", "password":"admin_pass"}, "tenantId":""}}' -H 'Content-type: application/json'

and get:

{"error": {"message": "The request you have made requires authentication.", "code": 401, "title": "Not Authorized"}}

but I download the keystone client on the same machine. Run this:

keystone --os-username=admin --os-password=admin_pass --os-auth-url= token-get

and get (the box-lines and spaces are omitted here):


Same URL, same ID same pass. Why doesn't the HTTP version work? Kevin

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted

answered 2014-06-13 09:09:40 -0500

Rakesh Patnaik gravatar image

updated 2014-06-13 09:10:07 -0500

I guess its the "tenantId":"" in the json payload that is making the REST API look for a user "admin" under tenant "" which does not exist. I tried the same and got a similar error as yours. Remove it and it works:

curl -k -X 'POST' -v -d '{"auth":{"passwordCredentials":{"username": "admin", "password":"admin_pass"}}}' -H 'Content-type: application/json'

without the "tenantName" or "tenantId" keystone API returns an empty serviceCatalog.

edit flag offensive delete link more

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Get to know Ask OpenStack

Resources for moderators

Question Tools


Asked: 2013-07-15 15:06:38 -0500

Seen: 921 times

Last updated: Jun 13 '14