- Jan 10, 2024
-
-
Marte Fossum authored
If the guest have a different affiliation or a different active guest role, do not send them a role end reminder as to limit the number of emails the guest receives
-
- Dec 21, 2023
-
-
Henrich Neumann authored
-
Henrich Neumann authored
-
- Nov 29, 2023
-
-
Marte Fossum authored
Guests will now also receive an email when their guest role is about to expire
-
- Oct 23, 2023
-
-
- Sep 18, 2023
-
-
Marte Fossum authored
-
- Sep 15, 2023
-
-
lass authored
-
- Aug 11, 2023
-
-
Henrich Neumann authored
This can be toggled on or off with a feature toggle.
-
- Apr 07, 2023
-
-
Jonas Braathen authored
-
- Apr 06, 2023
-
-
Jonas Braathen authored
-
Jonas Braathen authored
-
- Mar 16, 2023
-
-
lass authored
Also changed the name of some variables to make the code more readable
-
- Mar 10, 2023
- Mar 08, 2023
- Jan 20, 2023
-
-
Jonas Braathen authored
-
- Nov 23, 2022
-
-
Marte Fossum authored
-
- Nov 01, 2022
- Oct 20, 2022
-
-
Marte Fossum authored
-
- Mar 24, 2022
-
-
Andreas Ellewsen authored
-
- Mar 11, 2022
-
-
Andreas Ellewsen authored
Since we may not want to enable the identity check, it must be togglable. This commit adds environment variable REACT_APP_ENABLE_IGA_CHECK for toggling the check in the frontend, and django settings variable IGA_CHECK for toggling the check in the backend.
-
Jonas Braathen authored
-
- Mar 04, 2022
-
-
Andreas Ellewsen authored
Queries iga for an external id matching ours. If a match is found, the name of the owner is returend. Otherwise we return null. Uses the new iga module to fetch the data.
-
- Feb 09, 2022
-
-
Jonas Braathen authored
-
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
-
- Jan 27, 2022
-
-
Andreas Ellewsen authored
-
- Jan 25, 2022
-
-
Jonas Braathen authored
-
- Jan 17, 2022
-
-
Andreas Ellewsen authored
Link login was replaced by our own implementation some time ago, making sesame pointless.
-
- Jan 11, 2022
-
-
Andreas Ellewsen authored
Introduces the CEREBRUM_MANUAL_SPONSOR_UNITS settings variable which contains a list of stedkode for units where sponsors are handled manually. Resolves: GREG-163
-
Andreas Ellewsen authored
To reduce the amount of code and complexity of the service we move away from a management command triggered by a cronjob, to a task handled by django-q. Everything works the same way as before, but the management command now schedules the task instead of doing it. Introduces the ORGREG_SCHEDULE_TYPE settings variable controlling the scheduled when scheduling the import using the management command.
-
- Jan 06, 2022
-
-
Andreas Ellewsen authored
The setup has five parts: - a new email template type - a new django-q task for notifying - a management command for scheduling the task periodically - a new settings variable NOTIFIER_LIMIT for controlling the number of days into the future the notifier script should use for end date of roles. - a new settings variable NOTIFIER_SCHEDULE_TYPE for controlling how often the notifier task should be scheduled when using the management command. Resolves: GREG-162
-
- Jan 04, 2022
-
-
Andreas Ellewsen authored
Done to make djangoq settings accessible in production. The sync setting is changed to the default False value since the run order of the tasks is not relevant for our use case. Mail sending functions have gotten a sync argument to force the tasks to complete before checking their consequences in tests.
-
- Dec 21, 2021
-
-
Jonas Braathen authored
- Set the default to IsAdminUser - Set it explicitly on all the views - Add tests
-
- Dec 15, 2021
-
-
Jonas Braathen authored
-
- Dec 06, 2021
-
-
Tore.Brede authored
-
- Nov 19, 2021
-
-
Sivert Kronen Hatteberg authored
We do not use the token after initial login, no need to refresh.
-