[Security & JAAS/JBoss] - Re: JBoss Federated SSO: Does it support?
by ArjunDhar
Thanks Sohil. Thats was very helpful indeed.
On a less critical note and as tech discussion:
Once a person has logged in VIA SSO, I assume JBoss SSO design creates a session on the SSO server. So that for a "Passprt" like token functionality; when a person clicks a link on the browser (say) and moves to another application, one cannot pass credentials. There would be some sort of a session cookie passed on with an encrypted key ..or some similar mechanism.
Now, the point being that if the 4th App needs to get some info from the SSO service (like users phone number)*; it can pass the key, thus not compromising on the actual user credentials. Hence that key reference would be maintained on an SSO session.
*why would an SSO return phone number?
Ans) Because one of the ideas of SSO is also maintain common credential data which may include additional fields. In that scenario a service may request for additonal info. Now this part would not be out of the of box, thats ok. But the rest of the discussion is valid.
The issue that kicks in is that SSO sessiosn and local sessions may be out of synch. And thats ok, coz if my SSO session times out in 30 minuts. I may not want o enfore that on the session of a local application which may have its setting for 3 hours.
If the person needs to move to another site, then sure he wil require re authentication. This is how some SSO get the job done.
So thats what I was referring to as "SSO Session".
But I really appreciate the response, it has me excited to dig through the code. :)
...As for the Valve. I saw the code; but Valves connect to the container (engine, host, context), while filters to servlets. Anyway, can always tweak that code basedon our requirement.
Thanks! What I really am happy about is I dont need to JBossSX at this phase to complicate my life :) Thanks again.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4122917#4122917
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4122917
18 years, 6 months
[JBoss Messaging] - Re: How Do I Run JBoss Messaging TestSuite in Q1 2008
by jmesnil
"cmagidcmagid" wrote : Thank you so much for your reply.
| I will need more clarification as to the target of the jbm-beans.xml file you mentioned above. I can not find that file on my system. I am guessing that these instructions are out of date and I will need to install the AS before I can get the tests working. I am including the stacktrace and the FIT test results below. thnx in advance.
|
I think I found out what the bug is.
Can you do me a favor to confirm what I suspect?
Can you change the settings in jboss-messaging/src/etc/server/default/deploy/jbm-beans.xml, line 100 from
| <parameter>tcp</parameter>
|
to
| <parameter>TCP</parameter>
|
and rerun the tests?
It seems that JBoss Microcontainer is confused between the 2 constructors of MinaService.
I don't get the problem on my JVM (1.5.0_13-b05 on Linux) but I don't have access to a Windows box to check it on the same JVM than yours.
thanks
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4122913#4122913
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4122913
18 years, 6 months
[Messaging, JMS & JBossMQ] - JbossMQ not started?(jboss-4.2.1.GA)
by daedalus_hammer
Hi
I'm trying to deploy a MDB (it's not written by me and on other setups it works fine), but I get this error:
10:25:25,006 INFO [JMSContainerInvoker] Waiting for reconnect internal 10000ms for SSELogQueue2MDB
10:25:35,006 INFO [JMSContainerInvoker] Trying to reconnect to JMS provider for SSELogQueue2MDB
10:25:42,928 ERROR [JMSContainerInvoker] Reconnect failed: JMS provider failure detected for SSELogQueue2MDB
javax.naming.CommunicationException: Could not obtain connection to any of these urls: 127.0.0.1:1100 and discovery failed with error: javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out] [Root exception is javax.naming.Communi
cationException: Failed to connect to server 127.0.0.1:1100 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server 127.0.0.1:1100 [Root exception is java.net.ConnectException: Connection refused: connect]]]
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1416)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:596)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:589)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at org.jboss.ejb.plugins.jms.DLQHandler.createService(DLQHandler.java:182)
at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:260)
at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:188)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerStartDelivery(JMSContainerInvoker.java:510)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker$ExceptionListenerImpl$ExceptionListenerRunnable.run(JMSContainerInvoker.java:1428)
at java.lang.Thread.run(Thread.java:595)
Caused by: javax.naming.CommunicationException: Failed to connect to server 127.0.0.1:1100 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server 127.0.0.1:1100 [Root exception is java.net.ConnectException: Connection refused: connect]]
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:269)
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1387)
... 9 more
Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server 127.0.0.1:1100 [Root exception is java.net.ConnectException: Connection refused: connect]
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:243)
... 10 more
Caused by: java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:519)
at java.net.Socket.connect(Socket.java:469)
at java.net.Socket.(Socket.java:366)
at java.net.Socket.(Socket.java:266)
at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:84)
at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:77)
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:239)
... 10 more
In web-console/System/JMXMbeans Jboss.Mq seems to be deployed fine, and the settings are java.naming.provider.url=127.0.0.1:1100 and jnp.discoveryPort=1102, but when I try telneting to 1100 or 1102 I can't get a connection (just like the error above).
I'm clueless as to why this happens, and any help would be greatly appreciated.
Thanks!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4122910#4122910
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4122910
18 years, 6 months
[Messaging, JMS & JBossMQ] - JbossMQ not started?(jboss-4.2.1.GA)
by daedalus_hammer
Hi
I'm trying to deploy a MDB (it's not written by me and on other setups it works fine), but I get this error:
10:25:25,006 INFO [JMSContainerInvoker] Waiting for reconnect internal 10000ms for SSELogQueue2MDB
10:25:35,006 INFO [JMSContainerInvoker] Trying to reconnect to JMS provider for SSELogQueue2MDB
10:25:42,928 ERROR [JMSContainerInvoker] Reconnect failed: JMS provider failure detected for SSELogQueue2MDB
javax.naming.CommunicationException: Could not obtain connection to any of these urls: 127.0.0.1:1100 and discovery failed with error: javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out] [Root exception is javax.naming.Communi
cationException: Failed to connect to server 127.0.0.1:1100 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server 127.0.0.1:1100 [Root exception is java.net.ConnectException: Connection refused: connect]]]
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1416)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:596)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:589)
at javax.naming.InitialContext.lookup(InitialContext.java:351)
at org.jboss.ejb.plugins.jms.DLQHandler.createService(DLQHandler.java:182)
at org.jboss.system.ServiceMBeanSupport.jbossInternalCreate(ServiceMBeanSupport.java:260)
at org.jboss.system.ServiceMBeanSupport.create(ServiceMBeanSupport.java:188)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker.innerStartDelivery(JMSContainerInvoker.java:510)
at org.jboss.ejb.plugins.jms.JMSContainerInvoker$ExceptionListenerImpl$ExceptionListenerRunnable.run(JMSContainerInvoker.java:1428)
at java.lang.Thread.run(Thread.java:595)
Caused by: javax.naming.CommunicationException: Failed to connect to server 127.0.0.1:1100 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server 127.0.0.1:1100 [Root exception is java.net.ConnectException: Connection refused: connect]]
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:269)
at org.jnp.interfaces.NamingContext.checkRef(NamingContext.java:1387)
... 9 more
Caused by: javax.naming.ServiceUnavailableException: Failed to connect to server 127.0.0.1:1100 [Root exception is java.net.ConnectException: Connection refused: connect]
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:243)
... 10 more
Caused by: java.net.ConnectException: Connection refused: connect
at java.net.PlainSocketImpl.socketConnect(Native Method)
at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333)
at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195)
at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182)
at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366)
at java.net.Socket.connect(Socket.java:519)
at java.net.Socket.connect(Socket.java:469)
at java.net.Socket.(Socket.java:366)
at java.net.Socket.(Socket.java:266)
at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:84)
at org.jnp.interfaces.TimedSocketFactory.createSocket(TimedSocketFactory.java:77)
at org.jnp.interfaces.NamingContext.getServer(NamingContext.java:239)
... 10 more
In web-console/System/JMXMbeans Jboss.Mq seems to be deployed fine, and the settings are java.naming.provider.url=127.0.0.1:1100 and jnp.discoveryPort=1102, but when I try telneting to 1100 or 1102 I can't get a connection (just like the error above).
I'm clueless as to why this happens, and any help would be greatly appreciated.
Thanks!
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4122909#4122909
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4122909
18 years, 6 months