Skip to content

Failures in Security Configuration

Summary

There are failures in Security Configuration, at least for tested SAST and Dependency Scanning

Steps to reproduce

  • Create a project
  • Security & Compliance -> Configuration
  • SAST -> Enable SAST
  • Create Merge Request
  • An error occurred while creating the merge request.

image

  • Create a project
  • Security & Compliance -> Configuration
  • Dependency Scanning -> Configure with a Merge Request
  • You must provide a file path is shown

image

Example Project

https://gitlab.com/willmeek/license_compliance_test/-/security/configuration

What is the current bug behavior?

Security Configuration fails

What is the expected correct behavior?

Security Configuration does not fail to enable SAST / DS

Relevant logs and/or screenshots

See reproducible steps

Output of checks

This bug happens on GitLab.com

Results of GitLab environment info

Expand for output related to GitLab environment info 

(For installations with omnibus-gitlab package run and paste the output of:
`sudo gitlab-rake gitlab:env:info`)

(For installations from source run and paste the output of:
`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`)

Results of GitLab application Check

Expand for output related to the GitLab application check 
(For installations with omnibus-gitlab package run and paste the output of:
sudo gitlab-rake gitlab:check SANITIZE=true)


(For installations from source run and paste the output of:
sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true)


(we will only investigate if the tests are passing)

Possible fixes