You are viewing a plain text version of this content. The canonical link for it is here.
Posted to java-user@axis.apache.org by Moritz Mädler <ma...@moritz-maedler.de> on 2009/11/24 10:12:22 UTC
Configuring Axis2 using SSL
Hi,
we want to provide our service also via SSL.
Our Axis 1.5 runs as an application in Tomcat 6 which we already configured for listening for SSL-Connections.
When I call the WSDL using SSL Axis2 sets the wsdl-port-address as https://serviceurl:80/SERVICE. This is not
working as the Port 80 is added misleadingly.
I don't know how to fix that and especially keep both transports http and https as we want to use the old clients
were we could not change the address to the new https one.
I hope you can help!?
Thanks alot!
Moritz
AW: Configuring Axis2 using SSL
Posted by Moritz Maedler <ma...@moritz-maedler.de>.
Thanks alot! I will give that a try tomorrow.
-----Ursprüngliche Nachricht-----
Von: Andreas Veithen [mailto:andreas.veithen@gmail.com]
Gesendet: Dienstag, 24. November 2009 21:11
An: axis-user@ws.apache.org
Betreff: Re: Configuring Axis2 using SSL
Moritz,
What you can do is to include the WSDL in the AAR file (if that is the
deployment method you use) and set the useOriginalwsdl and
modifyUserWSDLPortAddress parameters so that Axis2 uses the WSDL
without modifications.
Andreas
On Tue, Nov 24, 2009 at 20:34, Moritz Maedler <ma...@moritz-maedler.de>
wrote:
> Is there a possibility to set the Endpoint-URL (the one that axis uses in
> the WSDL) for a service by hand?
> What I mean is to override the automatic detection and generation of the
> url, but set it manually through a
> config-parameter?
>
>
> -----Ursprüngliche Nachricht-----
> Von: Andreas Veithen [mailto:andreas.veithen@gmail.com]
> Gesendet: Dienstag, 24. November 2009 20:30
> An: axis-user@ws.apache.org
> Betreff: Re: Configuring Axis2 using SSL
>
> On Tue, Nov 24, 2009 at 13:56, Moritz Mädler <ma...@moritz-maedler.de>
wrote:
>> Hi Andreas!
>>
>> Thanks for your quick reply.
>>
>> Is it fixed in the 1.5.1 release, too?
>
> No, it is scheduled for 1.6.
>
>> If we discard the unsecured address and only provide the https-address is
> there a way to set it "by hand"?
>
> I'm not sure that I understand the idea. Can you explain a bit further?
>
>> Thanks alot!
>>
>>
>>
>>
>>> This is probably yet another instance of the issue described in
>>> AXIS2-4465 (which is fixed in trunk).
>>>
>>> Andreas
>>>
>>> On Tue, Nov 24, 2009 at 10:12, Moritz Mädler <ma...@moritz-maedler.de>
> wrote:
>>>> Hi,
>>>>
>>>> we want to provide our service also via SSL.
>>>> Our Axis 1.5 runs as an application in Tomcat 6 which we already
> configured for listening for SSL-Connections.
>>>> When I call the WSDL using SSL Axis2 sets the wsdl-port-address as
> https://serviceurl:80/SERVICE. This is not
>>>> working as the Port 80 is added misleadingly.
>>>> I don't know how to fix that and especially keep both transports http
> and https as we want to use the old clients
>>>> were we could not change the address to the new https one.
>>>>
>>>> I hope you can help!?
>>>>
>>>>
>>>> Thanks alot!
>>>>
>>>> Moritz
>>
>>
>
>
Re: Configuring Axis2 using SSL
Posted by Andreas Veithen <an...@gmail.com>.
Moritz,
What you can do is to include the WSDL in the AAR file (if that is the
deployment method you use) and set the useOriginalwsdl and
modifyUserWSDLPortAddress parameters so that Axis2 uses the WSDL
without modifications.
Andreas
On Tue, Nov 24, 2009 at 20:34, Moritz Maedler <ma...@moritz-maedler.de> wrote:
> Is there a possibility to set the Endpoint-URL (the one that axis uses in
> the WSDL) for a service by hand?
> What I mean is to override the automatic detection and generation of the
> url, but set it manually through a
> config-parameter?
>
>
> -----Ursprüngliche Nachricht-----
> Von: Andreas Veithen [mailto:andreas.veithen@gmail.com]
> Gesendet: Dienstag, 24. November 2009 20:30
> An: axis-user@ws.apache.org
> Betreff: Re: Configuring Axis2 using SSL
>
> On Tue, Nov 24, 2009 at 13:56, Moritz Mädler <ma...@moritz-maedler.de> wrote:
>> Hi Andreas!
>>
>> Thanks for your quick reply.
>>
>> Is it fixed in the 1.5.1 release, too?
>
> No, it is scheduled for 1.6.
>
>> If we discard the unsecured address and only provide the https-address is
> there a way to set it "by hand"?
>
> I'm not sure that I understand the idea. Can you explain a bit further?
>
>> Thanks alot!
>>
>>
>>
>>
>>> This is probably yet another instance of the issue described in
>>> AXIS2-4465 (which is fixed in trunk).
>>>
>>> Andreas
>>>
>>> On Tue, Nov 24, 2009 at 10:12, Moritz Mädler <ma...@moritz-maedler.de>
> wrote:
>>>> Hi,
>>>>
>>>> we want to provide our service also via SSL.
>>>> Our Axis 1.5 runs as an application in Tomcat 6 which we already
> configured for listening for SSL-Connections.
>>>> When I call the WSDL using SSL Axis2 sets the wsdl-port-address as
> https://serviceurl:80/SERVICE. This is not
>>>> working as the Port 80 is added misleadingly.
>>>> I don't know how to fix that and especially keep both transports http
> and https as we want to use the old clients
>>>> were we could not change the address to the new https one.
>>>>
>>>> I hope you can help!?
>>>>
>>>>
>>>> Thanks alot!
>>>>
>>>> Moritz
>>
>>
>
>
AW: Configuring Axis2 using SSL
Posted by Moritz Maedler <ma...@moritz-maedler.de>.
Is there a possibility to set the Endpoint-URL (the one that axis uses in
the WSDL) for a service by hand?
What I mean is to override the automatic detection and generation of the
url, but set it manually through a
config-parameter?
-----Ursprüngliche Nachricht-----
Von: Andreas Veithen [mailto:andreas.veithen@gmail.com]
Gesendet: Dienstag, 24. November 2009 20:30
An: axis-user@ws.apache.org
Betreff: Re: Configuring Axis2 using SSL
On Tue, Nov 24, 2009 at 13:56, Moritz Mädler <ma...@moritz-maedler.de> wrote:
> Hi Andreas!
>
> Thanks for your quick reply.
>
> Is it fixed in the 1.5.1 release, too?
No, it is scheduled for 1.6.
> If we discard the unsecured address and only provide the https-address is
there a way to set it "by hand"?
I'm not sure that I understand the idea. Can you explain a bit further?
> Thanks alot!
>
>
>
>
>> This is probably yet another instance of the issue described in
>> AXIS2-4465 (which is fixed in trunk).
>>
>> Andreas
>>
>> On Tue, Nov 24, 2009 at 10:12, Moritz Mädler <ma...@moritz-maedler.de>
wrote:
>>> Hi,
>>>
>>> we want to provide our service also via SSL.
>>> Our Axis 1.5 runs as an application in Tomcat 6 which we already
configured for listening for SSL-Connections.
>>> When I call the WSDL using SSL Axis2 sets the wsdl-port-address as
https://serviceurl:80/SERVICE. This is not
>>> working as the Port 80 is added misleadingly.
>>> I don't know how to fix that and especially keep both transports http
and https as we want to use the old clients
>>> were we could not change the address to the new https one.
>>>
>>> I hope you can help!?
>>>
>>>
>>> Thanks alot!
>>>
>>> Moritz
>
>
Re: Configuring Axis2 using SSL
Posted by Andreas Veithen <an...@gmail.com>.
On Tue, Nov 24, 2009 at 13:56, Moritz Mädler <ma...@moritz-maedler.de> wrote:
> Hi Andreas!
>
> Thanks for your quick reply.
>
> Is it fixed in the 1.5.1 release, too?
No, it is scheduled for 1.6.
> If we discard the unsecured address and only provide the https-address is there a way to set it "by hand"?
I'm not sure that I understand the idea. Can you explain a bit further?
> Thanks alot!
>
>
>
>
>> This is probably yet another instance of the issue described in
>> AXIS2-4465 (which is fixed in trunk).
>>
>> Andreas
>>
>> On Tue, Nov 24, 2009 at 10:12, Moritz Mädler <ma...@moritz-maedler.de> wrote:
>>> Hi,
>>>
>>> we want to provide our service also via SSL.
>>> Our Axis 1.5 runs as an application in Tomcat 6 which we already configured for listening for SSL-Connections.
>>> When I call the WSDL using SSL Axis2 sets the wsdl-port-address as https://serviceurl:80/SERVICE. This is not
>>> working as the Port 80 is added misleadingly.
>>> I don't know how to fix that and especially keep both transports http and https as we want to use the old clients
>>> were we could not change the address to the new https one.
>>>
>>> I hope you can help!?
>>>
>>>
>>> Thanks alot!
>>>
>>> Moritz
>
>
Re: Configuring Axis2 using SSL
Posted by Moritz Mädler <ma...@moritz-maedler.de>.
Hi Andreas!
Thanks for your quick reply.
Is it fixed in the 1.5.1 release, too?
If we discard the unsecured address and only provide the https-address is there a way to set it "by hand"?
Thanks alot!
> This is probably yet another instance of the issue described in
> AXIS2-4465 (which is fixed in trunk).
>
> Andreas
>
> On Tue, Nov 24, 2009 at 10:12, Moritz Mädler <ma...@moritz-maedler.de> wrote:
>> Hi,
>>
>> we want to provide our service also via SSL.
>> Our Axis 1.5 runs as an application in Tomcat 6 which we already configured for listening for SSL-Connections.
>> When I call the WSDL using SSL Axis2 sets the wsdl-port-address as https://serviceurl:80/SERVICE. This is not
>> working as the Port 80 is added misleadingly.
>> I don't know how to fix that and especially keep both transports http and https as we want to use the old clients
>> were we could not change the address to the new https one.
>>
>> I hope you can help!?
>>
>>
>> Thanks alot!
>>
>> Moritz
Re: Configuring Axis2 using SSL
Posted by Andreas Veithen <an...@gmail.com>.
This is probably yet another instance of the issue described in
AXIS2-4465 (which is fixed in trunk).
Andreas
On Tue, Nov 24, 2009 at 10:12, Moritz Mädler <ma...@moritz-maedler.de> wrote:
> Hi,
>
> we want to provide our service also via SSL.
> Our Axis 1.5 runs as an application in Tomcat 6 which we already configured for listening for SSL-Connections.
> When I call the WSDL using SSL Axis2 sets the wsdl-port-address as https://serviceurl:80/SERVICE. This is not
> working as the Port 80 is added misleadingly.
> I don't know how to fix that and especially keep both transports http and https as we want to use the old clients
> were we could not change the address to the new https one.
>
> I hope you can help!?
>
>
> Thanks alot!
>
> Moritz