Ex: Re: deprecation warnings only at TRACE log level?

[Paul B. Henson]

On Mon, Nov 13, 2023 at 01:06:30PM +0000, Cantor, Scott via users wrote:
> That's not possible, so you're misinterpreting or misconfiguring the
> logging settings in some way.

I'm literally just changing this:

	<variable name="idp.loglevel.idp" value="${idp.loglevel.idp:-INFO}" />

to this:

	<variable name="idp.loglevel.idp" value="TRACE" />

With the first one:

idp-dev-02 ~ # grep DEPRECATED /var/log/idp/idp-warn.log
[nada]

with the second:

idp-dev-02 ~ # grep DEPRECATED /var/log/idp/idp-warn.log

2023-11-13 11:43:19,014 - / - WARN [DEPRECATED:139] - Java class method 'requestContext.getId()': This will be removed in the next major version of this software
2023-11-13 11:43:19,015 - / - WARN [DEPRECATED:135] - Java class method 'requestContext.getPrincipalName()': This will be removed in the next major version of this software; replacement is resolutionContext.getPrincipal()
2023-11-13 11:43:19,015 - / - WARN [DEPRECATED:135] - Java class method 'requestContext.getPeerEntityId()': This will be removed in the next major version of this software; replacement is resolutionContext.getAttributeRecipientID()
2023-11-13 11:43:19,015 - / - WARN [DEPRECATED:135] - Java class method 'requestContext.getLocalEntityId()': This will be removed in the next major version of this software; replacement is resolutionContext.getAttributeIssuerID()

> They aren't spurious messages, you are calling them (as Rod said
> probably in a script).

<shrug>. Guess I'll find out when I update to idp 5, I sure don't see any at
all for a couple, and the others I don't think are the ones being logged.

idp-dev-02 shibboleth-idp # grep -r getLocalEntityId 

idp-dev-02 shibboleth-idp # grep -r getPeerEntityId


-- 
Paul B. Henson  |  (909) 979-6361  |  http://www.cpp.edu/~henson/
Operating Systems and Network Analyst  |  henson at cpp.edu
California State Polytechnic University  |  Pomona CA 91768