Gusted 02db188a50 [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 (cherry picked from commit 5a871f6095)		2024-08-28 08:45:05 +00:00
..
e2e	fix(ui): allow unreacting from comment popover	2024-08-10 09:42:40 +00:00
fuzz
gitea-lfs-meta
gitea-repositories-meta	[PORT] Fix agit automerge (gitea#31881)	2024-08-21 17:05:34 +02:00
integration	[SEC] Ensure propagation of API scopes for Conan and Container authentication	2024-08-28 08:45:05 +00:00
testdata/data/attachments/a/0
mysql.ini.tmpl	Update instance title in tests	2024-06-08 23:33:55 +05:00
pgsql.ini.tmpl	Update instance title in tests	2024-06-08 23:33:55 +05:00
sqlite.ini.tmpl	Update instance title in tests	2024-06-08 23:33:55 +05:00
test_utils.go	enable linter testifylint on v8 (#4573)	2024-07-30 19:41:27 +00:00