This question already has answers here:
CORS with POSTMAN
(6 answers)
How to enable CORS in AngularJs
(10 answers)
Closed 4 years ago.
I am trying to make an Angular web app to call SAS STP service. I have tested the page to make a 'GET' request from 'http://date.jsontest.com' and it worked perfectly. However, when I switched the URL to SAS STP service (https://server:port/SASStoredProcess/do1?_program=/Shared+Data/stp_service) it kept giving me an error saying I am not allowed.
I have tested the SAS STP service with Postman and was able to get a return successfully. do I need to deploy the STP service as Web service?
The requirement i have is i do not want to send close frame to client if the websocket is already closed by client.
So i want to know if the websocket is still alive. How to? No API's on POCO using 1.6 version with C++
Closed. This question needs to be more focused. It is not currently accepting answers.
Want to improve this question? Update the question so it focuses on one problem only by editing this post.
Closed 8 years ago.
Improve this question
I want to establish the WSO2 Gadget Server in version wso2GadgetServer-1.4.2 (Carbon 3.2.x) in an environment secured by a Tivoli Access Manager (WebSEAL). All authenticated requests which reaches the gadget server have the parameter iv-user filled (with the username) in the HTTP header. The infrastructure environment has some restrictions: In opposition to the functionality of the WebSEAL authenticator plugin provided by WSO2 (as declared in the article “WebSEAL authentication for WSO2 Carbon based products”) there is no additional communication between TAM and the gadget server and no special TAM user account possible. The gadget server should evalute the header and automatically log in the user if necessary. Under normal circumstances the end-user should never see the login mask of the gadget server. It would be nice, if the necessary changes could be done without changing and compiling the gadget server. After studying the article “Carbon Authentication Framework”, I have tried to write an own authenticator plugin with BE and FE services to replace the default gadget server authentication.
My approach is, to lead through all HTTP requests to a filter where I can inspect the HTTP header and log in the user if necessary. In difference to the examples I’ve followed where only a single url is catched (article “How to create redirector in WSO2 Stratos” and the source code of the “SAML2 SSO Authenticator” provided by WSO2), I want to catch all requests. I have set the url-pattern in the servlet to "/*", with the result, that my filter logic will not be called. If I use an url-pattern for one single site (e.g. "/carbon/admin/docs/about.html"), then the filter logic will be reached.
Why does the url-pattern "/*" not work as I expect?
Working on a docuSign integration with Coldfusion and need assistance in making the SOAP request using WS security.
Your question is a little short on detail, but I presume you mean the Web Services SOAP security extension.
We had to do this a few years back when communicating with a .NET web service. The basic idea is that you provide a set of extra SOAP headers that contains security info such as:
Timestamp
Username
Password
Etc
To do this you need to create a new XML document as per the standard defined here. Next you will need to write code to create the SOAP headers. This means:
Create your remote web service object, e.g.
var objWebSvc = createObject("webservice", "http://remoteURL?WSDL");
Creating an XML document to represent the new headers
Populating it with the required info (such as username and timestamp etc.)
Adding the XML document to the web service object, using addSOAPRequestHeader()
Call your remote web service
Then of course if and when they call your web service you'll need to parse out those headers from their SOAP request and validate them. That can be done by grabbing the XML using getSOAPRequestHeader() and parsing out the info.
I found this to be an error prone task and (basically) a royal pain. The web service we integrated with eventually dropped the requirement, apparently becuase the any web services trying to connect that were not native .NET were having a hard time implementing the specification.
Good luck!
I blogged this a while back. See if this helps:
http://onlineanthony.blogspot.com/2010/05/using-ws-security-for-soap-in.html
This question already has answers here:
Difference between SOAP and HTTP protocol?
(3 answers)
Closed 4 years ago.
I have read that web services are transmitted through SOAP over HTTP. Then what is the difference between SOAP and HTTP, if they are both communication protocols?
Is there any difference or is HTTP simply a binding used by SOAP?
There are two main protocols related to web services.
1st, transport protocols - e.g.
HTTP(commonly used), TCP, UDP
2nd, messaging protocols - e.g. SOAP,
XML, JSON or binary encoded messages
Generally speaking,
Messaging protocols are responsible for exchanging the messages in a commonly agreed format.
Transport protocols are responsible for delivering the messages and how
it should communicate.
A real world example:
HTTP is like telephone communication, SOAP is like English.
You call the web service over HTTP in SOAP messages such as you call your friend by mobile phone and talking in English.
It's not web services are transmitted. Rather, messages are transmitted in SOAP format.
SOAP being a protocol specification for exchanging structured information can use pretty much any transport protocol (HTTP being the most widely used, RPC and SMTP can be used as well).
Long story short, you cannot compare HTTP and SOAP since these are two orthogonal things. See Wikipedia for introduction.
Web services do not need to be implemented using SOAP, and SOAP does not actually need to be transmitted over HTTP (although this is pretty rare). HTTP is the underlying protocol of the web, while SOAP is one way of using XML as an envelope for RPC calls.
Http or Https is the protocol over witch SOAP runs.
SOAP (Simple Object Access Protocol) is meant for data exchange between servers.
client systems of soap are just other servers that connect to get data from the master server.
the oter option of soap is RPC (remote procedure call)
http://en.wikipedia.org/wiki/SOAP