Provide infrastructure for live documents #3

Closed
opened 2021-08-01 21:05:30 +02:00 by nik · 5 comments
Owner

Resint should provide infrastructure for live documents. Live documents are media files that are generated at periodic intervals, and stored in their most recent version. This infrastructure can be used by features like the substitution plan generator in Chronos, that publishes an updated version of a print-out substitution plan PDF on plan changes.

The media files should be provided under an OAuth scope to applications that have undergone Client Credentials authentication (attention: currently, django-oauth-toolkit does not support limiting available scopes per application, cf. https://github.com/jazzband/django-oauth-toolkit/issues/262, so all OAuth applications will be able to retrieve these media files, for now - maybe this is only a limitation of the Authorization Code Flow; I will investigate).

Resint should provide infrastructure for live documents. Live documents are media files that are generated at periodic intervals, and stored in their most recent version. This infrastructure can be used by features like the substitution plan generator in Chronos, that publishes an updated version of a print-out substitution plan PDF on plan changes. The media files should be provided under an OAuth scope to applications that have undergone Client Credentials authentication (attention: currently, django-oauth-toolkit does not support limiting available scopes per application, cf. https://github.com/jazzband/django-oauth-toolkit/issues/262, so all OAuth applications will be able to retrieve these media files, for now - maybe this is only a limitation of the Authorization Code Flow; I will investigate).
Author
Owner

mentioned in issue AlekSIS/official/AlekSIS-Core#495

mentioned in issue AlekSIS/official/AlekSIS-Core#495
Owner

assigned to @hansegucker

assigned to @hansegucker
Owner

created merge request !39 to address this issue

created merge request !39 to address this issue
Owner

mentioned in merge request !39

mentioned in merge request !39
Author
Owner

mentioned in commit d8cd078e0f

mentioned in commit d8cd078e0f7aa3fa3fddd06be2aa58068ae626fb
nik closed this issue 2021-11-03 13:09:51 +01:00
Sign in to join this conversation.
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
aleksis/AlekSIS-App-Resint#3
No description provided.