Unimplemented error on V3 get token

[Marcos Lobo]

Configuring keystone on V3 with LDAP configured for Assignment and Identity

If you try this curl command:

$ curl -i -X POST https://theserver:5000/v3/auth/tokens -H "Content-Type: application/json" -d '{"auth": {"identity": {"methods": ["password"], "password": {"user": {"domain": {"name": "Default"}, "name": "USERNAME", "password": "PASSWORD"}}}}}' --insecure

The response is:

{"error": {"message": "The action you have requested has not been implemented.", "code": 501, "title": "Not Implemented"}}

This is the log info http://paste.openstack.org/show/63030/

[Dolph Mathews (dolph)]

What's raising a NotImplemented in the service-side logs? Which identity driver are you using?

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.openstack.org/71887

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/71887
Committed: https://git.openstack.org/cgit/openstack/keystone/commit/?id=60a570e2bb04126a8b90ec4f554be57f7259ac2a
Submitter: Jenkins
Branch: master

commit 60a570e2bb04126a8b90ec4f554be57f7259ac2a
Author: Marcos Lobo <email address hidden>
Date: Fri Feb 7 13:51:18 2014 +0100

    Unimplemented error on V3 get token

    Configuring keystone on V3 with LDAP configured for Assignment and
    Identity. When you try to obtain the token (using CURL ie), the keystone
    server raises an unimplemented exception. You can see how to reproduce
    this on the description's bug.

    This is caused because, when you make logging on keystone it assign to
    the validate user the 'default' domain (thats because LDAP is
    single-domain backend). In the LDAP backend, one of the functions
    involved on this workflow is not implemented.

    Change-Id: I04faddf888f66978bfe5a330140f8fac9b961a5a
    Closes-Bug: #1277463