[Design of Security on JBoss] - Problem with SSL configuration
by xsedlacp
Hi,
I tried configuration explained in JBoss documentation (http://docs.jboss.org/jbossas/admindevel326/html/ch8.chapter.html#d0e18946 ).
I defined securityDomain
<mbean code="org.jboss.security.plugins.JaasSecurityDomain"
| name="jboss.security:service=JaasSecurityDomain,domain=RMI+SSL">
| <constructor><arg type="java.lang.String" value="RMI+SSL"/></constructor>
| <attribute name="KeyStoreURL">jboss.keystore</attribute>
| <attribute name="KeyStorePass">rmi+ssl</attribute>
| </mbean>
and I defined invoker
<mbean code="org.jboss.invocation.jrmp.server.JRMPInvoker" name="jboss:service=invoker,socketType=SSL,type=jrmp">
| <attribute name="RMIObjectPort">14445</attribute>
| <attribute name="RMIClientSocketFactory">org.jboss.security.ssl.RMISSLClientSocketFactory</attribute>
| <attribute name="RMIServerSocketFactory">org.jboss.security.ssl.RMISSLServerSocketFactory</attribute>
| <attribute name="SecurityDomain">java:/jaas/RMI+SSL</attribute>
| <depends>jboss.security:service=JaasSecurityDomain,domain=RMI+SSL</depends>
| </mbean>
But this invoker never starts
13:07:17,453 WARN [ServiceController] Problem starting service jboss:service=invoker,socketType=SSL,type=jrmp
javax.naming.NameNotFoundException: TransactionPropagationContextExporter not bound
at org.jnp.server.NamingServer.getBinding(NamingServer.java:527)
at org.jnp.server.NamingServer.getBinding(NamingServer.java:535)
at org.jnp.server.NamingServer.getObject(NamingServer.java:541)
at org.jnp.server.NamingServer.lookup(NamingServer.java:294)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:621)
at org.jnp.interfaces.NamingContext.lookup(NamingContext.java:583)
at javax.naming.InitialContext.lookup(Unknown Source)
at org.jboss.invocation.jrmp.server.JRMPInvoker.startService(JRMPInvoker.java:303)
at ...
Can somenone help me, how to configure using SSL with JBoss. I am using JBoss version 3.2.8SP1.
any help would be appriciate ...
Thanks
Peter
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4108362#4108362
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4108362
18 years, 4 months
[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Refactoring on delegates
by clebert.suconic＠jboss.com
anonymous wrote :
| I don't want to see any state or delegates methods remainaing - that's a half way hack. There should just be ConnectionFactory, Connection, Session and Consumer classes in the agnostic layer - all the code from the delegate, state and aspect classes should end up in those classes.
|
that's ok... but looking at the code now (with all the fields we have on states) it seems that would be reasonable to keep separated data for Connection, Session.. etc... like SessionData, ConnectionData and so on... This wouldn't be like the SessionState we have now.. just a separated POJO.
anonymous wrote : I don't think we have need of any interceptors (apart from * see below), ClosedInterceptor can be easily implemented without being an interceptor.
|
| Failover doesn't need interceptors either. We just have a simple valve on Jeff's dispatcher send methods. So no need for a factory or anything else to create any proxies.
|
That's exactly what I thought one hour after I sent the post/finished the doc (I just think about the Customer's needs on interceptors tough). I thought I would be able to send another post before you wake up in London (6 hours time difference) but apparently you never sleep :-)
anonymous wrote : The current wiki page describes various intermediate versions. That's fine, but I'm not so interested in the intermediate ones, but really the end goal. I think it's a bit confusing describing intermediate stages.
|
I was more concerned about how to get on the final model, than the final model itself.
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4108287#4108287
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4108287
18 years, 4 months
[Design of Messaging on JBoss (Messaging/JBoss)] - Re: Refactoring on delegates
by timfox
A few initial comments.
The "agnostic" layer doesn't talk directly to MINA - it talks to Jeff's new Dispatcher which in turn talks to an abstracted MINA-like set of interfaces (so they can be mocked) which in turn talks to MINA.
I don't want to see any state or delegates methods remainaing - that's a half way hack. There should just be ConnectionFactory, Connection, Session and Consumer classes in the agnostic layer - all the code from the delegate, state and aspect classes should end up in those classes.
Actually ConnectionFactory, Connection, Session and Consumer should be interfaces, not concrete classes so they can be easily mocked.
I don't think we have need of any interceptors (apart from * see below), ClosedInterceptor can be easily implemented without being an interceptor.
Failover doesn't need interceptors either. We just have a simple valve on Jeff's dispatcher send methods. So no need for a factory or anything else to create any proxies.
The current wiki page describes various intermediate versions. That's fine, but I'm not so interested in the intermediate ones, but really the end goal. I think it's a bit confusing describing intermediate stages.
* - one place where an interceptor will be necessary is to allow an extension point for users to add their own client and server side interceptor(s) - this can probably be a simple java.lang.reflect.Proxy implementation
View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4108270#4108270
Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4108270
18 years, 4 months