[Web] Dis-/enable users

[exalate-issue-sync]

Description

User Stories

• As a school admin, I would like to disable or enable individual local users quickly so that this user can no longer log in to my school immediately.

Value

• act quickly in case of emergency

Acceptance Criteria

[ ] New option in User Management "Login": "Allowed" or "Forbidden".
~~[ ] Additionally show read-only status of IAM-attribute. [~tbaader] add scribble~~
[ ] Add Contextual Helper "Inactive Users are not allowed to login any more. No data will be removed from the server."
[ ] The default value is "Allowed"
[ ] If the login option is set to forbidden, users can not log in anymore
[ ] Show status in list.
[ ] Show IAM status flag in panel als well (read only)
[ ] The User can only login, if both, the remote IAM and the local IDM have flaged the User as active. If one of the Systems flagged the user as inactive, login is not possible any more.
[ ] Not in scope: Behavior Desktop & Mobile Clients: Offline available files remain available on the devices but no new files can be synced. CC [~mstingl]
[ ] Show IAM and IDM status in details panel

Criteria

Definition of ready

[ ] everybody needs to understand the value written in the user story
[ ] acceptance criteria has to be defined
[ ] all dependencies of the user story need to be identified
[ ] feature should be seen from an end user perspective
[ ] user story has to be estimated
[ ] story points need to be less then 20

Definition of done

• Functional requirements
  [ ] functionality described in the user story works
  [ ] acceptance criteria are fulfilled
• Quality
  [ ] code review happened
  [ ] CI is green
  [ ] critical code received unit test
  [ ] E2E test:
• admin disables a user; user can not login any more

[exalate-issue-sync]

Michael Barz commented: [~tbaader] It seems that web is not the correct UI to implement it. We will not use our User Management UI in the project.

[exalate-issue-sync]

Tobias Baader commented: [~mstingl]anything we need to consider in order to make the clients stop syncing at the next possible point of time if login was set to foorbidden?

[exalate-issue-sync]

Tobias Baader commented: decided to not show the IAM status in Administration settings, as this information is currently not availaible via IAM (would be in the claims, but if a user is "disabled" claims are not beeing transferred)

[exalate-issue-sync]

Jan Ackermann commented: Web UI part done, on hold, waiting for backend