Chongyi Zheng de484e86bc Support scoped access tokens (#20908) ... This PR adds the support for scopes of access tokens, mimicking the design of GitHub OAuth scopes. The changes of the core logic are in `models/auth` that `AccessToken` struct will have a `Scope` field. The normalized (no duplication of scope), comma-separated scope string will be stored in `access_token` table in the database. In `services/auth`, the scope will be stored in context, which will be used by `reqToken` middleware in API calls. Only OAuth2 tokens will have granular token scopes, while others like BasicAuth will default to scope `all`. A large amount of work happens in `routers/api/v1/api.go` and the corresponding `tests/integration` tests, that is adding necessary scopes to each of the API calls as they fit. - [x] Add `Scope` field to `AccessToken` - [x] Add access control to all API endpoints - [x] Update frontend & backend for when creating tokens - [x] Add a database migration for `scope` column (enable 'all' access to past tokens) I'm aiming to complete it before Gitea 1.19 release. Fixes #4300		2023-01-17 15:46:03 -06:00
..
e2e
fuzz	Move fuzz tests into tests/fuzz (#22376)	2023-01-09 15:30:14 +08:00
gitea-lfs-meta
gitea-repositories-meta
integration	Support scoped access tokens (#20908)	2023-01-17 15:46:03 -06:00
mssql.ini.tmpl
mysql.ini.tmpl	Add support for incoming emails (#22056)	2023-01-14 23:57:10 +08:00
mysql8.ini.tmpl
pgsql.ini.tmpl
sqlite.ini.tmpl
test_utils.go
testlogger.go