roles within domains do not show in auth_ref details
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Identity (keystone) |
New
|
Undecided
|
Unassigned |
Bug Description
I have the following setup:
$ openstack domain list
+------
| ID | Name | Enabled | Description |
+------
| 3eda6a0074144f3
| bb2f7b1a50524d2
| default | Default | True | The default domain |
| e69aa4c1e76b4de
+------
$ openstack project list --domain example.com
+------
| ID | Name |
+------
| f81d9cf81bd7446
+------
$ openstack role list
+------
| ID | Name |
+------
| 14783cf48be5497
| 5140d865c479415
| 7d737800fbb7481
| 8de3b2be221148f
| 8eaed8e42e454b9
| fa51b8f09b5347a
+------
$ openstack role list --domain example.com
+------
| ID | Name | Domain |
+------
| 6e5430e8b875473
| c29ebdcf3803415
+------
openstack role assignment list --user tstark --project operations
+------
| Role | User | Group | Project | Domain | System | Inherited |
+------
| 5140d865c479415
| 6e5430e8b875473
| 8de3b2be221148f
| c29ebdcf3803415
| fa51b8f09b5347a
+------
When I use the python api to scope into the project operations (which resides in the example.com domain), I get these contents for the output of ... sess.auth.
"roles": [
{
"id": "5140d865c47941
"name": "operator"
},
{
"id": "8eaed8e42e454b
"name": "reader"
},
{
"id": "8de3b2be221148
"name": "admin"
},
{
"id": "fa51b8f09b5347
"name": "member"
}
],
Note, the above roles array is constructed like so:
auth_params = {...}
sess = ks_session.
auth_ref = sess.auth.
roles = [{
"id": auth_ref.
"name": auth_ref.
} for i in range(len(
For reference, the contents of auth_ref.
"scope": {
"project": {
"domain": {
"id": "e69aa4c1e76b4d
"name": "example.com"
},
"id": "f81d9cf81bd744
"name": "operations"
}
},
THE ISSUE
- note the reported roles from auth_ref are missing general (example.com) and admin (example.com), but they include all the roles that are not associated with a domain.
- this is despite the fact that the role assignments are clearly defined for these example.com roles
I realize that the auth system is in the middle of a re-work as discussed in https:/
What i want to know is ... is this a bug, or am I missing something?