[
https://issues.apache.org/jira/browse/LOG4J2-3478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17534840#comment-17534840
]
oskarryn commented on LOG4J2-3478:
----------------------------------
You are right, I checked again and base64 lookup doesn't work in log4j2. It
was an error on my part, I didn't verify it properly at first because I was so
sure it works after seeing this in docs.
I close this issue, but I believe the mismatch between documentation and
available features is undesirable so I created LOG4J2-3504.
> 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)
