axis-c-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Stadelmann Josef" <josef.stadelm...@axa-winterthur.ch>
Subject AW: Connecting to a webservice with only username, password, and .cer file
Date Mon, 26 Mar 2012 07:52:19 GMT
Hi Dee,

If you connect to your Microsoft Web Service by C# then you are actually working in a homogenous
environment, that is to say, your client works as Microsoft Visual Studio .NET 3.5 or 4.0
WCF Client. And a Microsoft Client talks to a Microsoft Server. Then you have managed to make
this client server connection safe by a cert and a username and a password. OK.
  
BUT now comes the bigger challenge for you. How can you go heterogeneous? How can you make
an AXIS2/J or AXIS2/C Client talk to your Microsoft .NET WCF Service? Your client will be
written in C or C++ and what has been nicely generate by svcutil as a C# stub needs to be
generated now as a C stub to be linked with your client code. For that, it is of advantage,
if you first understand the interface, the contract, between your client and server/service.
This is expressed in WSDL and maybe closer specified by some XSD, a schema definition file.
Departing from this scenario, you need to lookout for a WSDL2C tool in the axis2 binary kit.
It's under %AXIS2C_HOME%\bin. For a description look at http://axis.apache.org/axis2/c/core/docs/axis2c_manual.html#wsdl2c

Take the browser and get and have a look at http://your.serverice.com:8080/xyz/services/service?wsdl

Hoppe this help to get started. What you should do first is to generate the stub talking to
a service which is not made secure and which does not need a certificate. If you master that
your AXIS2/C coded client can talk your Microsoft .NET C# coded service without the security
burden, if you understand that, then you are ready for the next step, securing the conversion.
Then you might have a look at AXIS2/C- RAMPART and go with this examples unless you understand
what goes on. TCP Monitor helps to see the protocol, and by protocol a client is separated
from its service. By protocol, the tow CL/SV become independent of implementation techniques
used, such as language and run time systems.

Josef






-----Ursprüngliche Nachricht-----
Von: S. Dee [mailto:sdee1973@live.com] 
Gesendet: Sonntag, 25. März 2012 17:38
An: c-user@axis.apache.org
Betreff: Connecting to a webservice with only username, password, and .cer file


First a little background:

I have already managed to successfully connect to a Microsoft web service using C#. To use
this web service, I have to supply a username and a password in the C# code. I also have to
install a certificate (in .cer format) into the "Root Certificate Authorities" section of
the system's certificates.

(By the way, the C# class I use to connect to the service was automatically generated for
me with the command line tool "svcutil.exe https://address.of.service")

Here is my question:

How can I connect to such a web service using Axis2/C? The example in the documentation is
of a completely different nature -- it asks for a certificate, key file, and a passphrase.
In my case, it is username, password, and a .cer file.

So I'm not sure where to even begin. I'm not sure where my .cer file should go, and where
my username and password should go. Any ideas?

Thanks,S. Dee 		 	   		  
---------------------------------------------------------------------
To unsubscribe, e-mail: c-user-unsubscribe@axis.apache.org
For additional commands, e-mail: c-user-help@axis.apache.org


---------------------------------------------------------------------
To unsubscribe, e-mail: c-user-unsubscribe@axis.apache.org
For additional commands, e-mail: c-user-help@axis.apache.org


Mime
View raw message