-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
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
/api/v1/version should not give 403 for authenticated users/tokens #26035
Labels
Comments
It seems that it's related to my (unresolved) review comment:
|
lunny
pushed a commit
that referenced
this issue
Jul 26, 2023
GiteaBot
pushed a commit
to GiteaBot/gitea
that referenced
this issue
Jul 26, 2023
lunny
pushed a commit
that referenced
this issue
Jul 26, 2023
Backport #26134 by @wxiaoguang Fix #26035 Co-authored-by: wxiaoguang <wxiaoguang@gmail.com>
project-mirrors-bot-tu bot
pushed a commit
to project-mirrors/forgejo-as-gitea-fork
that referenced
this issue
Jan 23, 2025
…o-gitea#26149) Backport go-gitea#26134 by @wxiaoguang Fix go-gitea#26035 Co-authored-by: wxiaoguang <wxiaoguang@gmail.com> (cherry picked from commit a8445e9)
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Description
Before gitea 1.20.0, a token with the
repo
scope could access the/api/v1/version
endpoint.In gitea 1.20.0, a token with the
write:repository
scope cannot access the/api/v1/version
endpoint.Here's the partial bash script that I've used to create the token and test it:
Gitea Version
1.20.0
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Screenshots
No response
Git Version
No response
Operating System
No response
How are you running Gitea?
In docker, as configured in the first part of the bash script at https://github.com/rgl/my-ubuntu-ansible-playbooks/blob/main/renovate.sh
Database
SQLite
The text was updated successfully, but these errors were encountered: