Built with Seam
You can find the full source code for this website in the Seam package in the directory /examples/wiki. It is licensed under the LGPL.
| Online: | 24 Members of 4546 |
| Forum: Seam Users |
 |
05. Aug 2008, 18:00 CET | Link |
Hello,
i have some ejbs usable as webservices with role-based access control via ejb container security methods (ejb-jar.xml descriptor).
Now i must use these EJBs from an seam-web-application, but the seam-Identity would not be propagated to the ejb-container security. I've found some older postings (old forum) but without a solution.
How can i manage this? Both are using the same jaas-security-domain but each call results in:
17:44:58,583 ERROR [RoleBasedAuthorizationInterceptor] Insufficient permissions, principal=null, requiredRoles=[Direktor], principalRoles=[]
17:44:58,618 ERROR [STDERR] 05.08.2008 17:44:58 com.sun.facelets.FaceletViewHandler handleRenderException
SCHWERWIEGEND: Error Rendering View[/home.xhtml]
i have some ejbs usable as webservices with role-based access control via ejb container security methods (ejb-jar.xml descriptor).
Now i must use these EJBs from an seam-web-application, but the seam-Identity would not be propagated to the ejb-container security. I've found some older postings (old forum) but without a solution.
How can i manage this? Both are using the same jaas-security-domain but each call results in:
17:44:58,583 ERROR [RoleBasedAuthorizationInterceptor] Insufficient permissions, principal=null, requiredRoles=[Direktor], principalRoles=[]
17:44:58,618 ERROR [STDERR] 05.08.2008 17:44:58 com.sun.facelets.FaceletViewHandler handleRenderException
SCHWERWIEGEND: Error Rendering View[/home.xhtml]
