Skip to content

XML reserved characters are not escaped when being used in XML configuration files #842

Description

@Jimvin

Affected Stackable version

25.7

Affected Apache NiFi version

2.4.0

Current and expected behavior

When the Stackable NiFi operator takes a parameter value and uses it in one of its XML-based configuration files it does not escape reserved characters. This means that if the value contains a character such as an ampersand (&) then the result is malformed XML document that cannot be parsed, causing NiFi to fail on startup.

Possible solution

The operator should escape any reserved characters when it includes a parameter value e.g. replacing & with &.

Additional context

No response

Environment

No response

Would you like to work on fixing this bug?

None

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions