Support OAuth2 authentication for LiveDocument PDF view #5

Closed
opened 2021-11-04 22:02:20 +01:00 by hansegucker · 7 comments
Owner

This includes the following items:

  • Secure an API view with OAuth2
  • Provide scopes for all live documents
  • Check OAuth2 scopes in API view
This includes the following items: - [x] Secure an API view with OAuth2 - [x] Provide scopes for all live documents - [ ] Check OAuth2 scopes in API view
Author
Owner

assigned to @hansegucker

assigned to @hansegucker
Author
Owner

marked the checklist item Secure an API view with OAuth2 as completed

marked the checklist item **Secure an API view with OAuth2** as completed
Author
Owner

marked the checklist item Provide scopes for all live documents as completed

marked the checklist item **Provide scopes for all live documents** as completed
Author
Owner

created merge request !44 to address this issue

created merge request !44 to address this issue
Author
Owner

mentioned in merge request !44

mentioned in merge request !44
Owner

I have prepared an MR that allows limiting scopes per app: AlekSIS/official/AlekSIS-Core!782

That means you can now simply rely on scopes being properly filtered already when they hit your permission check.

Please test this, after the changes land in core:

  • Verify that using an app that is notlimited can access the resource
  • Verify that using an app that is limited, and has the desired scope, can access the resource
  • Verify that using an app that is limited, but not for the desired resource, can not access the resouce
I have prepared an MR that allows limiting scopes per app: AlekSIS/official/AlekSIS-Core!782 That means you can now simply rely on scopes being properly filtered already when they hit your permission check. Please test this, after the changes land in core: * Verify that using an app that is notlimited can access the resource * Verify that using an app that is limited, and has the desired scope, can access the resource * Verify that using an app that is limited, but not for the desired resource, can not access the resouce
nik closed this issue 2021-11-06 21:55:40 +01:00
Owner

mentioned in commit 243fe08114

mentioned in commit 243fe08114f30854e358c5d16e68e98a2e45ee1e
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#5
No description provided.