Security training settings are hidden when the GitLab instance cannot reach public internet
Summary
It was reported from a customer when they tried to configure the security training module, the settings were hidden. We determined that their environment does not reach the public internet and could be causing the issue.
Steps to reproduce
- Set up instance without internet access
- View security configuration view, specifically Vulnerability Management Tab.
- The text and toggle settings for Secure Code Warrior/Kontra are hidden.
Example Project
What is the current bug behavior?
The text and toggle settings for Secure Code Warrior/Kontra are hidden.
What is the expected correct behavior?
- The view should provide feedback to user if these settings cannot be configured in offline environments.
- Make a note of this in the docs: https://docs.gitlab.com/ee/user/application_security/vulnerabilities/#enable-security-training-for-vulnerabilities workflowcomplete
Relevant logs and/or screenshots
Requested from customer
Output of checks
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
Edited by Neil McCorrison