Slack integration blocked by OKTA

SonarQube Server / Community Build
, ,
1

What?

The core issue is that when using the /sonarqube-server command in slack, when Slack sends its webhook payload to SonarQube, Okta/Veriproxy is intercepting the request and returning the HTML for the SSO login screen, which slack just dumps into the channel.

Specs:

  • which versions are you using (SonarQube Server / Community Build, Scanner, Plugin, and any relevant extension)
    • Enterprise Edition v2025.6.1 (117629)
  • how is SonarQube deployed: zip, Docker, Helm
    • Docker, Helm, k8s
  • what are you trying to achieve
    • Use the new native slack integration
  • what have you tried so far to achieve this
    • Configured the slack app in sonarqube as an admin per Setting up the connection to Slack | SonarQube Server 2025.6 | Sonar Documentation
    • Configured the slack app in slack via our IT team as they are admins of our slack workspace
    • Configured the /sonarqube-server slack command and invited the app into relevant channels
    • Whitelisted the following paths as we use veriproxy:
    •       - path: "/api/v2/integrations/slack/slash-commands"
      - path: "/api/v2/integrations/slack/events"
      - path: "/api/v2/integrations/slack/user-bindings"

Curious if anyone has ran into this problem?

2

Example output:

/sonarqube-server connect

<!DOCTYPE html>
<!--[if IE 7]><html lang="en" class="lt-ie10 lt-ie9 lt-ie8"><![endif]-->
<!--[if IE 8]><html lang="en" class="lt-ie10 lt-ie9"> <![endif]-->
<!--[if IE 9]><html lang="en" class="lt-ie10"><![endif]-->
<!--[if gt IE 9]><html lang="en"><![endif]-->
<!--[if !IE]><!--><html lang="en"><!--<![endif]-->
<head>
    <meta charset="UTF-8">