identity: use token_provider with UUID

- token_provider is the new param that we should use.
- UUID is not the best option, but more work needs to be done on
  cloud::identity to ensure keystone uses the same certificate when
using PKI driver.

Close #75

Signed-off-by: Emilien Macchi <emilien.macchi@enovance.com>
This commit is contained in:
Emilien Macchi 2014-01-28 11:54:36 +01:00
parent 6153c637eb
commit 526d31891a
2 changed files with 2 additions and 2 deletions

View File

@ -399,7 +399,7 @@ class cloud::identity (
memcache_servers => $memcache_servers,
sql_connection => "mysql://${encoded_user}:${encoded_password}@${keystone_db_host}/keystone",
token_driver => 'keystone.token.backends.memcache.Token',
token_provider => 'keystone.token.providers.pki.Provider',
token_provider => 'keystone.token.providers.uuid.Provider',
use_syslog => true,
verbose => $verbose,
bind_host => $api_eth,

View File

@ -101,7 +101,7 @@ describe 'cloud::identity' do
:memcache_servers => ['10.0.0.1','10.0.0.2'],
:sql_connection => 'mysql://keystone:secrete@10.0.0.1/keystone',
:token_driver => 'keystone.token.backends.memcache.Token',
:token_provider => 'keystone.token.providers.pki.Provider',
:token_provider => 'keystone.token.providers.uuid.Provider',
:use_syslog => true,
:bind_host => '10.0.0.1',
:public_port => '5000',