Comment 5 for bug 1309180

> If it designed for not working from external net then why it is works when external `endpoint' is specified?

See below - I'm assuming you mean "public" instead of "external" throughout this report, but some calls work on both interfaces (auth, etc), some calls work only one the public interface (see below), and the bulk of the API only works on the admin interface (but these are also the least frequently hit calls).

> If it designed for working from external network then why it is trying to use internalURL/adminURL?

It's trying to use the admin URL because you're trying to make an admin-only call. Most of the v2 API is non-public. The public API *does* support a GET :5000/v2.0/tenants call, but it's entirely different from the GET :35357/v2.0/tenants call, and may be exposed differently by the client library.

> I can't find any documentation about `endpoint' and adminURL/internalURL/externalURL. Seems like this 3 urls are useless, and only one url can be used.

There's actually not an "externalURL" defined anywhere - although that's an entirely appropriate name, it's defined by the specification as a "public" URL. The v3 API likely has the provides the definitions: https://github.com/openstack/identity-api/blob/master/openstack-identity-api/v3/src/markdown/identity-api-v3.md