How to send NTLM authentication in soap header? - soap

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?

Related

SOAP to Rest Conversion

I have a rest api which need to be hit through soap request.I have created wsdl and endpoint for soap web service but when i am hitting the rest web service using apache camel routing it giving error of Request is not authorized for given resource access
rest api is access token based so i am passing the access token in exchange headers while converting soap request to rest

how to update service provider in wso2 using soap request with inbound saml web sso configuration details: need soap request

currently working on wso2 identity servicer v5.7 . need a help to update service provider using soap request. i read the wso2 docs and saw the services provided by wso2 but did not find the right soap request. I want to update service provider all the details in one request: saml sso configuration as well.
You can use the updateApplication method of IdentityApplicationManagementService to update a Service Provider. To obtain the WSDL, use the following URL.
https://{IShost}:{port}/services/IdentityApplicationManagementService?wsdl

SOAP and REST on the same endpoint URI

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

How to configure Keycloak with SAML ECP profile

I'm implementing an SSO authentication flow using SAML for a web server running tomcat. Everything is working ok when using POST or Redirect bindings, but from what I've read to support the SAML authentication in front of a REST API I need to also configure and use an ECP profile.
First correct me if I'm wrong but the ECP flow should be like this:
Client accesses the SP REST API
Client knows he needs to authenticate so he sets up the required ECP headers (Accept: application/vnd.paos+xml and PAOS: urn:liberty:paos:2003-08;urn:oasis:names:tc:SAML:2.0:profiles:SSO:ecp)
SP sees client is not authenticated and returns a SOAP Envelop containing PAOS Request.
The client is responsible to send this to the appropriate IdP on its ECP consumer service.
The IdP challenges the client for authentication
The IdP returns a response in the form of another SOAP Envelop, containing the saml Response in its body
The client must send this response to SP's ECP/SOAP assertion consumer service
The problem is all of this works until step 6. On this step I have the problem, that the Body of the response envelop contains a Destination attribute, which points to the POST assertion consumer service of the SP. This destination attribute is set by keycloak and mismatches the actual ECP service that I want to send the response to. The SAML library we are using is opensaml and it checks the request URI against this Destination attribute and if they do not match it throws an exception org.opensaml.xml.security.SecurityException: SAML message intended destination endpoint did not match recipient endpoint.
I understand why this exception is thrown, but cannot understand how I can configure Keycloak with the ECP/SOAP service of the SP. In Keycloak's admin console I can only configure the URLs for SSO POST/Redirect and SLO POST/Redirect, but nothing about ECP.
I'm currently in the process of configuring another IdP, but I would really like to make sure that Keycloak can also be a supported server for our solution.
Can't you just read the paos:Request responseConsumerURL and post the idp response to that url?
At least, that's how I managed to do it.

How to modify the SOAP header information for client IP address, while calling SOAP service

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