StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<blockquote> <p>I've deleted the directory <code>domains/domainx/generated/policy/<appname>/</code> and completly redeployed (not just restarted) the app.. its working now as expected.</p> </blockquote> <p>The GlassFish documentation has an entry for this error:</p> <blockquote> <h2><a href="http://docs.sun.com/app/docs/doc/820-4339/abgjw?l=En&a=view" rel="noreferrer"><code>javax.ejb.AccessLocalException:</code> Client Not Authorized Error</a></h2> <h3>Description</h3> <p>Role-mapping information is available in Sun-specific XML (for example, <code>sun-ejb-jar.xml</code>), and authentication is okay, but the following error message is displayed:</p> <pre><code>[...INFO|sun-appserver-pe8.0|javax.enterprise.system.container.ejb|...| javax.ejb.AccessLocalException: Client not authorized for this invocation. at com.sun.ejb.containers.BaseContainer.preInvoke(BaseContainer.java:... at com.sun.ejb.containers.EJBObjectInvocationHandler.invoke(...) </code></pre> <h3>Solution</h3> <p>Check whether the EJB module (<code>.jar</code>) or web module (<code>.war</code>) is packaged in an application (<code>.ear</code>) and does not have role-mapping information in application level, Sun-specific, <code>sun-application.xml</code>. For any application (<code>.ear</code>), security role-mapping information must be specified in <code>sun-application.xml</code>. It is acceptable to have both module-level XML and application-level XML.</p> </blockquote> <p>I don't know if it makes sense in your context.</p> <p>If it doesn't, maybe have a look at the following thread <a href="http://old.nabble.com/Persisting-Entity:-javax.ejb.AccessLocalException:-Client-not--authorized-for-this-invocation.-td26848696.html" rel="noreferrer">Persisting Entity: javax.ejb.AccessLocalException: Client not authorized for this invocation</a>. One of the poster suggested to <em>set the logging level of the SECURITY Logger to FINE [so that] the Glassfish Policy subsystem will log a detailed message describing the nature of the failed permission check</em>. This might help. And I can't tell you if you're facing the same problem but the OP solved his issue by cleaning the generated policy files:</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload