Re: How to troubleshoot a JWT issue ?

------DDF5FPG97K498DXR6UD3SDYQ7JP1CI
Content-Type: text/plain;
 charset=utf-8
Content-Transfer-Encoding: quoted-printable

Think it misses details=2E Do you have a reverse p or gateway in front of i=
t? Some might run into header size Issues=2E

You could add a ContainerRequestFilter to log all incoming requests to con=
firm whether your request reaches the app before security filters (with app=
ropriate priority)=2E

Or you add a RequestDumperValve for more information in your server=2Exml:=
 https://tomcat=2Eapache=2Eorg/tomcat-10=2E1-doc/config/filter=2Ehtml#Reque=
st_Dumper_Filter
, so you get more details=2E

Gru=C3=9F=20
Richard=20


Am 12=2E Juni 2025 18:25:11 MESZ schrieb COURTAULT Francois <francois=2Eco=
urtault@thalesgroup=2Ecom=2EINVALID>:
>THALES GROUP LIMITED DISTRIBUTION to email recipients
>
>Hello everyone,
>
>We have a Rest application that uses the microprofile-jwt-auth-spec-2=2E1=
 specification=2E
>
>We  have an issue with some of our requests, having a JWT in the Authoriz=
ation header (eg Authorization: Bearer <JWT 64 bits encoded>),  where we ge=
t a 400 (BAD REQUEST) and we don=E2=80=99t know why =E2=98=B9=E2=80=99
>No stack trace written in the logs=2E
>For such behavior,  it seems that the request doesn=E2=80=99t reach the a=
pplication=2E
>
>What could we do in order to troubleshoot this kind of issue ?
>
>Best Regards=2E
>
>
>
>

------DDF5FPG97K498DXR6UD3SDYQ7JP1CI--