[jboss-jira] [JBoss JIRA] Created: (EJBTHREE-1655) Get the "security" tutorial working on JBossAS-5.0 GA

jaikiran pai (JIRA) jira-events at lists.jboss.org
Tue Dec 23 04:08:54 EST 2008


Get the "security" tutorial working on JBossAS-5.0 GA
-----------------------------------------------------

                 Key: EJBTHREE-1655
                 URL: https://jira.jboss.org/jira/browse/EJBTHREE-1655
             Project: EJB 3.0
          Issue Type: Sub-task
          Components: Documentation
    Affects Versions: 1.0.0-Beta10
            Reporter: jaikiran pai
            Assignee: jaikiran pai


Right now, the security tutorial fails to access the secure EJB with the following exception:

[java] Exception in thread "main" javax.ejb.EJBAccessException: Invalid User
     [java]     at org.jboss.ejb3.security.Ejb3AuthenticationInterceptorv2.invoke(Ejb3Authentication
Interceptorv2.java:137)
     [java]     at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
     [java]     at org.jboss.ejb3.ENCPropagationInterceptor.invoke(ENCPropagationInterceptor.java:41
)
     [java]     at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
     [java]     at org.jboss.ejb3.asynchronous.AsynchronousInterceptor.invoke(AsynchronousIntercepto
r.java:106)
     [java]     at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
     [java]     at org.jboss.ejb3.BlockContainerShutdownInterceptor.invoke(BlockContainerShutdownInt
erceptor.java:65)
     [java]     at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
     [java]     at org.jboss.aspects.currentinvocation.CurrentInvocationInterceptor.invoke(CurrentIn
vocationInterceptor.java:67)
     [java]     at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
     [java]     at org.jboss.ejb3.stateless.StatelessContainer.dynamicInvoke(StatelessContainer.java
:486)
     [java]     at org.jboss.ejb3.session.InvokableContextClassProxyHack._dynamicInvoke(InvokableCon
textClassProxyHack.java:56)
     [java]     at org.jboss.aop.Dispatcher.invoke(Dispatcher.java:91)
     [java]     at org.jboss.aspects.remoting.AOPRemotingInvocationHandler.invoke(AOPRemotingInvocat
ionHandler.java:82)
     [java]     at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:908)
     [java]     at org.jboss.remoting.transport.socket.ServerThread.completeInvocation(ServerThread.
java:742)
     [java]     at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.j
ava:695)
     [java]     at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:522)
     [java]     at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:230)
     [java]     at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:
206)
     [java]     at org.jboss.remoting.Client.invoke(Client.java:1708)
     [java]     at org.jboss.remoting.Client.invoke(Client.java:612)
     [java]     at org.jboss.aspects.remoting.InvokeRemoteInterceptor.invoke(InvokeRemoteInterceptor
.java:60)
     [java]     at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
     [java]     at org.jboss.aspects.tx.ClientTxPropagationInterceptor.invoke(ClientTxPropagationInt
erceptor.java:61)
     [java]     at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
     [java]     at org.jboss.ejb3.security.client.SecurityClientInterceptor.invoke(SecurityClientInt
erceptor.java:65)
     [java]     at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
     [java]     at org.jboss.ejb3.remoting.IsLocalInterceptor.invoke(IsLocalInterceptor.java:76)
     [java]     at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
     [java]     at org.jboss.aspects.remoting.PojiProxy.invoke(PojiProxy.java:62)
     [java]     at $Proxy3.invoke(Unknown Source)
	

There has been a change in JBoss-5 in the way a standalone client can propagate user credentials to the EJB hosted on the server. The changes have been mentioned in this forum thread http://www.jboss.com/index.html?module=bb&op=viewtopic&t=144021. However, that does not seem to be working with JBoss-5.0 GA.

This issue is for identifying the root cause and fixing the same.


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        



More information about the jboss-jira mailing list