Open thinkgear opened 1 year ago
Any update on this issue?
Hello @thinkgear,
Yes, I managed to reproduce the error on the latest Payara version. It seems to be consistent across multiple environments. I have escalated the issue to the Platform development team, issue identifier: FISH-6922
. Apologies for the delay in my response.
Thanks for the update @felixif. Hoping for an early resolution.
Brief Summary
I am using the latest version of Payara 5.2022.4
I have enabled the monitoring console on the server. So __monitoringconsole app is deployed.
Now when I deploy my war app with @RolesAllowed annotation set on resources, and the below payara-web.xml, everything works fine the first time but raises 401 exception with the below log when I restart the domain/server.
If I disable monitoring console, everything works fine on restart server also. I don't know why this weird issue.
Maybe this could be the issue: https://github.com/payara/Payara/issues/2841#issuecomment-795114867
Expected Outcome
@RolesAllowed annotation should work as expected and should not raise 401 on domain/server restart.
Current Outcome
Request to resource returns 401 unauthorized and the above log in server.log
Reproducer
Enable monitoring console in domain. Deploy a war with @RolesAllowed enabled. Set jaxrs-roles-allowed-enabled to false in payara-web.xml. Access the resource after restarting the server.
Operating System
Ubuntu 22.04
JDK Version
Zulu JDK 1.8.0_352-b08
Payara Distribution
Payara Server Web Profile