[QUERY] Is there a way I can disable logs from the AuthenticationAuthority class

[Shabirmean]

Query/Question
I am consuming the Azure SDK for a project I am working on. However, I have set the LogLevel in the Azure controller to NONE.

Azure.configure().withLogLevel(LogLevel.NONE).authenticate(credentials);

But still get a bunch of a logs from the class c.m.a.adal4j.AuthenticationAuthority

2020-02-26 15:41:46,991 [pool-1-thread-37] INFO  c.m.a.adal4j.AuthenticationAuthority - [Correlation ID: 72e7c78f-67b6-4a95-b164-9f366cc5db91] Instance discovery was successful

I want to know how can I block these logs.

Why is this not a Bug or a feature Request?

• Because I am not sure if there is some way in Azure already that enables me to do this and its just that I am unaware of it.

Setup (please complete the following information if applicable):

• OS: MacOS
• IDE : IntelliJ
• 1.31.0

Information Checklist

• [ ✅ ] Query Added
• [ ✅ ] Setup information Added

[joshfree]

Thanks for the question @Shabirmean. @yaohaizh can you please follow up?

/cc @jianghaolu for any historical context on adal4j

[yaohaizh]

@jianghaolu does the adal4j log separate from the SDK logging? Can we control from the client runtime authentication side? Thanks

[Shabirmean]

Hi,

Is there any updates on this?

[weidongxu-microsoft]

This is not SDK feature. It only depends on the logging SDK and its config.

E.g. for slf4j simple, one can change log level

System.setProperty(org.slf4j.impl.SimpleLogger.DEFAULT_LOG_LEVEL_KEY, "WARN");

[FireDrunk]

My solution for this issue was:
logging.level.com.microsoft.aad.adal4j.AuthenticationAuthority=WARN
in application.properties

[ghost]

Hi @Shabirmean. Thank you for opening this issue and giving us the opportunity to assist. We believe that this has been addressed. If you feel that further discussion is needed, please add a comment with the text “/unresolve” to remove the “issue-addressed” label and continue the conversation.

[ghost]

Hi @Shabirmean, since you haven’t asked that we “/unresolve” the issue, we’ll close this out. If you believe further discussion is needed, please add a comment “/unresolve” to reopen the issue.