Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Review test tokens and impact of authorization, esp wrt read/write/upload permissions #789

Open
Tracked by #777
johnaohara opened this issue Oct 20, 2023 · 3 comments
Open
Tracked by #777

Review test tokens and impact of authorization, esp wrt read/write/upload permissions #789

johnaohara opened this issue Oct 20, 2023 · 3 comments

Comments

@johnaohara
Copy link
Member

johnaohara commented Oct 20, 2023 •
edited
Loading

This depends on : #782
@johnaohara johnaohara mentioned this issue Oct 20, 2023
Open
14 tasks
@johnaohara
Copy link
Member Author

Test tokens are generated client side, with no validations on length, complexity etc.

@johnaohara
Copy link
Member Author

There are multiple ways in which tokens can be generated, and it is not consistent between different object types, e.g. Test access tokens are generated client side. Run & Schema tokens are generated server side. There is no record of who generated what token.

@johnaohara
Copy link
Member Author

@barreiro after chatting yesterday, it also seems that you are trying to fix this issue, alongside #780

Is that correct?

@johnaohara johnaohara added this to the 0.12 milestone Jan 18, 2024
@johnaohara johnaohara removed this from the 0.12 milestone Feb 5, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@johnaohara