admin interface + API

[eroux]

I think in order for the workflow to be smoother we should have some API endpoints on ldspdi that:

• reloads everything from auth0
• reloads the information about one specific user from auth0 (and not every user)

Also, by doing that we could also:

• when the library looks at a token and sees a auth id that's not in the database, it could just update this user id and update the model of ldspdi, then pushing it on fuseki
• when the library loads it would just load the model on fuseki without going through auth0 (maybe that's the case already?)

with that system we don't depend on the auth0 api so much

[MarcAgate]

• reloads everything from auth0

We have that here:
https://github.com/buda-base/lds-pdi/blob/master/src/main/java/io/bdrc/ldspdi/rest/controllers/BdrcAuthController.java#L320

• reloads the information about one specific user from auth0 (and not every user)

This needs to be implemented (I must check)

Also, by doing that we could also:

• when the library looks at a token and sees a auth id that's not in the database, it could just update this user id and update the model of ldspdi, then pushing it on fuseki

This happens in editserv when the user logs into the library for the first time. A BudaUser is created and the authModel is updated on Fuseki.
We just have to call another existing webhook to read and update authModel from the updated fuseki graph on ldspdi:
https://github.com/buda-base/lds-pdi/blob/master/src/main/java/io/bdrc/ldspdi/rest/controllers/BdrcAuthController.java#L328

• when the library loads it would just load the model on fuseki without going through auth0 (maybe that's the case already?)

• I beleive this should be configurable. Yes.

[eroux]

great!