:8443"
On Mon, Dec 30, 2019 at 4:41 AM robertlazarski .
wrote:
>
> Somehow I missed before, that you are running the transport/https-sample .
>
> Configuring your server for https is a separate step, for recent
> Wildfly versions it uses a self signed cert you should be able to
Somehow I missed before, that you are running the transport/https-sample .
Configuring your server for https is a separate step, for recent
Wildfly versions it uses a self signed cert you should be able to do
this to confirm the port is open.
nmap -p 8443 localhost
Since you are getting a
I followed the README.txt.
The section "Running the Sample Service" used the port 8443 in the steps
2.) "-XX-XX XX:XX:XX. XXX:INFO::Started [email protected]:8443"
3.) https://localhost:8443/services/SimpleService?wsdl
On Mon, Dec 23, 2019 at 10:16 AM robertlazars
Port 8443 is HTTPS, you likely mean port 8080 as you would need a
cert, and in most cases load balancer of some sort, for SSL.
On Sat, Dec 21, 2019 at 2:50 AM albert kao wrote:
>
> Thank you for your suggestions :).
> I did:
> cd $AXIS2_HOME/samples/transport/https-sample/https
Thank you for your suggestions :).
I did:
cd $AXIS2_HOME/samples/transport/https-sample/httpsClient
mvn package exec:java
-Dexec.mainClass="org.apache.axis2.examples.httpsclient.SimpleServiceClient"
-Dexec.classpathScope=runtime -Dexec.cleanupDaemonThreads=false
Output is:
org.ap
Looks like a 15 second timeout , try passing this to maven:
-Dexec.cleanupDaemonThreads=false
On Fri, Dec 13, 2019 at 12:49 PM albert kao wrote:
>
> I am following samples/transport/https-sample/README.txt.
>
> Running the Sample Client get the expected result.
>
> Howev
I am following samples/transport/https-sample/README.txt.
Running the Sample Client get the expected result.
However, how to fix the following WARNING?
org.apache.axis2.deployment.AxisConfigBuilder processDeployers
WARNING: Unable to instantiate deployer
org.apache.axis2
SimpleHTTPServer doesn't support SSL. To get HTTPS support on the
server side, you need to deploy AxisServlet into a servlet container.
Andreas
On Mon, Jun 27, 2016 at 10:09 AM, Sterpu Victor wrote:
> Hello
>
> I'm trying to make a 2 way authentication https server with axis2
Hello
I'm trying to make a 2 way authentication https server with axis2 and I
don't know how to activate https from code.
Server starts from code on http and works fine.
This is my code:
public static void test() {
try {
ConfigurationContext con
Date: Sat, 14 Jun 2014 12:32:56 -0700
From: [email protected]
To: [email protected]
Subject: Re: [Axis2] Web Services Rest using https support
Axis2 support HTTPS, you need to expose
the service via https. For that you need to add the following to
See the last section of the following document:
http://axis.apache.org/axis2/java/core/docs/servlet-transport.html
Andreas
On Sat, Jun 14, 2014 at 8:17 PM, Marcos Morales
wrote:
> Hi! I was trying to develop a web service rest using https (the same web
> service works using http) b
Thanks for the reply! this includes rest web services?
De: Deepal jayasinghe
Enviado: 14/06/2014 16:33
Para: [email protected]
Asunto: Re: [Axis2] Web Services Rest using https support
Axis2 support HTTPS, you need to expose the service via https. For
Axis2 support HTTPS, you need to expose the service via https. For that
you need to add the following to services.xml (or axis2.xml).
https
This might help -
http://blogs.deepal.org/2007/07/all-about-axis2-servicesxml.html
Deepal
> Hi! I was trying to develop a web service rest using ht
Hi! I was trying to develop a web service rest using https (the same web
service works using http) but i'm having the following error:
GRAVE: El Servlet.service() para el servlet [AxisServlet] en el contexto con
ruta [/axis2] lanzó la excepción [https is forbidden] con
I have Java Client based on Axis2 (1.5) , trying to post message to WCF service
which is running in https mode.
I do not see any issue while message is send to same service running in http
mode but if WCF service is
started in https mode then start getting "Security verifying exception&q
Hello,
If I upgrade my axis2 libraries in my client from version 1.5.6 to 1.6.2, then
every call to an external 'https' web service results in the following error:
"org.apache.axis2.AxisFault: Transport error: 404 Error: Not Found."
This "issue" prevents me from si
ender">
> HTTP/1.1
> chunked
>
>
> class="org.apache.axis2.transport.http.CommonsHTTPTransportSender">
> HTTP/1.1
> chunked
>
>
> When I call an operation with https endpoint, I get this:
>
&g
I create the Stub with useSeparateListener = true
I have these in axis2.xml, which is loaded into ConfigurationContext when
creating the Stub.
HTTP/1.1
chunked
HTTP/1.1
chunked
When I call an operation with https endpoint, I get this
Thanks! That's where I am heading to. Will keep you posted.
Nandeesh
-Original Message-
From: George Stanchev [mailto:[email protected]]
Sent: Monday, May 07, 2012 5:04 PM
To: [email protected]
Subject: RE: Axis1.6 -- making Https calls
The server is using a certificate
@axis.apache.org
Subject: Axis1.6 -- making Https calls
Hi,
I am using Axis2 v 1.6 for invoking 3rd party WS calls. Things were fine but
the new requirement is, I need to be making secured calls (Https) and the
existing code throws the following exception. Can you please tell me how/what
changes should
Hi,
I am using Axis2 v 1.6 for invoking 3rd party WS calls. Things were fine but
the new requirement is, I need to be making secured calls (Https) and the
existing code throws the following exception. Can you please tell me
how/what changes should be made or point me to the right resource
Using AXIS2, I have a WSDL which specifies a service port address using
https.
Using wsdl2java.sh (linux), I have created both server and client code,
such that my service receives requests using this WSDL definition and
calls an identical service using the same WSDL but with a different
end
Hello,
I am trying to create a webservice which uses HTTPS for transport and
rampart for username and password authentication, but I have some
problems. I am working on Tomcat 7.0.22, axis2 1.6.0 and rampart 1.6.0.
However, I can't get HTTPS to work. I have followed tutorials for
se
: Tuesday, August 23, 2011 6:46 PM
To: [email protected]
Subject: Https forbidden, but it should be terminated by httpd
Hello all:
I am creating a web service using Axis2.
I have httpd in front with the JK connector to push web services to Tomcat. I
do not have SSL configured on Tomcat since
Hello all:
I am creating a web service using Axis2.
I have httpd in front with the JK connector to push
web services to Tomcat. I do not have SSL configured
on Tomcat since httpd handles that.
When I try to download a WSDL using this url:
https://myserver.com/myapp/services/MyService?WSDL
I
gt; About SSL test: when I open https://localhost:443 I get the apache
> startup page.
> However, when I try to open the webservice url
> https://localhost:443/axis2/services/MyService.MyServiceHttpEndpint/
>
> I get the following error page.
>
> ---
> HTTP Status 403 - Acc
Hi,
About SSL test: when I open https://localhost:443 I get the apache
startup page.
However, when I try to open the webservice url
https://localhost:443/axis2/services/MyService.MyServiceHttpEndpint/
I get the following error page.
---
HTTP Status 403 - Access to the requested resource has
Hi Denise,
Have you ascertained your ssl is installed properly, and you can pull up
an https page on your server via the web?
What about your error logs, what do they say?
JM
On 7/27/2011 8:32 AM, Denise Wu wrote:
Hi,
I've been strugling with the following error for days, can you
lient I am using the truststore as the keystore for testing
purpose.
When running the client I am getting the following error:
org.apache.axis2.transport.http.HTTPSender sendViaPost
INFO: Unable to sendViaPost to
url[https://localhost:443/axis2/services/MyService.MyServiceHttpEndpoint/]
org.apache.axis2.AxisFault:
Another option not related to java would be to install apache/nginx and
use it as reverse proxy from SSL port to axis listening on local interface.
On 14/06/11 10:14, Matta, Geethamadhurima wrote:
Hi,
Can anyone help on the below. I am using stand-alone Axis2 server.
Need it on https
The stand-alone Axis2 server doesn't support HTTPS. It is only
supported when using the servlet transport, i.e. inside an application
server.
Andreas
On Tue, Jun 14, 2011 at 00:14, Matta, Geethamadhurima
wrote:
> Hi,
>
> Can anyone help on the below. I am using stand-alone Axis2 s
OK,
8096
Here you declare that https as a transportReceiver name is used in
conjunction with a class understanding http but maybe not https. I think
all it does is listening now on port 8096 for a http protocol but gets a
https offered and does not understand it. Maybe you have a
Hi,
Can anyone help on the below. I am using stand-alone Axis2 server. Need it on
https.
From: Matta, Geethamadhurima [ICG-IT]
Sent: 09 June 2011 17:46
To: '[email protected]'
Subject: RE: Axis2 server on Https
I am running Axis2 standalone
2011 17:42
To: [email protected]
Subject: AW: Axis2 server on Https
Then you might be so kind and you say me how you run axis2/j stand alone
without any AS; do you?
While this is possible for axis2/C (the simple server) I have never used such a
thing as a simple server for axis2/J.
Please
next week.
Josef
Von: Matta, Geethamadhurima [mailto:[email protected]]
Gesendet: Donnerstag, 9. Juni 2011 16:23
An: '[email protected]'
Betreff: RE: Axis2 server on Https
Thanks Josef for your reply.
I am not using tomcat or any other servlet conta
@axis.apache.org
Subject: AW: Axis2 server on Https
Remember axis2 is a LARGE SERVLET
And SERVLETS run in a SERVLET CONTAINER established by APPLICATION SERVERS
Hence did you configure your APPLICATION SERVER to have an SSL port for https
request setup using i.e. Tomcats server.xml
Josef
Von: Matta
Remember axis2 is a LARGE SERVLET
And SERVLETS run in a SERVLET CONTAINER established by APPLICATION
SERVERS
Hence did you configure your APPLICATION SERVER to have an SSL port for
https request setup using i.e. Tomcats server.xml
Josef
Von: Matta, Geethamadhurima
Hi,
I am unable to start Axis2 server on https.
I changed the axis2.xml (transportReceiver) to https as below.
8096
This is the axis2server.sh containing:
java $* -Xms512m -Xmx512m -XX
ttpConnectionManager.closeIdleConnections(0);
}
}
}
if (e != null) {
throw buildException(e);
}
}
Do you guys see something wrong in there..?
Thank you,
Phil
On Tue, May 10, 2011 at 4:57 PM, Philippe Frangioni wrote:
> Hello all,
> we're using A
légalement obligatoire. Étant donné que les email peuvent facilement
être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité
pour le contenu fourni.
From: [email protected]
To: [email protected]
Subject: axis over https
Date: Wed, 11 May 2011 11:
Check this post http://blogs.oracle.com/andreas/entry/no_more_unable_to_find
HTH
On 11/05/11 21:26, Roberto Juárez Maldonado wrote:
Hi everybody,
I need to create a client of a web service which runs under a Tomcat
requiring https protocol; i.e. the url of the service is something
like
Hi everybody,
I need to create a client of a web service which runs under a Tomcat
requiring https protocol; i.e. the url of the service is something like
https://host:port/someService. The Tomcat uses self-signed certificates. I
have found examples on the Internet which say that with Axis 1
Hello all,
we're using Axis2 1.5.1. Our client makes web service calls every
second over https (we're doing 2-way SSL). We noticed the number of
CLOSE_WAIT connections client-side grows over time on our production
servers...
This bug looks related:
https://issues.apache.org/jira/browse/
Hi all,
I need to create a client of a web service which runs under Tomcat requiring
https protocol; i.e. the url of the service is something like
https://host:port/someService. The Tomcat uses self-signed certificates. I
have found examples on the Internet which say that with Axis 1 that was
Hi all,
I need to create a client of a web service which runs under Tomcat requiring
https protocol; i.e. the url of the service is something like
https://host:port/someService. The Tomcat uses self-signed certificates. I
have found examples on the Internet which say that with Axis 1 that was
on talks on Virtual IP
> and yet client authentication happens successfully.
>
>
> Note: This works well if it is HTTP and not HTTPS Axis2 WS client. How can
> we make this work with Axis2?
>
>
> Thanks!
>
> -Sethu
>
Hi,
Earlier we were calling a web service over HTTP and one of the element was
encrypted and was working fine.
Now we need to invoke the web service over HTTPS and all elements are
encrypted using the previous key only.
We have imported the certificate. But while calling the service we are
I tried a variant on Prabath idea and the following works:
String incomingTransport = messageContext.getIncomingTransportName();
if (incomingTransport.equals("https" )) {
}
Also I found that messageContext.getTo() returns the URL the client used:
something like https://host
@axis.apache.org
Cc:
[email protected]
Date:
09/07/2010 03:34 PM
Subject:
Re: If Tomcat is configured to accept both HTTP and HTTPS, how to know in
axis2 if the request came over HTTPS?
Thanks Prabath. I would test it out.
From:
Prabath Siriwardana
To:
[email protected]
Date:
09/07
Thanks Prabath. I would test it out.
From:
Prabath Siriwardana
To:
[email protected]
Date:
09/07/2010 03:29 PM
Subject:
Re: If Tomcat is configured to accept both HTTP and HTTPS, how to know in
axis2 if the request came over HTTPS?
String incomingTransport
(String)*messageContext*.getProperty(*"")*;
> }
>
> From: Deepal jayasinghe To:
> [email protected] Date: 09/07/2010 02:46 PM Subject: Re: If Tomcat
> is configured to accept both HTTP and HTTPS, how to know in axis2 if the
> request came over HTTPS?
>
url = (String)messageContext.getProperty("");
}
From:
Deepal jayasinghe
To:
[email protected]
Date:
09/07/2010 02:46 PM
Subject:
Re: If Tomcat is configured to accept both HTTP and HTTPS, how to know in
axis2 if the request came over HTTPS?
You can do that by
You can do that by looking at the request URL which you can access
using MessageContext.
Deepal
Folks
In my server code, I need to know if the call received came through
over HTTP or HTTPS. I would like to process the request a bit
differently if the request came through HTTPS.
How can
Folks
In my server code, I need to know if the call received came through over
HTTP or HTTPS. I would like to process the request a bit differently if
the request came through HTTPS.
How can I do this in axis2 1.2 (the version I am using)? If it is easier
to do in axis2 1.5.1, I could
Hi,
WSDL2Java doesn't seem to work for SSL enabled wsdl urls..
I tried a couple of things to fix this:
1)Tried creating a custom SSL factory with a dummy trust manager and setting
it as the default SSL factory..
2) Tried setting javax.net.ssl.trustStore property..
both of them didn't work.
could y
It seems a bit overkill to me to introduce yet another library just to
get HTTPS working since I don't use WS-Security.
On Fri, May 21, 2010 at 12:59 PM, Martin Gainty wrote:
> the easiest way to issue a SSL request is with a Security Provider *such as
> Rampart* configure
> Subject: transportsession + HTTPS = NullPointerException
>
> Hi,
>
> I'm currently having a hard time getting Axis2 1.4.1 running with HTTPS.
> In my setup Axis is part of a web app deploayed in Tomcat 6.0.20. My
> service scope is set to transportsession. This works fine
.1 running with HTTPS.
In my setup Axis is part of a web app deploayed in Tomcat 6.0.20. My
service scope is set to transportsession. This works fine as long as I
stick to HTTP. When I switch over to HTTPS I get the following error:
2010-05-17 16:47:16,388 ERROR AxisServlet:172 -
java.lang.NullPoin
Hi,
I'm currently having a hard time getting Axis2 1.4.1 running with HTTPS.
In my setup Axis is part of a web app deploayed in Tomcat 6.0.20. My
service scope is set to transportsession. This works fine as long as I
stick to HTTP. When I switch over to HTTPS I get the following error:
Reverse
> Proxy (HTTPS).
>
> The web service has to be accessible from the web.
>
> In my wsdl, i have set the address to https://myurl and it works fine, i
> can access my web service from the web.
>
>
> The problem comes when i send my Soap Request :
>
>
Hi,
I have to install an Axis2 web service in Tomcat (HTTP) behind a Reverse
Proxy (HTTPS).
The web service has to be accessible from the web.
In my wsdl, i have set the address to https://myurl and it works fine, i
can access my web service from the web.
The problem comes when i send my
wrote:
> Hi,
> I am using Axis 2.1.5.1 .
>
> In my Axis2.xml configuration, i removed the HTTP ( name="http") transport sender and am only having the "https" transport
> sender . I see that the request comes in fine into the service, however i
> get a NullPointer
ance(Constructor.java:494)
>
>
>
> Regards,
> Vish
>
> On Mon, Mar 1, 2010 at 5:06 AM, Martin Gainty wrote:
>>
>> can you confirm 8443 is the secure port for https only (and not tcp)
>> once you have decided to use HTTPS (port 8443) then i would suggest
>
java.lang.reflect.Constructor.newInstance(Constructor.java:494)
Regards,
Vish
On Mon, Mar 1, 2010 at 5:06 AM, Martin Gainty wrote:
> can you confirm 8443 is the secure port for https only (and not tcp)
> once you have decided to use HTTPS (port 8443) then i would suggest
> engaging rampart module..here i
Hi,
I am using Axis 2.1.5.1 .
In my Axis2.xml configuration, i removed the HTTP (
HTTP/1.1
chunked
Can someone please advice why is this an issue ?
Regards,
Vish
can you confirm 8443 is the secure port for https only (and not tcp)
once you have decided to use HTTPS (port 8443) then i would suggest engaging
rampart module..here is a quick tutorial
http://wso2.org/library/3190
as mentioned securing a TCP connection uses a different architecture than
e.axis2.rpc.receivers.RPCMessageReceiver"/>
>
>
>
> In my axis2.xml file I have the following:
>
>
> class="org.apache.axis2.transport.http.SimpleHTTPServer">
> 8443
> https://127.0.0.1:8443/axis2
>
>
>
> class="org.
owing:
8443
https://127.0.0.1:8443/axis2
HTTP/1.1
chunked
Which nearly gives me the desired result but the URL on my endpoint is
missing and AXIS throws errors:
WSDL:
AXIS Java errors:
When I start Tomcat (axis2):
[INFO] Deploying Web service: FirstServic
try adding transports entry to service as given below.
https
org.wso2.carbon.user.mgt.UserAdmin
thanks,
Amila.
On Fri, Feb 26, 2010 at 8:38 PM, chu_man_fu wrote:
>
> I need to create SOAP service which only allows HTTPS acces
Chris,
Releases up to Axis2 1.5.1 had indeed some problems with the
transportReceiver declarations in axis2.xml. This issue (AXIS2-4465)
should be fixed in the current trunk. [1] explains how HTTPS-only can
be configured properly with the current snapshots (and the upcoming
1.6 release). Thus
I need to create SOAP service which only allows HTTPS access.
I am half way to achieving this by adding the Rampart module to my
services.xml with a UsrnameTokenOverHTTPS policy. My problem now is that my
WSDL still shows the http binding:
http://127.0.0.1:8080/axis2/services
already configured and listening on an HTTPS
> port. Except then, Axis2 refuses to display endpoint information for
> services if the user is bringing back the wsdl over HTTPS.
>
> How can I solve this?
>
> Thanks,
> David
>
ers in the configuration file to
determine whether or not to display them in the WSDL.
My issue is, I do not want to define a transport receiver on its own port
because our Glassfish server is already configured and listening on an HTTPS
port. Except then, Axis2 refuses to display endpoint infor
73 matches
Mail list logo
