Looking to whitelist the IP address for webhooks. I'm implementing some automations using the PHP SDK for a client, but their server isn't accessible via HTTP unless we whitelist the specific IP address of origin. Where do those posts originate from?
Thanks!
As Podio is built on a scaleable infrastructure we continuously add more capacity to our background worker cluster. This means that we cannot guarantee which IP addresses we will connect from when doing a webhook.
Related
I have A.Mysite.com and B.Mysite.com all calling my API.
Is there a way for my API to know where the request came from? (A.Mysite.com vs B.Mysite.com)
Thank you.
If you have control over the two sites calling the API, you can configure the two to send an additional parameter to identify themselves, and use this to track them. You would need to modify the API to accept this additional parameter. This is the ideal solution.
Additionally, there are numerous http parameters that may be used to track the origin of a http request. If the two callers use two different static ip addresses, this would probably be the most reliable method. For example, if the API is written in PHP you could access the remote IP address using $_SERVER['REMOTE_ADDR'].
The domain/subdomain of a website is only used during DNS resolution, when you try to send to the domain. Each domain will always send as it's ip address. If they both originate from the same ip address, they will be indistinguishable unless you add an identifying parameter.
I have Outbound IP range from partner system(server) whose HTTPS URL we are trying to connect to transfer files but since no APIs are involved , how to check if IP's are whitelisted or is it any way to Whitelist that IP range in anypoint Studio7 using Mule4
Not finding way to do it via Anypoint studio as my code is deployed locally and not on any CloudHub or on-premise as of now, as its just a POC
It is the other way around. The other side, which exposes the HTTPS service you are connecting to, restricts access to their service by whitelisting some IPs. If your IP, from where you connect to the service, is whitelisted, then you will be able to connect to it. If not, you might not even get an error response. It is up to the side whitelisting, which is usually the server.
I am creating my first chatbot with Facebook for developers and I don't know how to set a callback url. I already have my url (IP address of my EC2 instance). Do you know by any chance how could I obtain one? And do I have to set a domain name for my app? Thanks a lot in advance!
Yes, you need a domain name. The Platform won't accept an IP address for a webhook. All you need to do is expose an https endpoint on your EC2 instance that can accept POST requests, and provide that URL.
Are Shared hosting IP OK for Mandrill API Requests?
I'm trying figure out if a Nightmare is true or simply pure work overload. :)
Mandrill comes with a Shared and Dedicated IP Options for sending out emails. What I fully 100% agree with. But do I need a Dedicated IP for sending out API Requests to Mandrill? Or can Shared Hosting IP work as a starting point. (e.g Bluehost / Hostgator Shared Plans ).
Is there a possibility, that tow Account will use the same IP and lead to very Angry Mandrill? :{
I am planing to apply for a Dedicated IP. But would like to not rush with buy every feature to quickly.
The Mandrill dedicated IP option is an IP that is only used for sending your emails. You don't make API calls to that address. You would still make API calls to the same API endpoint described in the Mandrill API docs - with a dedicated IP, once we receive and process your mail, we would then route it over a dedicated IP address instead of the shared pool of sending IP addresses. All of the sending IPs are only used for sending emails. They aren't used for other portions of the application or API.
I have deployed my application on cloudbees, and was wondering how I can create a whitelist of allowed IPs which can access the application via browser requests or API requests.
Thanks
This is not possible on RUN#Cloud shared server pool.
Such IP restriction can be configured on "dedicated" servers as they provide more configuration option with isolated setup
You could write a filter (eg a servlet filter) which looks at the http://en.wikipedia.org/wiki/X-Forwarded-For header - this is the IP of the client - and filter it that way if you like.
(you have to use that header as the routing layer will provide it).