[jboss-jira] [JBoss JIRA] (WFWIP-280) Warnings propagated from io.smallrye.jwt.auth.* don't have assigned ID

[Jan Kasik (Jira)]

    [ https://issues.redhat.com/browse/WFWIP-280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13823829#comment-13823829 ] 

Jan Kasik commented on WFWIP-280:
---------------------------------

[~dlofthouse] What I'm afraid of is that having no logging IDs also means limited means of log monitoring and filtering. This might be crucial for some users since missing logging IDs can introduce false alarms in their established monitoring solutions and other unpredictable issues. The document also specifically mentions third-party projects:

{quote}
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.
{quote}

> 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)