[JBoss Messaging] - User null is NOT authenticated
by rnicholson10
On AS5.0.0.GA we occasionally get an error when we startup jboss on two different boxes when there is a bridge between them.
Here's the course of events:
1) Start both JBoss instances (on physically different boxes, no clustering)
2) Redeploy the bridge on one server (bug in this release)
3) and we get the ERROR below.
The strange thing is that the only way to get this error to go away is to restart both servers and deploy the bridge again.
If we remove the bridge file so it's not there on startup and deploy once startup is complete, we will never get the error below.
Just making you guys aware of this.
| 2009-03-03 12:11:18,423 WARN [org.jboss.jms.server.bridge.Bridge] jboss.messaging:name=TestBridge,service=Bridge Failed to set up connections
| javax.jms.JMSSecurityException: User null is NOT authenticated
| at org.jboss.jms.server.jbosssx.JBossASSecurityMetadataStore.authenticate(JBossASSecurityMetadataStore.java:223)
| at sun.reflect.GeneratedMethodAccessor402.invoke(Unknown Source)
| at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
| at java.lang.reflect.Method.invoke(Unknown Source)
| at com.sun.jmx.mbeanserver.StandardMetaDataImpl.invoke(Unknown Source)
| at javax.management.StandardMBean.invoke(Unknown Source)
| at org.jboss.mx.server.RawDynamicInvoker.invoke(RawDynamicInvoker.java:164)
| at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668)
| at org.jboss.mx.util.MBeanProxyExt.invoke(MBeanProxyExt.java:210)
| at $Proxy110.authenticate(Unknown Source)
| at org.jboss.jms.server.endpoint.ServerConnectionFactoryEndpoint.createConnectionDelegateInternal(ServerConnectionFactoryEndpoint.java:233)
| at org.jboss.jms.server.endpoint.ServerConnectionFactoryEndpoint.createConnectionDelegate(ServerConnectionFactoryEndpoint.java:171)
| at org.jboss.jms.server.endpoint.advised.ConnectionFactoryAdvised.org$jboss$jms$server$endpoint$advised$ConnectionFactoryAdvised$createConnectionDelegate$aop(ConnectionFactoryAdvised.java:108)
| at org.jboss.jms.server.endpoint.advised.ConnectionFactoryAdvised.createConnectionDelegate(ConnectionFactoryAdvised.java)
| at org.jboss.jms.wireformat.ConnectionFactoryCreateConnectionDelegateRequest.serverInvoke(ConnectionFactoryCreateConnectionDelegateRequest.java:91)
| at org.jboss.jms.server.remoting.JMSServerInvocationHandler.invoke(JMSServerInvocationHandler.java:143)
| at org.jboss.remoting.ServerInvoker.invoke(ServerInvoker.java:908)
| at org.jboss.remoting.transport.socket.ServerThread.completeInvocation(ServerThread.java:742)
| at org.jboss.remoting.transport.socket.ServerThread.processInvocation(ServerThread.java:695)
| at org.jboss.remoting.transport.socket.ServerThread.dorun(ServerThread.java:549)
| at org.jboss.remoting.transport.socket.ServerThread.run(ServerThread.java:230)
| at org.jboss.remoting.MicroRemoteClientInvoker.invoke(MicroRemoteClientInvoker.java:206)
| at org.jboss.remoting.Client.invoke(Client.java:1708)
| at org.jboss.remoting.Client.invoke(Client.java:612)
| at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.org$jboss$jms$client$delegate$ClientConnectionFactoryDelegate$createConnectionDelegate$aop(ClientConnectionFactoryDelegate.java:171)
| at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.invokeTarget(ClientConnectionFactoryDelegate$createConnectionDelegate_N3019492359065420858.java)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:111)
| at org.jboss.jms.client.container.StateCreationAspect.handleCreateConnectionDelegate(StateCreationAspect.java:81)
| at org.jboss.aop.advice.org.jboss.jms.client.container.StateCreationAspect_z_handleCreateConnectionDelegate_5452358.invoke(StateCreationAspect_z_handleCreateConnectionDelegate_5452358.java)
| at org.jboss.aop.joinpoint.MethodInvocation.invokeNext(MethodInvocation.java:102)
| at org.jboss.jms.client.delegate.ClientConnectionFactoryDelegate.createConnectionDelegate(ClientConnectionFactoryDelegate.java)
| at org.jboss.jms.client.JBossConnectionFactory.createConnectionInternal(JBossConnectionFactory.java:205)
| at org.jboss.jms.client.JBossConnectionFactory.createXAConnection(JBossConnectionFactory.java:128)
| at org.jboss.jms.client.JBossConnectionFactory.createXAConnection(JBossConnectionFactory.java:123)
| at org.jboss.jms.server.bridge.Bridge.createConnection(Bridge.java:859)
| at org.jboss.jms.server.bridge.Bridge.setupJMSObjects(Bridge.java:958)
| at org.jboss.jms.server.bridge.Bridge.setupJMSObjectsWithRetry(Bridge.java:1166)
| at org.jboss.jms.server.bridge.Bridge.access$1600(Bridge.java:66)
| at org.jboss.jms.server.bridge.Bridge$FailureHandler.run(Bridge.java:1512)
| at java.lang.Thread.run(Thread.java:595)
|
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214545#4214545
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214545
17 years, 1 month
[Security & JAAS/JBoss] - Forwarding to different webapps with given credentials (sing
by mjustin
Hello newsgroup,
which is the recommended strategy to implement a central login page (JSP) in JBoss which can forward the user to other web application based on user access rights?
The current setup is: we have two web apps, secured with JAAS
<jboss-web>
<security-domain>java:/jaas/app_1</security-domain>
</jboss-web>
and
<jboss-web>
<security-domain>java:/jaas/app_2</security-domain>
</jboss-web>
which use basic authentication.
We need one central login form for all web apps, and a single sign on, so we need to figure out a way to forward the user to a web app using his login information, so that the second web app does not ask for name / password again.
In a new web app, we implement a login form for user name / password and a database lookup using these values, which finds the webapps the user is authorized for, and then redirects him to this web apps entry page.
I tried to use a sendRedirect with username/password encoded in the URL (http://user:pass@site/context), but unfortunately Internet Explorer did not accept the request.
I am reading about Single Sign On and Web Authentication (Programmatic Web Login) with JBoss but still I am not sure which path to follow.
All apps are on the same virtual host. We are using version 4.2.0 of JBoss.
Is this a standard problem with a best practice to solve it?
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4214509#4214509
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4214509
17 years, 1 month