Andreas Ellewsen authored 3 years ago and Jonas Braathen committed 3 years ago

If a sponsor verifies a nin that is already in use by an account in
cerebrum, the guest will gain access to that account, which in turn
allows the guest to change the password of that account. This makes it
possible to abuse the guest service to steal the account of users.

A feature that checks for this problem, and helps the sponsor make a
decision on it, will be introduced in the near future. At that point
nin verification can be enabled again.

Resolves: GREG-202

This ensures that identity values created from values written in the
frontend by guests are given a source value signifying so.

Resolves: GREG-186

If the user logs in through the frontpage we now check if they have
completed the registration process. If they have completed it halfway
before, we find their info through the GregUserProfile of the user and
redirect to the register page. If we dont find any profile connected to
the user they are treated as anonymous users as before.

Resolves: GREG-164

Resolves: GREG-173

Issue: greg-112

It has been decided that a sponsor at a unit should have access to all
roles at that unit. This includes all units accessible through
hierarchical access.

Resolves: GREG-150

Dates can now be changed after they have started and ended. This means
that there is no situation which needs disabling the input fields, and
disabling has been removed.

Start and end date can now be in the past. The following rules apply:
 - Start dates can be any date in the past, and no more into the future
   than the max days property of the role type.
 - End dates follow the same rules
 - End dates must be equal to or later than start date.

Notification publishing has been reviewed to ensure duplicate
notifications are not created when start or end date is today.

Resolve: GREG-148

- Combine the /invite and /invitelink endpoints into one
- Return error messages from the backend
- Handle errors in the frontend
- Lower number of queries ran when calling the userinfo endpoint

Used to "log" a user out in the manual invite flow

Serialization has been moved to serializer classes, sharing them when
sensible and Views have been converted to ViewSets to simplify code.

Separates the queryset and the serialization from each other.

The OU view deserves its own file, and the guest info is actually a
person view and should live with  the other person views.

The profile page of a guest now shows a verification button if the guest
has a passport or national identificaiton number that has not been
verified. Clicking the button shows a dialog, with a confirmation button
which triggers a PATCH request to the backend and reloads the page when
it returns.

Resolves: GREG-101

Does the same as before with less and more readable code.