Improve using scopes for user commands

Description

Background

The user:create command without arguments is broken, since the introduction of user scopes.
The working of userassword:change is unsure when a username is used in multiple scopes.

Requirements

  • Use the Integrated scope for the user:create and userassword:change command, when no scope is specified

  • Add the scope as optional argument for the userassword:change command (when not specified use the Integrated scope)

  • The "user:create" command currently adds a new scope admin scope when the specified scope does not exist. This is not OK, only one admin scope can exist. Please create as a non-admin scope, or prevent using scopes which not exists.

Test scenarios

  • Set up an installation with multiple scopes

  • Use the user:create command to create a user --> it should be created in the Integrated scope

  • Use the user:create command to create a user x on scope x --> User should be created in scope x, unable to login into Integrated

  • Use the userassword:change command to change user x --> should not be able to find user, password should not be changed

  • Use the userassword:change command to change user x on scope x --> password should be changed

  • Create a duplicate username (on different scopes) and use the userassword:change command on scope x. Only the user with scope x should be changed

Technical tasks

None

Deployment actions

None

Status

Assignee

Unassigned

Client

Integrated Marijn

Epic Link

Sprint

None

Fix versions

Configure