Specification for system-wide registration of participants

[jankapunkt]

We need a specification for system wide registration of participants.

Background:

There are two entry points for participants into the lea.online system.

1. otu.lea diagnostics app (desktop/pwa)
2. lea.app learning app (mobile app)

The user needs to be able to authenticate and authorize date exchange across both platforms (using an oauth2 workflow) without hassle. The process needs to be super easy, which is why a good spec is very important here.

The specs should consider multiple cases:

1. Register on otu.lea, later authenticate in the new downloaded lea.app
2. Register in lea.app, later authenticate in the otu.lea diagnostics
3. Register in lea.app and restore a previous account (e.g. due to lost phone)
4. Register in otu.lea in context of a course/group with an existing account and the help of an instructor

@ImkeMey @kadewe do you see any more use cases right now?

[ImkeMey]

5. register only in lea.app (without any group/course context and otu.lea)
   but maybe this is redundant, since it is already included in your specs indirectly