[
https://issues.redhat.com/browse/WFWIP-280?page=com.atlassian.jira.plugin...
]
Brian Stansberry commented on WFWIP-280:
----------------------------------------
There are many projects in WildFly that do not follow that standard.
Re "Messages generated by third-party code should be caught by the consumer, which
will typically be a JBoss project. The consumer should then map the third-party framework
error into something that is both meaningful to the user and follows this
convention." -- that's totally impractical. For messages that basically means the
logging layer has some sort of callout for every INFO or above message where we analyze or
something and do a translation. Probably some pluggable set of translators, one per
subsystem, that can be invoked until one marks the message as translated. Most messages
not needing translation as they were produced with an id. For errors we stick catch
(Throwable) blocks all over the place where we call into external code?
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)