saml_message_max_byte_size is not having an affect on omnibus instance SAML
Summary
Steps to reproduce
- Update
saml_message_max_byte_size
in the GitLab instance's/etc/gitlab/gitlab.rb
. - Run
sudo gitlab-ctl reconfigure
on the same GitLab instance. - Value for
Settings.omniauth['saml_message_max_byte_size']
is confirmed to change to new value. - Error message containing default value is still returned
Enconded saml message exceeds 250000 bytes, so was rejected
.
Example Project
GitLab omnibus self-managed instance.
What is the current bug behavior?
When the omnibus GitLab instance has this value changed it does not have an effect where the saml_message_max_byte_size
value is used.
What is the expected correct behavior?
When the omnibus GitLab instance has this value changed it has an effect where the saml_message_max_byte_size
value is used.
Relevant logs and/or screenshots
This is a direct report from a customer: https://gitlab.zendesk.com/agent/tickets/326127
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)