Re: [Openstack] glance keystone authentication problem

2012-05-12 Thread Shashi Kanth Boddula
# cat /etc/keystone/keystone.conf [DEFAULT] bind_host = 0.0.0.0 public_port = 5000 admin_port = 35357 admin_token = 012345SECRET99TOKEN012345 compute_port = 8774 verbose = True debug = True log_config = /etc/keystone/logging.conf # cat /etc/glance/glance-api-paste.ini [filter:authtoken] paste.f

Re: [Openstack] glance keystone authentication problem

2012-05-12 Thread Dolph Mathews
The admin_token config is being used to bypass to normal authentication process, thereby avoiding the issue. Can you paste the rest of your authtoken config? Also, try token-get against 5000, and then try the resulting token as your admin_token value. -Dolph Mathews On May 12, 2012, at 12:01 P

Re: [Openstack] glance keystone authentication problem

2012-05-12 Thread Shashi Kanth Boddula
# keystone user-list +--+-+---++ |id| enabled | email | name | +--+-+---++ | 76a3cb1e5e7a427d8272838fc0a759fc | True| None | nova | | a19e7f6975984e7fa6c8

Re: [Openstack] glance keystone authentication problem

2012-05-12 Thread Dolph Mathews
I think the key is this line: 2012-05-11 10:03:11 18461 INFO [keystone.middleware.auth_token] Keystone rejected admin token {'X-Auth-Token': u' 6f220a2e7e324bf4bd7a96040f364316'}, resetting It looks like your auth_token middleware isn't properly authenticating itself with keystone. Verify tha

Re: [Openstack] glance keystone authentication problem

2012-05-12 Thread Shake Chen
you can check your keystone whether work correctly. keystone user-list On Fri, May 11, 2012 at 12:42 PM, Shashi Kanth Boddula wrote: > Ubuntu 12.04 Essex. > > # glance index > Failed to show index. Got error: > You are not authenticated. > Details: 401 Unauthorized > > This server could not v

[Openstack] glance keystone authentication problem

2012-05-10 Thread Shashi Kanth Boddula
Ubuntu 12.04 Essex. # glance index Failed to show index. Got error: You are not authenticated. Details: 401 Unauthorized This server could not verify that you are authorized to access the document you requested. Either you supplied the wrong credentials (e.g., bad password), or your browser does