Gusted 5a871f6095 [SEC] Ensure propagation of API scopes for Conan and Container authentication ... - The Conan and Container packages use a different type of authentication. It first authenticates via the regular way (api tokens or user:password, handled via `auth.Basic`) and then generates a JWT token that is used by the package software (such as Docker) to do the action they wanted to do. This JWT token didn't properly propagate the API scopes that the token was generated for, and thus could lead to a 'scope escalation' within the Conan and Container packages, read access to write access. - Store the API scope in the JWT token, so it can be propagated on subsequent calls that uses that JWT token. - Integration test added. - Resolves #5128		2024-08-28 10:33:32 +02:00
..
actions
agit
asymkey
attachment
auth
automerge
context
contexttest
convert
cron
doctor	fix: correct doctor commands and rename to forgejo	2024-08-27 02:40:55 +02:00
externalaccount
f3
federation
feed
forgejo
forms
gitdiff	feat: Improve diff being generated	2024-08-26 13:58:17 +02:00
indexer
issue
lfs
mailer
markup
migrations
mirror
notify
org
packages	[SEC] Ensure propagation of API scopes for Conan and Container authentication	2024-08-28 10:33:32 +02:00
pull
release
remote
repository
secrets
task
uinotification
user
webhook
wiki