External Keystone access trying to use Admin URL

Asked by Jesse Pretorius

We've setup external access to Keystone and Nova-API and I'm testing that access. What I find, when doing the command 'keystone --debug service-list' is that the keystone client authenticates to the purlicURL, gets a token, then tries to communicate to the adminURL instead of continuing to talk to the publicURL.

Obviously we have only opened the publicURL for the services for access, so this causes a failure.

Why would it be trying to access the adminURL instead of the publicURL?

Environment: Essex, multi-node

Question information

Language:
English Edit question
Status:
Solved
For:
OpenStack Identity (keystone) Edit question
Assignee:
No assignee Edit question
Solved by:
Jesse Pretorius
Solved:
Last query:
Last reply:
Revision history for this message
Jesse Pretorius (jesse-pretorius) said :
#1

Never mind - I misunderstood the use case. We can auth happily to keystone for other services and keystone's command set shouldn't be used externally. nova, for instance, is totally usable externally.