`os_admin_project_domain_name` in configuration is not reflected
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Blazar |
Fix Released
|
Medium
|
Unassigned |
Bug Description
As it is noted in blazar sample configuration [1], we have the following options.
* os_admin_
* os_admin_
[1] https:/
They are used for keystone authentication.
However, the ``os_admin_
This is because internally in the blazar server ``os_admin_
This doesn't affect users who set neither of the values explicitly in the cofiguration file,
because the default values of the options are both set to "Default".
But this affect users who set either of the values explicitly.
Changed in blazar: | |
importance: | Undecided → Medium |
milestone: | none → rocky-3 |
Reviewed: https:/ /review. openstack. org/578029 /git.openstack. org/cgit/ openstack/ blazar/ commit/ ?id=3a7f6303aea 22ab1c589329fa6 1701b5b09e0f34
Committed: https:/
Submitter: Zuul
Branch: master
commit 3a7f6303aea22ab 1c589329fa61701 b5b09e0f34
Author: Tetsuro Nakamura <email address hidden>
Date: Tue Jun 26 17:45:58 2018 +0900
Correct the project domain option for authorization
In blazar configuration, we have the following options:
* os_admin_ user_domain_ name project_ domain_ name
* os_admin_
They are used for Keystone authentication, but admin_project_ domain_ name`` in the configuration file was not admin_user_ domain_ name" for both *project* and *user* domain name.
``os_
reflected in Blazar. This is because the Blazar service used
``os_
This patch fixes the bug and adds related tests.
Change-Id: Ifbca9f622afba3 aa9f41296fff2d3 4afce22da0a
Closes-Bug: #1779660