Bartholodeus wrote: > Hi, > > I am currently running an axis2 v1.3 webservice with https support. I made > the webservice with java2wsdl and wsdl2java with the eclipse codegen plugin. > In my scenario Axis and Tomcat are both deployed in JBoss. What I do not > fully understand is how they work together especially with https. As I > understand it Axis is deployed in Tomcat and Tomcat is deployed in JBoss so > the https request of the client reaches Tomcat first (maybe even something > before) and is forwarded to axis then. So far I have read about 2 > possibilities to configure the server to accept https with authentication in > 2 ways (client auth = true): > > 1.) Configure Tomcat (This is what I am using and which is working) > Uncommenting the SSL/TLS Connector in the server.xml in the tomcat home > directory and setting client auth = true and the server keystore and > truststore files. > The clients key- and truststore files are set over System properties. > > Yes you need to do this to make the Application server to be HTTPS aware. > 2.) Configure Axis > Adding the following to the service.xml > <transports> > <transport>https</transport> > </transports> You need this option if and only if you need to expose the service in https. Whether you specify this or not axis2 will expose the service in both http and https. As I mentioned earlier if you want your service to be expose only in https then you need to do that. > > > and uncomment the section in axis2.xml > <transportReceiver name="https" > class="org.apache.axis2.transport.nhttp.HttpCoreNIOSSLListener"> > and add the corresponding server key- and truststores (as above) > > You do not need to do this. This transport listener has nothing to do with tomcat https connection. > Also the client system properties have to been set as above. > > My questions are: > 1.) Did I understand the connection between jboss, tomcat and axis > correctly? > Well , Axis2 is just an application running behind an application server. Once the message receive to Axis2, it does not know how it came. > 2.) As I did not try the second possibility: Did I describe it correctly or > is there to be done something else? > 3.) Are these indeed the 2 possibilities to enable https support? Which of > the two do I have to configure? > 4.) How can I configure that this particular webservice can only be accessed > by https? Obviously the https-transport tag in the second possibility does > that (if I described it correctly) but how do I do it in the first > possibility? > Just adding the transport "https" in services.xml > 5.) The https connection is around 50 times slower then the http connection. > Is there a possibility to speed things up? There are several other post > about this issue in this forum and other forums but none of them got an > answer. > > Thank you very much for your help, > > Bartho > Thank you! Deepal
http://blogs.deepal.org --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
