Ask Your Question

Should not be version of identity API included in service-catalog?

asked 2016-12-05 07:00:56 -0500

jbouska gravatar image

I have a running OS instance. When I call openstack catalog list command I get

| keystone    | identity       | RegionOne                                                               
|             |                |   admin:                          
|             |                | RegionOne                                                                      
|             |                |   public:                                    
|             |                | RegionOne                                                                      
|             |                |   internal:

But If I use URI from this table I get response with status code 404.

example: curl --header "X-Auth-Token: TOKEN"

To make this feature work I have to use following command:

curl --header "X-Auth-Token: TOKEN"

Should not be the API version in service catalog included or I have to append this version to URI from the service catalog?

edit retag flag offensive close merge delete

1 answer

Sort by ยป oldest newest most voted

answered 2016-12-06 15:10:10 -0500

volenbovsky gravatar image

Hi, the recommended approach is indeed to have unversioned URL as endpoints in catalog. That is from So your deployment tool apparently did it this way.

And then in same page: "If you were to perform a GET against either of these endpoints, you would be greeted by an HTTP/1.1 300 Multiple Choices response, which newer Keystone clients can use to automatically detect available API versions."

So, that doesn'tmean that you can use REST API on something like http://URL/identity/projects, that is without V2 or V3 in path, and that's how it is described in - /v3 is always there.

edit flag offensive delete link more

Get to know Ask OpenStack

Resources for moderators

Question Tools

1 follower


Asked: 2016-12-05 07:00:56 -0500

Seen: 96 times

Last updated: Dec 06 '16