Andreas Svanberg
03ad12f435
Daisy's API does not support the function "change supervisor" and only what comes down to SQL INSERT and DELETE on a specific table. If the removal of the previous supervisor(s) failed the new one was still added. This change makes it so that if the removal of any (there is no limit in the API) current supervisor fails it will not attempt to add the new supervisor. Fixes #39 ## How to test 1. Configure the Daisy integration in SciPro 2. Enable it (Maven profile) 3. The only currently known way to make removing a supervisor fail is to use a project where they've sent the thesis to the examiner 4. Find one such project in the test server for Daisy (or send one for examination from SciPro) 5. Change the supervisor of the project in SciPro 6. Run the job "Export projects to daisy" (System / Maintenance) 7. See that it logs the failure and that no duplicate supervisors were added to Daisy Reviewed-on: #26 Reviewed-by: Tom Zhao <tom.zhao@dsv.su.se> Co-authored-by: Andreas Svanberg <andreass@dsv.su.se> Co-committed-by: Andreas Svanberg <andreass@dsv.su.se>
Working with the API
The API is protected by OAuth 2 acting as a resource server verifying tokens using token introspection.
When developing it uses a locally running instance of an
authorization server
that is run inside Docker. It can be started with docker compose -f docker-compose.yml up.
Since there is no frontend to interact with the authorization server there's a helper script in
GetToken.java that can be run directly with java GetToken.java to run through the authorization flow
and get an access token.
Once the token has been obtained go to the Swagger UI to interact with the API. Click the "Authorize" button in the top right and paste the access token to log in.