Age | Commit message (Collapse) | Author |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
PATs are accepted using the OAuth2 compliant header
"Authorization: Bearer {token}" in order to allow for
OAuth requests while 2FA is enabled.
|
|
|
|
|
|
|
|
Token column are no longer used as token values are stored digested in
token_digest.
|
|
|
|
Partially addresses #47424.
|
|
|
|
|
|
Closes #37789
|
|
|
|
This cop has been renamed to ActiveRecordSerialize to match the way
"ActiveRecord" is usually written.
|
|
Allow pulling container images using personal access tokens
Closes #19219
See merge request !11845
|
|
This is the first commit doing mainly 3 things:
1. create a new scope and allow users to use it
2. Have the JWTController respond correctly on this
3. Updates documentation to suggest usage of PATs
There is one gotcha, there will be no support for impersonation tokens, as this
seems not needed.
Fixes gitlab-org/gitlab-ce#19219
|
|
This Cop blacklists the use of ActiveRecord's "serialize" method, except
for cases where we already use this.
|
|
|
|
Gitlab::Auth and API::APIGuard already check for at least one valid
scope on personal access tokens, so if the scopes are empty the token
will always fail validation.
|
|
|
|
|
|
|
|
|
|
|
|
|