Import wsdl with basic auth

[Steve James]

Hi, I am trying to import a wsdl with basic auth and keep getting connection refused. There are also dozens of imported xsd so it's not feasible to build a local wsdl.

I've managed to manually create a single operation and this runs fine but it is time consuming and there are dozens of potential operations.

I've tried setting the auth before importing the wsdl without success and tried including the credentials with in the url which worked in SOAP-UI eg

http://theID:password@www.supplier.co.u ... rvice?wsdl

I've tried this in both 4.5 and 5.0.1.

Any ideas about how I can get the wsdl to import?

Thanks

[Steve]

Hi Steve,

Unfortunately we do not set any authentication on the WSDL reader. Ebase uses WSDL4J to read the WSDL before processing it and it just passes in the URL. I am not sure there are any authentication options with this.

Currently, the only way you can do this is to create them manually or download the WSDL with all the XSD's.

Steve

[Steve James]

Ouch but thanks anyway.

I may be able to get Soap-UI to create the files locally as there are 100+ included xsds.

[Steve]

Hi Steve,

We support loading WSDL from your local file system.

Is there any way the Web Service provider can send you a copy of the WSDL and the XSD's so that you can load the WSDL from your local file system?

Steve

[Steve James]

Possibly yes but of course these things change so it's always best to remove links in the chain and be self sufficient.

At the moment we only need to use 2 operations but this is likely to grow quickly so we'll manage for the moment by manually creating the operation in Ebase.

It would be good to have an import mechanism where the wsdl has basic auth.

Thanks

[Steve James]

Using Soap-UI it was easy enough to get a full list of the 148 included xsds.

A quick Powershell script to download them all.

Ebase isn't happy importing the full wsdl but I can tweak it easily enough to allow me to import the necessary operations.

Thanks.