marsha icon indicating copy to clipboard operation
marsha copied to clipboard

JWT token scope extended to a playlist instead of a resource

Open lunika opened this issue 3 years ago • 0 comments

Feature Request

Is your feature request related to a problem or unsupported use case? Please describe.

The JWT token used in the application (the LTI one) is focused only on a resource (a video or a document). We would like to extend this scope to a playlist. If you can access a resource in a playlist, then you should also have the right to access to other resources in the same playlist.

There is a special when you access a public resource, then your token can only access public resources in the same playlist.

Describe the solution you'd like

The generated JWT token in the views.py module should be changed to manage this new behaviour. All permissions should be rework to manage this new token and also some endpoints should change accordingly (like listing all timed text tracks belonging to a video, the existing endpoint will not work anymore).

Also the permission should take care of the user's role to determine if he/she can access a private resource or not.

Discovery, Documentation, Adoption, Migration Strategy

Before starting this big refactor, we must list all impacted permissions and endpoints to have a look of what we have to do.

lunika avatar Feb 02 '22 10:02 lunika