- Aug 18, 2020
-
-
GitLab Release Tools Bot authored
[ci skip]
-
GitLab Release Tools Bot authored
[ci skip]
-
GitLab Release Tools Bot authored
-
GitLab Release Tools Bot authored
- Aug 17, 2020
-
-
GitLab Release Tools Bot authored
[ci skip]
-
GitLab Release Tools Bot authored
[ci skip]
-
GitLab Release Tools Bot authored
-
Yorick Peterse authored
Stop deploy token being used as user in ProjectPolicy and GroupPolicy See merge request gitlab-org/security/gitlab!822
-
Yorick Peterse authored
Add check for project access on deploy token check See merge request gitlab-org/security/gitlab!818
-
Thong Kuah authored
This prevents deploy token from getting permissions for users that happen to have the same id as the deploy token.
-
When a deploy token is authenticated, project access is checked and rejected if not allowed. Auth spec is fixed to properly test this scenario Update guard clause to allow nil projects to pass for registry access Update LFS spec - now returns 401 for invalid deploy token Fixing flaky tests Add spec for group deploy token as well
- Aug 05, 2020
-
-
GitLab Release Tools Bot authored
-
GitLab Release Tools Bot authored
[ci skip]
-
GitLab Release Tools Bot authored
[ci skip]
-
GitLab Release Tools Bot authored
-
- Aug 04, 2020
-
-
Mayra Cabrera authored
2FA not enforced on /profile/applications See merge request gitlab-org/security/gitlab!783
-
Add one more spec Add changelog entry Fix changelog Move concern to doorkeeper base controller Add base metal controller Add new controller Fix Remove 2FA from api-endpoints Add if-clause block around helper method Add controllers tests And implement 2FA enforcement in tokens controllers Remove obsolete let in spec Fix Fix
-
Mayra Cabrera authored
Update GitLab Runner version See merge request gitlab-org/security/gitlab!755
-
GitLab Release Tools Bot authored
Fix XSS on jobs view See merge request gitlab-org/security/gitlab!652
-
GitLab Release Tools Bot authored
Revoke OAuth grants when a user revokes an application See merge request gitlab-org/security/gitlab!759
-
GitLab Release Tools Bot authored
Add a prohibited branches system See merge request gitlab-org/security/gitlab!663
-
GitLab Release Tools Bot authored
Verify confirmed email for OAuth Authorize POST endpoint See merge request gitlab-org/security/gitlab!741
-
GitLab Release Tools Bot authored
Add refreshing projects to transfering groups See merge request gitlab-org/security/gitlab!717
-
GitLab Release Tools Bot authored
Escape milestone title in sidebar tooltip See merge request gitlab-org/security/gitlab!734
-
GitLab Release Tools Bot authored
Only support HTML tooltips for scoped labels See merge request gitlab-org/security/gitlab!692
-
GitLab Release Tools Bot authored
Add decompressed archive size validation on Project/Group Import See merge request gitlab-org/security/gitlab!653
-
GitLab Release Tools Bot authored
Stop excess logs from invite email when group no longer exists See merge request gitlab-org/security/gitlab!721
-
- Jul 27, 2020
-
-
Currently, when a user revokes OAuth applications only existing access tokens are revoked. If an application has already requested a code (grant) to later redeem for an access token, the grant may remain valid and will generate a valid access token until expired (10 min expiry). This change ensures both access tokens *and* grants are revoked when a user revoked the application.
-
Steve Xuereb authored
-
- Jul 24, 2020
-
-
Similar to the recent change to require email confirmation/verification for the OAuth Authorize GET (:new) endpoint, require the same for the OAuth Authorize POST (:create) endpoint. This will prevent forcing a POST request to authenticate to an external service with an unconfirmed email address.
-
- Jul 23, 2020
-
-
GitLab Release Tools Bot authored
[ci skip]
-
GitLab Release Tools Bot authored
[ci skip]
-
GitLab Release Tools Bot authored
-
Mayra Cabrera authored
Prepare 13.1.5-ee release See merge request gitlab-org/gitlab!37707