quarkus: Random HTTP 401 failures from endpoints secured with `@RolesAllowed`

I tested and could not reproduce the issue Thanks!

I created https://github.com/quarkusio/quarkus-github-bot/issues/342 .

No, in order to test the fix, you would have to follow build main https://github.com/quarkusio/quarkus/blob/main/CONTRIBUTING.md#building-main then use quarkus version 999-SNAPSHOT and group id io.quarkus (not a platform in it).

Great stuff, thanks for your help Julien @jponge

Yes

On Tue, Jun 27, 2023 at 2:27 PM Sergey Beryozkin @.***> wrote:

Hey @jponge https://github.com/jponge @cescoffier https://github.com/cescoffier Looks like #34249 https://github.com/quarkusio/quarkus/pull/34249 got this fixed, right ?

— Reply to this email directly, view it on GitHub https://github.com/quarkusio/quarkus/issues/33602#issuecomment-1609404231, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAAGK2IDXOCV5XFAA3KMQ5DXNLGTNANCNFSM6AAAAAAYOV5B5Q . You are receiving this because you were mentioned.Message ID: @.***>

There’s a fix in Mutiny.

Yea, but this test is exactly the code that is run in HttpSecurityRecorder where the bug is. I was trying to reproduce the bug, not demonstrate memoization 😃

Hey @michalvavrik Thanks for spending the time on this one. I wonder, if there is indeed a race condition with the Vert.x context propagation. Hey @cescoffier @jponge, can you check please https://github.com/quarkusio/quarkus/issues/33602#issuecomment-1575635342 ? Might be an interesting issue related to the way Mutiny handles it

I’ll have a look.

Hello @sberyozkin I updated the project to log, for incoming requests, an internal ID, the authorization header and the principal name. For the failing request, you will notice that the authorization header is present, but the principal is null.

Thanks for the heads up