Our SonarQube server is accessible behind our organization’s reverse proxy (RP). The RP authenticates the client. The client is a sonar scanner call coming from anywhere in the organization. How should we configure the sonar scanner call to make it embed authentication data? Our RP supports SAML, Kerberos, OAuth2, but does not support basic authentication.
Sonar-scanner : run in all kinds of platforms and versions.
Reverse proxy : F5 Big IP.
SonarQube 9.9.1 LTS, Deployed on OpenShift.
Many thanks in advance for your help.
Welcome to the community!
Sorry for the long delay in responding. The scanner only supports basic authentication. I’m going to move your topic to the Product Manager for a Day category since the functionality you’re after doesn’t exist.
Thanks for your insight, we really appreciate that you took the time to share it. At the moment, we don’t have any plans to address this on our current roadmap, but if we find evidence that it’s a wider problem we’ll look into it further.
Did you manage to run your Scanner behind your proxy?
Thank you Ilham for your answer. We managed to make our Scanner reach SonarQube through a reverse proxy, at the cost of not configuring the reverse proxy and making it act merely as a URL redirection in pass-through mode.