[Openstack] Keystone, pki tokens and memcache
Sam Morrison
sorrison at gmail.com
Mon Jun 17 23:23:59 UTC 2013
On 18/06/2013, at 1:18 AM, Adam Young <ayoung at redhat.com> wrote:
> On 06/17/2013 12:27 AM, Sam Morrison wrote:
>> I'm currently looking into Grizzly and have been having some issues getting PKI tokens to work.
>>
>> If I have memcache as the token backend keystone issues uuid based tokens, if I have sql as the backend then it issues PKI tokens.
>>
>> Does this mean you can't use memcache backend if you want to use PKI tokens?
>>
>> Cheers,
>> Sam
>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~openstack
>> Post to : openstack at lists.launchpad.net
>> Unsubscribe : https://launchpad.net/~openstack
>> More help : https://help.launchpad.net/ListHelp
> You are making additional configuration changes beyond the Backend. The config options for PKI vs UUID is defined in keystone/common/config.py
>
>
> 'token_format', group='signing', default="PKI"
>
> The Backend is in the same place:
>
> 'driver', group='token', default='keystone.token.backends.sql.Token'
>
>
> So to set UUID tokens, in the config file,
> [signing]
> token_format=UUID
>
> or explicitly
>
> [signing]
> token_format=PKI
Yeah I had token_format set. I switched back to memcache and it started working, not sure what is going on there. Will see if I can replicate.
Cheers,
Sam
More information about the Openstack
mailing list