Uploaded image for project: 'RH-SSO'
  1. RH-SSO
  2. RHSSO-2204

[RH-SSO 7.6.X container images] Escape all XML special characters (AKA incomplete fix for CLOUD-3198)

XMLWordPrintable

    • False
    • None
    • False
    • Compatibility/Configuration, User Experience
    • Workaround Exists
    • Hide

      Till the updated RH-SSO container image, containing the correction is available:

      • Either don't use any XML special characters in environment variables passed to the image,
      • Or escape that special XML character in the environment variable value (if correlated circumstances specific to this env var allow it to be escaped).
      Show
      Till the updated RH-SSO container image, containing the correction is available: Either don't use any XML special characters in environment variables passed to the image, Or escape that special XML character in the environment variable value (if correlated circumstances specific to this env var allow it to be escaped).
    • Hide

      See the accompanied SSOSUP-207 ticket.

      Show
      See the accompanied SSOSUP-207 ticket.
    • CIAM Sprint 23

      Using some of XML special characters in the value of some environment variable, passed to the RH-SSO container image (mainly env vars holding passwords or dynamically generated values) leads to malformed XML configuration file, subsequently followed by a RH-SSO pod startup failure.

      This issue is related to previous CLOUD-3198, but additional (on top of CLOUD-3198 fix) is necessary, because the original fix escaped just the ampersand (&) and semicolon (;) characters, and only, when specified as part of the JDBC URL string.

      We need to extend the original fix to escape all five of the XML special characters

              rhn-jlieskov Ján Lieskovský (Inactive)
              rhn-jlieskov Ján Lieskovský (Inactive)
              Ivan Khomyn
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: