May 2009 - jboss-dev-forums - Jboss List Archives

[Design of Management Features on JBoss] - EJBAccessException when trying to invoke methods on Profile

by ips

I've followed the instructions at http://www.jboss.org/community/wiki/RemoteAccesstoProfileService, including setting up a "profileservice" security domain containing a user "admin" with role "Administrator". I'm able to successfully lookup the remote EJB proxy, but I'm getting the following error when I try to invoke any methods on it: Exception in thread "main" javax.ejb.EJBAccessException: Caller unauthorized | at org.jboss.ejb3.security.RoleBasedAuthorizationInterceptorv2.invoke(RoleBasedAuthorizationInterceptorv2.java:199) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) | at org.jboss.ejb3.security.Ejb3AuthenticationInterceptorv2.invoke(Ejb3AuthenticationInterceptorv2.java:186) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) | at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:41) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) | at org.jboss.ejb3.BlockContainerShutdownInterceptor.invoke(BlockContainerShutdownInterceptor.java:67) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) | at org.jboss.aspects.currentinvocation.CurrentInvocationInterceptor.invoke(CurrentInvocationInterceptor.java:67) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) | at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java:415) | at org.jboss.ejb3.session.InvokableContextClassProxyHack._dynamicInvoke(InvokableContextClassProxyHack.java:53) | at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:91) | at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocationHandler.java:82) | at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:891) | at org.jboss.remoting.transport.socket.ServerThread.completeInvocation(ServerThread.java:744) | at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:697) | at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:524) | at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:232) | at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:211) | at org.jboss.remoting.Client.invoke(Client.java:1724) | at org.jboss.remoting.Client.invoke(Client.java:629) | at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:60) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) | at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) | at org.jboss.ejb3.security.client.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) | at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:74) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) | at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62) | at $Proxy7.invoke(Unknown Source) | at org.jboss.ejb3.proxy.impl.handler.session.SessionProxyInvocationHandlerBase.invoke(SessionProxyInvocationHandlerBase.java:207) | at org.jboss.ejb3.proxy.impl.handler.session.SessionProxyInvocationHandlerBase.invoke(SessionProxyInvocationHandlerBase.java:164) | at $Proxy2.getDomains(Unknown Source) | at test.EjbClient.main(EjbClient.java:35) | at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor.java:72) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) | at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInterceptor.java:61) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) | at org.jboss.ejb3.security.client.SecurityClientInterceptor.invoke(SecurityClientInterceptor.java:65) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) | at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:74) | at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102) | at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62) | at $Proxy7.invoke(Unknown Source) | at org.jboss.ejb3.proxy.impl.handler.session.SessionProxyInvocationHandlerBase.invoke(SessionProxyInvocationHandlerBase.java:207) | at org.jboss.ejb3.proxy.impl.handler.session.SessionProxyInvocationHandlerBase.invoke(SessionProxyInvocationHandlerBase.java:164) | at $Proxy2.getDomains(Unknown Source) | at test.EjbClient.main(EjbClient.java:35) The client code I'm using is at https://svn.jboss.org/repos/jopr/trunk/etc/jbas5-ejb-client/. Here's my security config from the server side: entry from default/conf/login-config.xml: <application-policy name="profileservice"> | <authentication> | <login-module code="org.jboss.security.auth.spi.UsersRolesLoginModule" | flag="required"> | <module-option name="usersProperties">props/profileservice-users.properties</module-option> | <module-option name="rolesProperties">props/profileservice-roles.properties</module-option> | </login-module> | </authentication> | </application-policy> default/conf/props/profileservice-users.properties: admin=admin default/conf/props/profileservice-roles.properties: admin=Administrator What am I missing? Thanks, Ian View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4228433#4228433 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4228433

15 years, 7 months

1
0
0 / 0

[Design of POJO Server] - Re: Caching of classes in BaseClassLoaderDomain

by alesj

I don't think you should solve this via catching the CNFE. The fix should be as you stated in JIRA - additional parameter. This is new code anyway, so adding extra parameters should not present any problems. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4228432#4228432 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4228432

15 years, 7 months

1
0
0 / 0

[Design of POJO Server] - Re: Caching of classes in BaseClassLoaderDomain

by bstansberry＠jboss.com

I went ahead and fixed the CNFE issue. https://jira.jboss.org/jira/browse/JBCL-101 View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4228426#4228426 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4228426

15 years, 7 months

1
0
0 / 0

[Design of JBoss Identity] - WS-Trust Integration in JBoss Identity

by anil.saldhana＠jboss.com

Currently Stefan has implemented a JBoss STS building on the object model in the JBoss Identity project. http://www.jboss.org/community/docs/DOC-13642 Given this, from an user's perspective, there are two options: Option A: ==== User configures the JBoss STS from JBID. In this case, the delegation of the core WS functionality needs to be sent to the JBossWS stack (irrespective of which underlying stack exists - native, cxf or metro). I think Stefan is pretty clear on this end (except that the client code has some JBossWS classes). Apart from that, it is plain Jax-WS usage. Option B: ===== User would like to use the WS-Sec implementation that is present in the JBossWS stack. During the usage, the user would like to delegate the ws-trust token handling to the JBID infrastructure. For this use case, Stefan needs to know what handlers/interceptor chain or such exists in the JBossWS stack to provide token handlers for ws-t (saml token profile, x509 etc). View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4228420#4228420 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4228420

15 years, 7 months

1
0
0 / 0

[Design of JBoss Identity] - Re: Identity Management integration with JBossAS5.

by anil.saldhana＠jboss.com

Jeff, we have a platform build workspace where we create the deployment archives for tomcat, JBAS etc..... we will have to update that workspace to use your stuff. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4228382#4228382 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4228382

15 years, 7 months

1
0
0 / 0

[Design of EJB 3.0] - Re: javax.ejb.EJB Annotations Outside EJB3 Components

by ALRubinger

Also I'd recommend injecting your EjbReferenceResolver delegate so you can swap impls. So instance we install one as an MC Bean: http://anonsvn.jboss.org/repos/jbossas/projects/ejb3/trunk/core/src/main/... ...grep for bean name "org.jboss.ejb3.EjbReferenceResolver". S, ALR View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4228367#4228367 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4228367

15 years, 7 months

1
0
0 / 0

[Design of EJB 3.0] - Re: javax.ejb.EJB Annotations Outside EJB3 Components

by jaikiran

anonymous wrote : is the construction of the ejb reference right in the following code? Looks fine :) Just a note though, which ALR already mentioned, the FirstMatchEjbReferenceResolver isn't constrained by the deployment unit passed to it. Consider your application is pacakged as : | XYZ.ear | | | |--- A.jar | | | |--- B.jar Assuming a deployment unit corresponding to A.jar (which belongs to XYZ.ear) is passed to this resolver, the resolver will not just look for the right EJB within A.jar but will also look for beans from within B.jar. If you want the behaviour to be different, then you will have to use a different implementation other than the FirstMatchEjbReferenceResolver. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4228359#4228359 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4228359

15 years, 7 months

1
0
0 / 0

[Design of JBoss Admin Console] - Re: Failed to parse source: Store not found as a child of Ma

by PeterJ

The error message seems pretty clear to me, including the suggested solution. Besides, it must not be that urgent if you did not post the contents of the context.xml file, nor describe the app that contains this file. Why did you post into this forum? What does this error have to do with the design of the admin console? View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4228344#4228344 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4228344

15 years, 7 months

1
0
0 / 0

[Design of Messaging on JBoss (Messaging/JBoss)] - User documentation for 2.0.0.beta1

by jmesnil

I've started an outline for the user documentation for 2.0.0.beta1 http://www.jboss.org/community/wiki/JBM20Beta1UserGuideOutline As for the examples, we could use this wiki page to split the doc task in smaller tasks and do them in parallel. One thing not clear for me is if we have made a final decision about the documentation source. Currently we use docbook but Tim talked about using OpenOffice to write the doc. Does that mean the source will still be in docbook or do we keep it in ODF and generate the docbook from it? I'm non-plussed about using OpenOffice for tech documentation (or any wysiwig editor for that matter) and I don't know how well docbook is supported. The only requirement I have is the ability to create permanent anchors for sections in HTML exportation so that I can link to them from the examples. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4228342#4228342 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4228342

15 years, 7 months

1
0
0 / 0

[Design of EJB 3.0] - Re: javax.ejb.EJB Annotations Outside EJB3 Components

by richard.opalka＠jboss.com

Little fix, my getEjbReference() method looks like this now (because of @EJB annotation defaults): private EjbReference getEjbReference(EJB ejbAnnotation, Class<?> type) { String beanInterface = ejbAnnotation.beanInterface().getName(); if (java.lang.Object.class.getName().equals(beanInterface)) { beanInterface = type.getName(); } return new EjbReference(ejbAnnotation.beanName(), beanInterface, ejbAnnotation.mappedName()); } View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4228331#4228331 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4228331

15 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jboss-dev-forums May 2009