We are having an issue with logging into our instance of SonarQube (Developer edition) v22.214.171.124792, via our instance of GitLab when using https. Can we ask for some advice on this please?
Initially, our SonarQube instance was set-up using the default port (http://sonar:9000/, etc) and with that configuration, integrated it with our GitLab instance (https://gitlab/, etc). We are able to get our projects into SonarQube and perform code analysis using this just fine.
Later, we have decided to get our SonarQube instance behind an https proxy, and so we followed the instructions in Configure SSL for SonarQube on Windows to set it up. Logging into https SonarQube (https://sonar/) using accounts made in SonarQube works fine. All seemed well until we tried logging into https SonarQube with our GitLab accounts. When attempting to log in https SonarQube with GitLab, we get redirected back to https://sonar/ without getting into the GitLab login page.
To note, our GitLab instance has been configured such that SonarQube is registered as an application, with the redirect url set to https://sonar once we have set-up our https proxy, and all relevant scopes checked. Also, on our SonarQube instance, sonar.core.serverBaseURL has been set to the same url. Our servers are inside our private network, and all certificates are accounted for.