[
https://issues.redhat.com/browse/WFWIP-280?page=com.atlassian.jira.plugin...
]
Darran Lofthouse commented on WFWIP-280:
----------------------------------------
Reviewing the code within SmallRye JWT the primary issue that I actually see is not the
content of the error messages i.e. the lack of ID but the level and verbosity of the
messages.
Under normal operation a server should expect to handle both valid and invalid tokens,
although an invalid token is an error it is still normal and so should not result in per
request logging so I have raised the following PR to see if they will accept lowering the
log levels: -
https://github.com/smallrye/smallrye-jwt/pull/156
As a third party project they can reject some / all of these proposed changes. A short
term back up could be to turn off SmallRye JWT logging in our default configuration,
longer term something that could be interesting to discuss is if internally we could
re-map the levels for specific categories.
Warnings propagated from io.smallrye.jwt.auth.* don't have
assigned ID
----------------------------------------------------------------------
Key: WFWIP-280
URL:
https://issues.redhat.com/browse/WFWIP-280
Project: WildFly WIP
Issue Type: Bug
Components: MP JWT
Reporter: Jan Kasik
Assignee: Darran Lofthouse
Priority: Critical
Warning which are propagated to log from io.smallrye.jwt.auth package don't have
assigned logging ID.
Example:
{code}
11:52:50,705 WARN [io.smallrye.jwt.auth.mechanism.JWTHttpAuthenticationMechanism]
(default task-1) Unable to validate bearer token: Failed to verify token:
io.smallrye.jwt.auth.principal.ParseException: Failed to verify token
{code}
--
This message was sent by Atlassian Jira
(v7.13.8#713008)