Skip to content

Feature/collaboration scope #711

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 26 commits into from
Jul 14, 2023
Merged

Conversation

bartvanb
Copy link
Member

@bartvanb bartvanb commented Jun 14, 2023

Fix #245 and #635

bartvanb added 15 commits June 6, 2023 14:36
… modified base functions to check permissions
For task, run and result, changed organization scope to collaboration scope. Organization scope ceases to exist there
…ources. We now check better if the user is allowed to see resources for the arguments they provide
…of them and implemented them in relevant endpoints
…ore adding node to collaboration in post /collaboration/<id>/node
…iated by user themselves or by their organization
@bartvanb bartvanb changed the base branch from main to release/v4.0 June 14, 2023 13:33
@bartvanb
Copy link
Member Author

bartvanb commented Jul 3, 2023

Ignore codacy

@bartvanb bartvanb merged commit 86564e1 into release/v4.0 Jul 14, 2023
@bartvanb bartvanb deleted the feature/collaboration-scope branch July 14, 2023 08:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Feature Request] Extend API security layers with Collaboration scope
2 participants