I am recieving a "org.apache.http.conn.HttpHostConnectException: Connection to https://demo.docusign.net refused" exception when trying to connect to start the embedded signing envelope request using serverside java HTTP call with a proxy server in between.
Is there a limitation of the number of requests per hour?
DocuSign imposes a limitation of 1,000 API calls per hour for an account. See the DocuSign API Best Practices Guide for information about this limitation: http://www.docusign.com/sites/default/files/SOAP_REST_API_Best_Practices_with_Connect_Guide.pdf.
I was using a HTTP proxy instead of a HTTPS proxy, the proxy in between me and docusign was causing the issue.
Related
I have an Azure API Management (APIM) (Basic) service set up to authenticate my JWT tokens over HTTP query connections via the validate-jwt plugin, and that works fine. I would like to do the same JWT token validation using a WebSocket connection over APIM.
The best I can get with websockets is the typical subscription-key querystring validation. After reading that WebSocket clients (like Apollo's WebSocketLink) only allow query string params as opposed to header modifications (potential due to Browser restrictions?), I tried passing an "authorization" query string pair in, but validate-jwt seems to misread that too (the websocket connection fails).
Microsoft does appear to advertise JWT validation on the docs website (https://learn.microsoft.com/en-us/azure/api-management/websocket-api)
but I can't find a clear example to show how that's expected to work.
Any suggestions (especially if you've gotten this to work)? Thanks!
You can use it as below in the handshake operation but once the handshake is done the http request is upgraded to WebSocket so the operation is no longer executed during the web socket connection.
https://learn.microsoft.com/en-us/azure/api-management/api-management-access-restriction-policies#ValidateJWT
As I see in this article:
https://www.docusign.com/blog/dsdev-adding-webhooks-application
that in Sandbox mode we can config webhook url with HTTP but when I go to my account Setting section it won't let me use HTTP
So my question is how can I use HTTP in sandbox mode for testing purpose.
Unfortunately you can't use HTTP with Connect
This guide explains it https://developers.docusign.com/esign-rest-api/guides/connect-https-only
Quote from Q&A
"DocuSign Connect is used to transmit sensitive data about your envelopes across the Internet. As part of DocuSign’s focus on security, we are upgrading all notifications to use HTTPS only."
Hope this answer your question
Hi I have a question about azure mobile apps.
Can I confirm HTTP request including header, body and url parameter in azure mobile apps when troubleshooting?
If yes, how can I confirm that?
For example, let me assume that client send a HTTP request to azure mobile apps, and a the response is bad request(status code 400).
Then I would like to figure out the cause.
First of all I set [Diagnostics log] - [Web server logging] as Storage in portal.azure.com,and confirmed the IIS log.
But there is no header, body info in the HTTP request.
So I did not find out the cause by that log.
Finally problem is solved by client logs by taking fiddler and cause is wrong info in body of the http request.
Above all, by taking fiddler log in client side, I was able to solve the problem but I would like to know if there is a way to confirm http request's header, body and url parameter in azure mobile apps side.
You can log the inbound query on the client or server side, or use something like Fiddler. For the server side, just use regular methods for Node.js or ASP.NET - nothing special is needed. For the client side, I documented the process for all platforms on my blog. Although the documentation is for adjusting the HTTP request, it's the same recipe for logging.
I do not know if I missed this information, but it seems to me that nowhere is written what the REST listener should return when it is called by the DocuSign connect.
Should it return a kind of formatted response?
Thank you,
Marco
DocuSign Connect will send an HTTP POST request to the endpoint that you specify for the Connect configuration settings. When your "listener" application that resides at that endpoint receives a message from Connect, it will automatically respond via normal HTTP request/response semantics -- you shouldn't have to do anything (from a coding perspective) to make this happen, since it's just normal request/response behavior for a web application.
We are having issues with Connect notifications from our DocuSign demo account.We are not able to receive any updates from our Connect configuration. Though, when I republished the XML from Connect logs, I did receive a Connect update to a specified URL.
When I created new envelopes using API as well as from DocuSign account itself, I never got any notifications to the same URL.I do not even see a Connect log.
We do not have any issues with Connect notifications for our DocuSign live account.
We have never experienced this issue before with Connect updates from our DocuSign demo account.
Please advise.
Just a hunch - do you use http or https? connect can only work over port 443 with a valid SSL certificate. If you're on localhost - you may need to get a temp certificate or something like that but also using azure websites is good way to avoid this issue since they're pretty much just as good as working on your localhost