JACC Policy Provider: Failed Permission Check -- issue suddenly appeared!

[Keith.P Smith]

Wasn't sure which forum really suited this so put it under general...

Just wondering, has anyone come across the issue where for no apparent reason Glassfish starts throwing this error:

[#|2010-03-15T00:23:22.325+0000|INFO|glassfishv3.0|javax.enterprise.system.core.security|_ThreadID=24;_ThreadName=Thread-1;|JACC Policy Provider: Failed Permission Check, context(myproject/client_war)- permission((javax.security.jacc.WebUserDataPermission /pages/signin/enter-details.jsf POST))|#]

[#|2010-03-15T00:23:22.325+0000|INFO|glassfishv3.0|javax.enterprise.system.core.security|_ThreadID=24;_ThreadName=Thread-1;|JACC Policy Provider: Failed Permission Check, context(myproject/client_war)- permission((javax.security.jacc.WebUserDataPermission /pages/signin/enter-details.jsf POST:CONFIDENTIAL))|#]

I have a JSF/EJB app which has been working fine for weeks now, then today I redeployed teh EAr and suddenly started getting this, the error is thrown at the point of clicking any commandButton (essentially a form post) and I can't see anything that is causing it.

I have had a look around the forums but can find no definitive reason.

Cheers

KS

[mark dufresne]

Any luck on solving this error? I'm receiving the same thing.

[Alex Ka]

I got the same message :

[#|2010-08-11T10:09:32.522+0300|INFO|glassfish3.0.1|javax.enterprise.system.core.security|_ThreadID=75;_ThreadName=Thread-1;|JACC Policy Provider: Failed Permission Check, context(primer/primer)- permission((javax.security.jacc.WebUserDataPermission  GET))|#]
[#|2010-08-11T10:09:32.522+0300|INFO|glassfish3.0.1|javax.enterprise.system.core.security|_ThreadID=75;_ThreadName=Thread-1;|JACC Policy Provider: Failed Permission Check, context(primer/primer)- permission((javax.security.jacc.WebUserDataPermission  GET:CONFIDENTIAL))|#]

The browser showed:
HTTP Status 403 - Access to the requested resource has been denied

I did an undeploy/deploy and now it seems ok.

[mark dufresne]

My apologies for not posting sooner. I also resolved this issue. I performed an un-deploy -> deploy, but I don't remember if that made the issue go away for me. I do remember spending a morning going through the Java EE 6 Security section, then configuring security for my web application, afterwards never seeing this issue again. But I don't know if the issue went away after the re-deploy or the security config.

[Alex Ka]

Well, I'm working on a new project so no security configurations involved. It was really strange to see this error.

On the other hand I'm using emergent technologies like PrettyFaces and the new Glassfish, I'm tweaking the server and playing with Java EE 6 (maven+hotdeploy) so normally I would break something and then have to check what went wrong and how I should use the technology.

It's good that the problem disappeared after cleaning up.

[mark dufresne]

I am receiving the error again... so both suggestions I gave earlier are suspect to fixing the issue in my case... hope I didn't lead anyone down the wrong path... I guess I'll be checking my security configuration again...