Public bug reported:
We should issue an exception here since if a v3 call does not explicitly
specify the domain_id in the entity, it should be using a domain scoped
token. However, the current tempest heat tests issue a v3 call without
this. This is raised as bug #1283539. Once this is fixed, w
** Project changed: tripleo => keystone
** Changed in: keystone
Milestone: queens-2 => None
** Changed in: keystone
Assignee: (unassigned) => Raildo Mascena de Sousa Filho (raildo)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team,
According to your steps, you grant a group role, as you said, domain
admin won't be part of this group, so the behavior is correct. If you
want to domain admin still with this role, you should grant the role for
user and not just for group.
** Changed in: keystone
Status: New => Invalid
-
various auth methods supported by Keystone as well as different Keystone
API versions.
** Affects: glance
Importance: Undecided
Assignee: Raildo Mascena de Sousa Filho (raildo)
Status: In Progress
** Changed in: glance
Assignee: (unassigned) => Raildo Mascena de Sousa Fi
.
** Changed in: keystone
Assignee: (unassigned) => Raildo Mascena de Sousa Filho (raildo)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1506986
Title:
documentation needs to
** Changed in: keystone
Status: New => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1474622
Title:
test submit bug
Status in Keystone:
Invalid
Bug description:
te
The bug is already solved
I tried that way and I got HTTP 400 error, as you may see:
stack@raildo:~/devstack$ glance image-create --name test --location
'swift://example.com/container/obj'
400 Bad Request
Location is missing user:password information.
(HTTP 400)
** Changed in: glance
Public bug reported:
When using inherites roles and the roles list call is made for the
user in the project, with v3, inherited roles are not shown. If we use
v2.0 (v2.0/tenants/{tenant_id}/users/{user_id}/roles) works correctly
and shown the inherited roles.
** Affects: keystone
Importanc
Public bug reported:
When create a user with admin role in a domain 'X' and assigning the
same user role as a member 'Y' domain. When requesting a token in v3
keystone for the 'Y' domain, an error is returned to the user is not
associated with this domain, and the user can not progress.
** Affect
9 matches
Mail list logo