Listing projects with OSClientV3 resolves to "/v2.0/projects" GET request

[ScottMaclure]

As per the docs here:
http://www.openstack4j.com/learn/identity/identity-v3/#projects

Using OSClientV3 (scoped to domain):

OSClientV3 os = OSFactory.builderV3()... etc.

List<? extends Project> projectList = os.identity().projects().list();

Debugging now, but have confirmed this locally with v3.0.2.

If I change the endpoint in the debugger to "v3/projects", I get back a project list. Otherwise, an empty collection is returned.

Will update when I dig further.

Edit1: KeystoneEndpoints configured for v3 service with v2.0 URLs?

[auhlig]

I guess the error's cause can be found in the token catalog. Can you check you configured identity v3 properly and the endpoint, found in the catalog, is correct and ending with /v3 ?

[ScottMaclure]

For configuration, currently I do:

OSClientV3 os = OSFactory.builderV3()
    .endpoint(someUrl)
    .credentials(username, password, domainIdentifier)
    .scopeToProject(projectIdentifier)
    .authenticate();

Can see the endpoint with v3 and the catalog with v2:

Am I missing a configuration step somewhere?

[auhlig]

Short: That screenshot confirms my suspicion. You only have one keystone available in the catalog which points to the wrong keystone v2 endpoints. You have to configure the OpenStack instance properly and setup a Keystone V3 service. But that is more about OpenStack itself than it is for OpenStack4j.

[ScottMaclure]

Thanks - I will ask the vendor - I will close the issue for now, and re-open if needed.