-
Title
Template name perceived as a literal string if template block is defined after the destination -
Description
Destination template names may falsely be perceived as strings, if the template definition block is placed after the destination definition.
Thus while the following example configuration works:source s_testfile {file("/test_in");};template t_tmpl {template("AAAA ${MESSAGE} AAAA\n");};destination d_testfile {file("/test_out"template(t_tmpl));};log {source(s_testfile);destination(d_testfile);};
The version below doesn't:
source s_testfile {file("/test_in");};destination d_testfile {file("/test_out"template(t_tmpl));};template t_tmpl {template("AAAA ${MESSAGE} AAAA\n");};log {source(s_testfile);destination(d_testfile);};
It simply prints "t_tmpl" on every outgoing message. -
Cause
Product defect. -
Resolution
This defect has been confirmed and change request #SYSLOGDEV-3968 has been raised for tracking of the issue.
There is no ETA on when the fix will be implemented in a future release as of yet.
Please review the list of Resolved Issues and Enhancement Requests published within the product release notes to determine if this specific Change Request is included in an upcoming release. Release notes are available at support.oneidentity.com under the technical documentation section of our website. We do not guarantee that all Change Requests will be implemented in future releases. For more information on our Product Enhancements and Defects policy, please consult the One Identity Global Support Guide https://support.oneidentity.com/essentials/support-guide
-
Change Request
SYSLOGDEV-3968