openstack team mailing list archive

Thread
Date

[keystone] Why are we returing such a big payload in validate token?

To: OpenStack Development Mailing List <openstack-dev@xxxxxxxxxxxxxxxxxxx>
From: "Ali, Haneef" <haneef.ali@xxxxxx>
Date: Fri, 1 Feb 2013 00:44:34 +0000
Accept-language: en-US
Cc: "openstack@xxxxxxxxxxxxxxxxxxx" <openstack@xxxxxxxxxxxxxxxxxxx>
Thread-index: Ac4AFUeNSJEkJy4rQ9ydS2Un0KFXjQ==
Thread-topic: [keystone] Why are we returing such a big payload in validate token?

Hi,

As of now  v3  validateToken response has "tokens, service catalog, users, project , roles and  domains.  (i.e)  Except for groups we are returning everything.  We also discussed about the possibility of 100s of endpoints.  ValidateToken is supposed to be a high frequency call .    This is going to be a huge performance impact . What is the use case  for such a big payload  when compared with v2?

If a service needs catalog , then the service can always ask for the catalog.

Thanks
Haneef

Follow ups

Re: [keystone] Why are we returing such a big payload in validate token?
From: Adam Young, 2013-02-01
Re: [keystone] Why are we returing such a big payload in validate token?
From: Jay Pipes, 2013-02-01