[JNDI/Naming/Network] - Re: Jboss 4.0.5 Multiple Interfaces
by PeterJ
I don't think that this is under the control of JBoss AS. It just sends something out and it is the TCP/IP stack that determines how the data will be routed (that is, via which address). I don't know how, or if, you can configure the TCP/IP stack to send via a particular address. I have often wondered this myself but have not yet been curious enough to google the issue.
On thing you can try is use tracert (or similar utility) to trace the route to the destination IP address - this should tell you which IP address on your machine is the starting point. I don't know if you can tell tracert which IP address to start with. But it sounds like some fun experimenting to do on a cold rainy day (that is, if I already did not have a ton of work to do).
By the way, if you learn anything, please post it here.
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4210398#4210398
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4210398
17 years, 2 months
[Security & JAAS/JBoss] - Encrypt KeyStore-Password in a Tomcat-Connetctor for 4.2.3.G
by isc-hoa
Hi there
I'm having a question about setting up SSL for a JBoss-4.2.3GA:
I was able to configure the following connector-entry in the Tomcat server.xml:
<Connector protocol="org.apache.coyote.http11.Http11Protocol"
| port="8443" minSpareThreads="5" maxSpareThreads="75"
| enableLookups="true" disableUploadTimeout="true"
| acceptCount="100" maxThreads="200"
| scheme="https" secure="true" SSLEnabled="true"
| keystoreFile="${jboss.server.home.dir}/conf/server.keystore"
| keystorePass="12345678"
| truststoreFile="${jboss.server.home.dir}/conf/server.truststore"
| truststorePass="12345678"
| clientAuth="want" sslProtocol="TLS"/>
With this entry, SSL works fine. Unfortunately, I was not happy with the password in plain text. So I tried to setup a connector with encrypted password as described in
http://www.jboss.org/community/docs/DOC-9702
My Connector:
<Connector port="8443" address="${jboss.bind.address}"
| maxThreads="100" minSpareThreads="5" maxSpareThreads="15"
| scheme="https" secure="true" clientAuth="want"
| sslProtocol = "TLS"
| securityDomain="java:/jaas/encrypt-keystore-password"
| SSLImplementation="org.jboss.net.ssl.JBossImplementation" >
I also added the entries in security-service.xml and the jboss-web.deployer\META-INF\jboss-service.xml as described in the wiki.
I can start the JBoss without any exceptions or errors, http is working fine, but when I'm sending a https-request, I'm running into a time-out. There are still no warnings or excpetions. The JBoss or the Tomcat just does not response...
Hint: When I change the value SSLImplementation to "whatTheHell", I still got no exception! No "NoClassDefFoundError" or something like that... Is this attribute still valid in 4.2.3?
Is there something special to foresee with JBoss-4.2.3.GA?
Thanks for helping!
Cheers
Andre
View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4210396#4210396
Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=4210396
17 years, 2 months