Keystone has an explicit concept of a default tenant/primary project
which by its nature is only a relationship to one project. That's what
you're setting at creation time.
Once the user is created you can add them to as many projects as you
like, but that's a completely different operation from
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
2 matches
Mail list logo
