From a3893f5d728e2223ac8853fb7b320e8c1cb5328d Mon Sep 17 00:00:00 2001 From: Peter Nied Date: Tue, 29 Mar 2022 15:51:08 -0500 Subject: [PATCH] Correct log4j2 syntax in the example In the [yml format](https://logging.apache.org/log4j/2.x/manual/configuration.html#Configuration_with_Properties) in of the log4j properties file, a logger is declared with logger.LOGGER_NAME.name, the value of LOGGER_NAME can be set as desired by the user. When the example included the `.` operator it was treated as another object and 'security' was referenced as a key which didn't resolve to anything. Signed-off-by: Peter Nied --- _troubleshoot/openid-connect.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/_troubleshoot/openid-connect.md b/_troubleshoot/openid-connect.md index fb1ab2b2..d1e4fda5 100644 --- a/_troubleshoot/openid-connect.md +++ b/_troubleshoot/openid-connect.md @@ -23,8 +23,8 @@ This page includes troubleshooting steps for using OpenID Connect with the secur To help troubleshoot OpenID Connect, set the log level to `debug` on OpenSearch. Add the following lines in `config/log4j2.properties` and restart the node: ``` -logger.plugins.security.name = com.amazon.dlic.auth.http.jwt -logger.plugins.security.level = trace +logger.securityjwt.name = com.amazon.dlic.auth.http.jwt +logger.securityjwt.level = trace ``` This setting prints a lot of helpful information to your log file. If this information isn't sufficient, you can also set the log level to `trace`.