The resulting standalone-openshift.xml XML configuration file, used by RH-SSO container images heavily depends (is autogenerated) based on the environment variables, specified at the moment of RH-SSO container start.

Since the values of these environment variables can contain basically arbitrary characters, upon an error encountered during variable value expansion process, the resulting XML configuration file might get invalid / malformed in to such a state, it's not possible to start the RH-SSO container image at all.

Therefore, instead of blindly relying such a dynamically generated XML file is valid, add a container image pre-launch check to verify the syntax/correctness of the XML configuration as a whole, and in the case a XML validation error is detected, throw appropriate error, and abort launch of the container image.