Mac command line tools run into this potentially blocking issue, starting sometime between ADAL 2.5.1 & 2.7.4 releases. Calling acquireToken APIs leads to the following message piped to the stderr, that cannot be controlled by the caller. Some such tools cannot function correctly if any stderr output is seen by the caller, and such an error will definitely be confusing to the users as well.
ERROR: createEncodedCachedResponseAndRequestForXPCTransmission - Invalid protocol-property list - CFURLRequestRef. protoProps=<CFBasicHash 0x7fde2290c7c0 [0x7fffa9a228f0]>{type = mutable dict, count = 1,
entries =>
0 : <CFString 0x10c2634e8 [0x7fffa9a228f0]>{contents = "context"} = <ADWebAuthRequest: 0x7fde229085e0>
Based on discussion in #1026, this seems to be caused due to carrying the whole request context in ADURLProtocol:
[NSURLProtocol setProperty:context forKey:@"context" inRequest:request];
For GUI apps, this error gets piped to the system Console.app, which is harmless, but not ideal either. For command line tools, this can be a blocking issue depending on their usage.
@oldalton
Mac command line tools run into this potentially blocking issue, starting sometime between ADAL 2.5.1 & 2.7.4 releases. Calling acquireToken APIs leads to the following message piped to the stderr, that cannot be controlled by the caller. Some such tools cannot function correctly if any stderr output is seen by the caller, and such an error will definitely be confusing to the users as well.
Based on discussion in #1026, this seems to be caused due to carrying the whole request context in ADURLProtocol:
For GUI apps, this error gets piped to the system Console.app, which is harmless, but not ideal either. For command line tools, this can be a blocking issue depending on their usage.
@oldalton