I need to configure docusign connect to push notifications to my application server, however it is behind a firewall. I do have a proxy but I dont see any options for configuring a proxy in the connect settings. Any advice on how to proceed with this?
There is no option to configuring a proxy in the DocuSign connect settings.
Here are some of the requirements for DocuSign connect.
Your app must include a listener HTTPS URL that DocuSign can POST to.
This URL must be available on the public internet.
It can’t be blocked by a firewall.
Here is good DocuSign blog post which discusses options when your listener is behind a firewall. Here are some of the options posted in the blog post.
You can install your listener on a Heroku, Amazon, Azure or private server that is available on the internet.
you can use a service such as ngrok to tunnel the incoming requests to your machine which is behind your fire wall.
Your server can be located on your organization’s DMZ, providing access to the internet.
Your firewall can be opened (a “pinhole opening”) to enable the incoming notification requests from DocuSign to reach your listener.
You will need to work with your IT and InfoSec departments to determine the best answer for your configuration.
Related
I've been working on a project in Azure in which I'd like some help. I have two different VMs running the same project on containers. The first VM has the server of the application and it has a frontend. Also, this VM has a keycloak container. When the user enters the private IP of the server, it redirects to the keycloak login and afterwards it authenticates and redirects to the server frontend. The other VM is the client of the application, and goes through the same process of authenticating with the keycloak that's on the Server VM. I cannot find the proper configuration that allows this process to happen on a public IP, through an Application Gateway. The issue is that when I enter the public IP, the page does not redirect to the keycloak login. I've tried using multi-site configuration on the HTTP settings. I also searched online for answers but I only found situations where people use two VMs, not the same VM for both the frontend and keycloak. I've got two of each: backend pools, http settings, route rules and listeners. Also important, I cannot use a DNS for this matter.
The backend health returns a 200 status code
So, to sum it up: I need an user to access the public IP frontend of an application that goes through authentication via keycloak. Both are on the same VM, on different ports. This process should happen through an Application Gateway. I'm not a native English speaker, so I apologize if I wrote something wrong or difficult to understand. Any help on this matter would be really appreciated. Thank you all.
You should publish also keycloak on the gateway so your users can acces the login page.
More info here : https://www.keycloak.org/server/reverseproxy
I am newbie to Azure Logicapp. 2-3 months of experience.
In Azure Logic app ISE, I am trying to make http call to customer end via our proxy, but i don't see any option to specify proxy server and port in Http Connector. I read the documentation but could not find any where. Some of the option I tried is to adding below http headers:
URL-https://Customerurl.com
{
"X-Forwarded-Host": "172.16.161.70:5555", --> Proxy server:port
"X-Forwarded-Proto": "http"
}
But that's not working, don't see any request coming to proxy server, instead its calling directly to customer url.
Seek help here. Any help is appreciated. How to make that work?
While Logic Apps don't have a way to redirect traffic via a proxy, you could setup VNET Routes that forward traffic to your proxy.
This is useful in cases where you would like to ensure all requests come from a single IP Address when working with multiple ISEs and data sources that have IP Restrictions in place. This official doc covers the steps in details.
I have a self-hosted instance of Gitlab running in a local data center behind a firewall and we use Trello for all simple task/issue management. I'd like to connect Gitlab and Trello via Zapier for an automated Trello card creation process for each new issue and/or merge request. A recent attempt to connect the two did not work due to the firewall.
Are there any settings in Zapier I may be missing, potential work arounds, or another service beside Zapier that may solve the problem?
We are stuck with the instance of Gitlab.
Requests from Zapier come from AWS. If your firewall is blocking all connections from non-whitelisted IP addresses, you've got two options if you want to use Zapier with your Gitlab instance:
Whitelist all AWS IP addresses (probably not what you want to do)
Come up with a whitelisted server that will forward requests from Zapier to Gitlab. That way you only have to whitelist a server you own.
There's more info here: https://zapier.com/help/troubleshoot/behavior/cant-access-or-use-zapier-with-other-apps
Sorry I don't have better news here!
I have an Azure app service and in some cases I need to send a web request to a non-azure webserver. What do I need to do to make it possible.
Currently the web request fails with no clear error message.
In response to a HttpClient Put request I get a System.Net.WebException exception which says there were errors.
THe same request works from a desktop application.
If your webserver is reachable from the internet you should be able to access it through your App Service. Try to log a ping to your webserver and google (8.8.8.8).
If your App Service is in a VNET you should enable some outbound rules to your webservers IP adress.
The server I am connecting to is an other Azure service. After some more investigating, It appears that I can connect to it if I do not use SSL (i.e. http://) but the connection is immediately closed when using SSL (https://). I assume that the problem must be related to the use of SSL.
I want to connect docusign locally to my application. How it can be done? How can I setup the DocuSign Connect feature while I am developing locally on my laptop? Please guide me with detailed steps.
You're going to have to have your network forward an externally accessible url to your localbox.
Since Connect is a service hosted at DocuSign and requires a valid endpoint to send data to, and if RequireAcknowledgement is enabled, you'll have to send data back to the service as well.