How to change WSDL "soap:address" location after importing a WSDL in WSO2 API Manager 4.5.0?

[omeruguz]

Description

I’m using WSO2 API Manager version 4.5.0. I created a SOAP API by importing a WSDL file. The API was successfully created and published to the Developer Portal.

However, when I access the API with the ?wsdl query like this:

https:///t//soapapi/1.0.0?wsdl

The returned WSDL still includes the original soap:address from the imported WSDL file. For example:

<soap:address location="https://original-service-url.com/service"/>

What I expect is for the soap:address location value to reflect the actual API Gateway endpoint, like:

<soap:address location="https:///t//soapapi/1.0.0"/>

Additionally, when I click the "Download WSDL" button on the Developer Portal, the downloaded WSDL file still contains the original endpoint, not the one served by WSO2.

I managed to change it manually, but for this I had to add a resource with HTTP method GET to the api and this is not a solution for me. This WSDL needs to be generated automatically.

Steps to Reproduce

I tried adding a custom policy to the GET source but it didn't work.

I downloaded the WSDL and changed it manually, then imported it again. However, when I call the wsd from test tools such as soap ui, the problem is the same.

Version

4.5.0

Environment Details (with versions)

No response

[mfevzikorkutata]

Hi Community,

I am also following this issue. I have checked the deployment.toml "API-M Config Catalog" and have been seen below properties which I thougt this could be the solution. But, after adding this properties still wsdl.location shows the backend URL.

Documentation: https://apim.docs.wso2.com/en/latest/reference/config-catalog/
listener.parameters.WSDLEPRPrefix

I had same problem in WSO2 Micro Integrator product and by adding below properties the issue was resovled and worked properly. But there is no equivalent for API Manager product. Or we are doing something wrong?

Docmentation: https://mi.docs.wso2.com/en/latest/reference/config-catalog-mi/

[transport.http]
listener.wsdl_epr_prefix="http://$IP:8290/"
listener.secured_wsdl_epr_prefix="https://$IP:8253/"

Is there anyone who understands "listener.parameters.WSDLEPRPrefix" properties and what's missing to replace WSDL location in WSO2 API Manager.?? Is this feature could be bug?

Kind Regards...

[NethmiRanasinghe]

Hi @omeruguz ,

I have looked in to the above issue and noted the following:

The ‘Download WSDL’ functionality in the Developer Portal works as expected and correctly rewrites the soap:address location. Below are the steps I followed:

1. Created a SOAP API with Implementation Type set to ‘Pass Through’,
   importing the WSDL from http://www.dneonline.com/calculator.asmx?wsdl
   with the endpoint set as: http://www.dneonline.com/calculator.asmx.
2. Deployed and published the API.
3. Accessed the API through the Developer Portal and clicked ‘Download WSDL’ from the Overview page.
The downloaded wsdl file contained the expected soap:address with the gateway URL.

<soap:address location="http://localhost:8280/cal/1.0"/>

I have verified this in both APIM 4.5.0 GA and the latest updated packs.

---

In case of accessing the WSDL via the ?wsdl query, we assume that you have added a GET resource (e.g., /*) to your SOAP API. Otherwise, API Manager should return a 405 - Resource Not Found response as wsdl generation using ?wsdl is not natively supported by API Manager.

What happens here is the following:

• When you access http://localhost:8280/cal/1.0?wsdl, APIM routes this GET request directly to the backend.
• Since the backend service (http://www.dneonline.com/calculator.asmx) natively supports WSDL generation using ?wsdl, the request is served directly by the backend.
• As a result, you receive the original WSDL from the backend, including the original soap:address pointing to http://www.dneonline.com/calculator.asmx.

Therefore this is not a bug. API Manager does not support WSDL generation via ?wsdl at the runtime gateway level.

Thank you,
Nethmi.

[NethmiRanasinghe]

Hi @mfevzikorkutata ,

WSO2 Micro Integrator creates proxy services that automatically generates a WSDL, which can be accessed by appending
?wsdl to the service URL.

The listener.wsdl_epr_prefix config prefixes the given url to all the services, server wide. Therefore when generating the wsdl automatically, this prefix is added to the soap:address.

But in API Manager, as we do not natively support WSDL generation via ?wsdl, adding this config will not solve the above issue.

Thank you,
Nethmi.

[mfevzikorkutata]

Hi @mfevzikorkutata ,

WSO2 Micro Integrator creates proxy services that automatically generates a WSDL, which can be accessed by appending ?wsdl to the service URL.

The listener.wsdl_epr_prefix config prefixes the given url to all the services, server wide. Therefore when generating the wsdl automatically, this prefix is added to the soap:address.

But in API Manager, as we do not natively support WSDL generation via ?wsdl, adding this config will not solve the above issue.

Thank you, Nethmi.

Hi @NethmiRanasinghe ,

Still there are lots of legacy systems available in the market. "Not natively supporting WSDL generation via ?wsdl" is a mission critical absence for WSO2 API Manager. I have used Micro Integrator and MI was able to do it easily. While WSO2 APIM is supporting proxy backend WSDL with SOA action, missing of WSDL address does not make sense. It is really quite ready infra for WSO2 API Manager. Because already supporting the SOAP actions. Thank you for the clarification.

Kind Regards...