[web] Navigate user to their available Schools

[exalate-issue-sync]

Description

After the user has logged in at the IdP we need to redirect the user to the correct oCIS instance. For this story we can assume that there's only ever 1 user for 1 oCIS instance.

User Stories

• As a user I want to reach my ownCloud after login so that I can use it.

• As a person who has more than 1 "cloud", I want want an option to select the right one so that I don't need to remember multiple URLs.

Value

Acceptance Criteria

• build minimalistic webfinger app which queries the webfinger service for available oCIS instances and
  • redirects to the first one (we assume there is only 1)
  • shows an error page if there are no oCIS instances for the user
• redirect should only happen for the (sub-)domain of oCIS instance, no URL metadata needed
• just fyi: ownCloud Web on the determined oCIS instance will then recognize that authentication is needed and will redirect to the IdP again, but the user will not see a login form, only a series of redirects. good for now.

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 tests by the developer
  [ ] automated tests passed (if automated tests are not available, this test needs to be created and passed
• Non-functional requirements
  [ ] no sonar cloud issues

[exalate-issue-sync]

Benedikt Kulmann commented: [~jfd] what should we do about possible error states? E.g. when a user doesn't have access to any school, we should probably show a minimal error page about that. Getting the feeling that we should've opted for a minimal web application as discussed in the first place...