[ https://issues.apache.org/jira/browse/LOG4J2-3478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17530910#comment-17530910 ]
Carter Kozak commented on LOG4J2-3478: -------------------------------------- I don't believe we have a base64 lookup in log4j2. If we did, the linked code should decode as expected. > Base64 lookup doesn't work with system property substitution > ------------------------------------------------------------ > > Key: LOG4J2-3478 > URL: https://issues.apache.org/jira/browse/LOG4J2-3478 > Project: Log4j 2 > Issue Type: Bug > Reporter: oskarryn > Priority: Minor > > Base64 encoded system property doesn't work, e.g. > {code:java} > property.token = ${base64:${sys:some.encoded.token}} > {code} > fails (silently) and is valued literally, without any expansion. The expected > behavior is that the _some.encoded.token_ system property would be looked up > and then decoded by base64 lookup. > If this kind of "nesting" should be considered a feature please comment and > I'll change the type. -- This message was sent by Atlassian Jira (v8.20.7#820007)