Adds default domain name to dashboard login params
Desc:
The current tempest configs requires a new property for the version of
Keystone that Horizon is set too. The login screen will require a
domain name when Horizon's local_settings.py is set to Keystone v3 with
multi-domain support enabled.
Details:
The Keystone API runs both version 2 and version 3 concurrently.
They are not compatible and have different methods of authentication.
Clients can choose which version of the API to talk to. (i.e. choosing
the endpoint)
Horizon (The OpenStack Dashboard) uses the Keystone Client binding to
authenticate to the Keystone API. Too choose which version of the
Keystone API to use there are settings in Horizon.
When Horizon's settings are configured to talk to the Keystone V3 API
the login screen will require additional credentials. Namely the the
domain name of the user. When this is omitted, authentication will fail.
The user will not be able to login and view the Overview screen.
Tempest has a scenario test that assumes Horizon will be configured to
use Keystone V2. This tests fails when Horizon is configured to use
Keystone V3.
The Proposed Fix:
Pass an additional request param to the login form that will allow
this scenario test to work for both keystone v2 and keystone v3.
Reviewed: https:/ /review. openstack. org/264354 /git.openstack. org/cgit/ openstack/ tempest/ commit/ ?id=a6aa1aa6d09 583ecd71f2e0bcf ee7dee74debad2
Committed: https:/
Submitter: Jenkins
Branch: master
commit a6aa1aa6d09583e cd71f2e0bcfee7d ee74debad2
Author: daniel-a-nguyen <email address hidden>
Date: Wed Jan 6 13:15:21 2016 -0800
Adds default domain name to dashboard login params
Desc:
The current tempest configs requires a new property for the version of
Keystone that Horizon is set too. The login screen will require a
domain name when Horizon's local_settings.py is set to Keystone v3 with
multi-domain support enabled.
Details:
The Keystone API runs both version 2 and version 3 concurrently.
They are not compatible and have different methods of authentication.
Clients can choose which version of the API to talk to. (i.e. choosing
the endpoint)
Horizon (The OpenStack Dashboard) uses the Keystone Client binding to
authenticate to the Keystone API. Too choose which version of the
Keystone API to use there are settings in Horizon.
When Horizon's settings are configured to talk to the Keystone V3 API
the login screen will require additional credentials. Namely the the
domain name of the user. When this is omitted, authentication will fail.
The user will not be able to login and view the Overview screen.
Tempest has a scenario test that assumes Horizon will be configured to
use Keystone V2. This tests fails when Horizon is configured to use
Keystone V3.
The Proposed Fix:
Pass an additional request param to the login form that will allow
this scenario test to work for both keystone v2 and keystone v3.
Closes-Bug: #1531594 872b065c94d3125 5b0dc1750fc
Change-Id: I060a7ceb19c2c2