-
Bug
-
Resolution: Done
-
Critical
-
RH-SSO-7.5.1, RH-SSO-7.5.2, RH-SSO-7.5.0
-
False
-
None
-
False
-
Compatibility/Configuration, User Experience
-
-
-
Workaround Exists
-
-
-
CIAM Sprint 17, CIAM Sprint 21
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
- is cloned by
-
RHSSO-2204 [RH-SSO 7.6.X container images] Escape all XML special characters (AKA incomplete fix for CLOUD-3198)
- Closed
-
RHSSO-2018 [RH-SSO 7.5.2+ container images] Add a pre-launch check to throw an error message when generated standalone-openshift.xml XML configuration file is invalid / malformed
- Closed
- is related to
-
CLOUD-3198 [EAP7] When user supplies a JDBC connection URL, parts of the URL will be ignored
- New
- mentioned on