We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently, the reviewers endpoints (specifically /api/v5/reviewers/addon/(int: addon_id)/versions/(int: version_id)/) returns a response of "detail": "Authentication credentials were not provided." and namely lacks the ability to support JWT auth outlined here.
/api/v5/reviewers/addon/(int: addon_id)/versions/(int: version_id)/
"detail": "Authentication credentials were not provided."
The content you are editing has changed. Please copy your edits and refresh the page.
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered:
/api/v5/reviewers/addon/(int: addon_id)/versions/(int: version_id)/ will go away when code-manager is removed so it's probably not necessary to change it.
What we should do is:
/api/v5/reviewers/addon/(int: addon_id)/file/(int: file_id)/validation/
Sorry, something went wrong.
Marking as not needing QA as @chrstinalin can verify.
diox
Successfully merging a pull request may close this issue.
Description
Currently, the reviewers endpoints (specifically
/api/v5/reviewers/addon/(int: addon_id)/versions/(int: version_id)/
) returns a response of"detail": "Authentication credentials were not provided."
and namely lacks the ability to support JWT auth outlined here.Acceptance Criteria
Acceptance Criteria
Checks
┆Issue is synchronized with this Jira Task
The text was updated successfully, but these errors were encountered: