On 07/30/2014 10:57 AM, Dolph Mathews wrote:
We recently merged an implementation for GET /v3/catalog which finally
enables POST /v3/auth/tokens?nocatalog to be a reasonable default
behavior, at the cost of an extra HTTP call from remote service back to
keystone where necessary.
Is that
On Thursday, July 31, 2014, Russell Bryant rbry...@redhat.com wrote:
On 07/30/2014 10:57 AM, Dolph Mathews wrote:
We recently merged an implementation for GET /v3/catalog which finally
enables POST /v3/auth/tokens?nocatalog to be a reasonable default
behavior, at the cost of an extra HTTP
Yes, it's a change in default client-side behavior (the client can
explicitly request ?nocatalog). The default server-side behavior is to
continue returning catalogs in requests unless the client requests
otherwise. Before the client adopts the new default, we need
well-established support in
We recently merged an implementation for GET /v3/catalog which finally
enables POST /v3/auth/tokens?nocatalog to be a reasonable default behavior,
at the cost of an extra HTTP call from remote service back to keystone
where necessary.
Spec:
