yahoo-eng-team team mailing list archive

[Dolph Mathews <1177241@xxxxxxxxxxxxxxxxxx>]

Similar answer from the keystone side - we're getting further away from
the "default project" thing. In v3, we're viewing a user's default
project as simply a user-defined preference: the project which the user
should authorize against if the user didn't request a specific project.

User-Project assignments are done via discrete user-project role
assignments. In v2, keystone internally assigns a "_member_" role to the
user's "default tenant" attributes (i.e. creating an explicit role
assignment during user-create) as a means of backwards compatibility.

So, moving forward, you'll need to do explicit role assignments after
the user is created, which means that horizon's UI may naturally go
multi-project or leave that as a separate workflow.

** Changed in: keystone
       Status: New => Won't Fix

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Dashboard (Horizon).
https://bugs.launchpad.net/bugs/1177241

Title:
  Cannot assign multiple tenants to a user when creating a user

Status in OpenStack Dashboard (Horizon):
  Won't Fix
Status in OpenStack Identity (Keystone):
  Won't Fix

Bug description:
  The CLI and Dashboard dont permit a single user being assigned multiple projects during user creation.
  CLI command
  # keystone user-create
  doesn't allow a user to be assigned multiple tenants/projects. 

  The same is true from dashboard using "Create User" options which
  allows only one primary project to be created and not mulitple ones.

  Currently the only way to assign multiple projects to a user is to:

  use the projects tab on the dashboard, and modify users for the
  required project.

  Is it not a valid usecase to assign multiple tenants to a user during
  user creation through Dashboard as well as CLI?

To manage notifications about this bug go to:
https://bugs.launchpad.net/horizon/+bug/1177241/+subscriptions