Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

Move authorization logic to dedicated service #44

Closed
mickvandijke opened this issue Jul 5, 2022 · 3 comments
Closed

Move authorization logic to dedicated service #44

mickvandijke opened this issue Jul 5, 2022 · 3 comments
Labels

Comments

@mickvandijke
Copy link
Member

Currently, authorization is handled by each handler on its own. We should translate this logic into actions that will be authorized by a service that checks whether the user that invoked the action has the proper permissions to do so.

@mickvandijke mickvandijke changed the title Move authorization logic to service Move authorization logic to dedicated service Jul 5, 2022
@rakema01
Copy link

rakema01 commented Jul 13, 2022

I'd also like to suggest a setting to force a check for a valid personal tracker link for private trackers.
Not sure if this is happening to anyone else, but it seems like the current backend still serves a download link with no personal tracker link if the backend isn't able to retrieve a valid one. This is an issue since once the tracker token expires the user usually has to log out and back in to refresh it.

I guess this would just be a suggestion for checking user authorization for torrent downloading.

@josecelano
Copy link
Member

Relates to #39

@josecelano
Copy link
Member

Currently, authorization is handled by each handler on its own. We should translate this logic into actions that will be authorized by a service that checks whether the user that invoked the action has the proper permissions to do so.

hi @rakema01 I will review that problem. See torrust/torrust-index-gui#417

@torrust torrust locked and limited conversation to collaborators Jan 16, 2024
@josecelano josecelano converted this issue into discussion #436 Jan 16, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
Projects
Status: Done
Development

No branches or pull requests

3 participants