-
Notifications
You must be signed in to change notification settings - Fork 306
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
security using RolesAllowed not always working #2729
Comments
Now, after again a lot of testing on the problematic server, deploying the same war that did not work before, all of a sudden it works as expected. Caching server side of some form? |
Perhaps these are of influence? set configs.config.server-config.admin-service.das-config.autodeploy-enabled=false Thing is how it stands I cannot be sure security is ok, I have to test each deployment and if it doesn't work I don't have a fix. |
Can you provide a reproducible test case? |
No, that's the frustrating thing, all I can do is upload the war that I saw the problem with and scripts to make it run, it will be like the reproducer in #2625. If that's ok I can provide that, but I suspect it will just run fine. |
I will close now. If you can create a reusable test case then please indicate below and we will reopen. Alternatively if a reproducer is difficult this can be investigated under a support contract with Payara. |
Ok, sorry I left it open, haven't seen anything unusual anymore... |
glad to hear it is working. |
Description
Context
same application (exact same war), same payara version, same java version, identical, automated payara configuration
Problem
on one machine RolesAllowed works on the other I am allowed updates without the correct role.
Expected Outcome
When I do not have the correct role I am not allowed to execute annotated method
Current Outcome
When I do not have the correct role I am allowed to execute annotated method
Steps to reproduce (Only for bug reports)
No steps yet, but relevant snippets:
servlet setup
Environment
The text was updated successfully, but these errors were encountered: