Project

General

Profile

Actions

Bug #21216

open

All rudder commands using the API don't detect the port of the webapp when we configure a virtualhost with a different port

Added by Nicolas CHARLES 2 months ago. Updated 27 days ago.

Status:
New
Priority:
N/A
Assignee:
-
Category:
Server components
Target version:
Severity:
Critical - prevents main use of Rudder | no workaround | data loss | security
UX impact:
User visibility:
Operational - other Techniques | Rudder settings | Plugins
Effort required:
Medium
Priority:
58
Regression:

Description

If the webapp/API listen on another port (because of ease of distinction of target for virtualhost) then the commands won't work, as they'll probably talk to 443
Detection of port is made with

get_https_port() {
  # get port from configuration
  PORT=$(agent_conf https_port)
  # if not trust the server on this
  if [ "${PORT}" = "" ] && [ -f "${RUDDER_JSON}" ]; then
    PORT=$(rudder_json_value 'HTTPS_POLICY_DISTRIBUTION_PORT')
  fi
  # else default to 443
  if [ "${PORT}" != "" ]; then
    PORT=":${PORT}" 
  fi
  echo "${PORT}" 
}

which is for the policy distribution, and not the webapp

There is nowhere yet where to store this value, so we'll probably need a new config parameter

Actions #1

Updated by Alexis Mousset 2 months ago

  • Severity set to Critical - prevents main use of Rudder | no workaround | data loss | security
  • User visibility set to Operational - other Techniques | Rudder settings | Plugins
  • Effort required set to Medium
  • Priority changed from 0 to 59
Actions #2

Updated by Vincent MEMBRÉ about 2 months ago

  • Target version changed from 7.0.4 to 7.0.5
Actions #3

Updated by Vincent MEMBRÉ 27 days ago

  • Target version changed from 7.0.5 to 7.0.6
  • Priority changed from 59 to 58
Actions

Also available in: Atom PDF