I have a SOAP server and multiple REST client application.
REST client application, internally Call the SOAP service using WSDL.
when we call the SOAP server it identifies the client on the basis of IP address in the SOAP Header.
I want to implement a mechanism, so that the SOAP sever cannot identify the client IP address and it appears that all the requests are coming from that same IP.
Can we modify this header at client end ? if yes please provide me some solution.....
thanks in advance
Related
I'm running Keycloak and it works great. The only thing I'd like to change is when the execute-actions-email API is called it sends the email but the link uses HTTP. I'd like it to be HTTPS. How does KC determine it should use HTTP? Is it because I made the API call over HTTP to trigger the request? Doe it get it from the client config?
It uses whatever protocol was used to make the RESTfull call; just connect to KC on port 8443 (default SSL port) and it'll send the email with a link that uses HTTPS.
I could invoke service in soap ui with my credentials or calling same service with node soap package , but I need to invoke It by sending request with soap header, but I couldn't find any examples about that, so is It even possible?
We have a requirement to expose SOAP service along with GET and POST Calls to the REST service on the same endpoint URI. Any inputs will be appreciated.
This needs to be achieved with oracle SOA
What's the appropriate way to extend a Balana-OpenAZ based PEP to send XACML3 decision requests to a remote WSO2 Identity Server PDP?
You want to send XACML decision request from PEP to Identity Server PDP. Still Identity Server only supports SOAP based web service API, Thrift based API and WS-XACML. Therefore i guess, best way to start is using SOAP based web service API. You can find sample java based client from here to write a extension for Balana-OpenAZ PEP.
We have an RPC-soap service. If we add new optional fields to the response data from the service, this can potentially break client applications, depending on the SOAP toolkit the client uses, if the client proxy is not updated to sync with the latest service API.
Could the same situation occur between client applications and a REST service, where the client applications use a REST client proxy generator on the WADL or WSDL2.0? Or do these REST clients gracefully handle data in the response that is unexpected, by ignoring those fields? Does it depend on the REST client toolkit?