You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* feat: add secured WSDL example with YAML config, update documentation and test alignment
- Introduced `apis.yaml` for secured WSDL configurations.
- Revised `ROADMAP.md` with a question about deprecating the old `rest2soap` interceptor.
- Updated `README.md` with instructions for secured WSDL usage.
- Adjusted test endpoint for SOAP proxy in `SecuredWsdlExampleTest`.
* refactor: minor
- The `soapProxy` acts as an entry point, listening on port `2010` and forwarding WSDL requests to the internal `wsdl-proxy`.
5
-
- The `wsdl-proxy` provides full authentication configuration.
6
-
- To secure a WSDL service, replace `<sampleSoapService/>` with a <target> definition specifying the actual WSDL endpoint. Authentication settings should be configured within the `wsdl-proxy` to ensure proper access control.
3
+
Usually WSDL documents are not secured and can be freely accessed by anyone. But sometimes WSDL documentation is considered sensitive and is protected by access control.
7
4
8
-
**Refer to [`proxies.xml`](./proxies.xml) for further details, settings, and modifications.**
5
+
To reference a secured WSDL in Membrane, configure an internal API to handle authentication and authorization with the server hosting the WSDL.
0 commit comments