I do not know How to cancel VLAN FireWall by rest api.
There was nothing like deleteObject method of SoftLayer_Network_Vlan or SoftLayer_Network_Vlan_Firewall service.
So, Please tell me how to cancel VLAN FireWall by rest api.
Thanks.
I recomed you to read this article:
https://sldn.softlayer.com/node/274103 (Getting started with REST and the SoftLayer Billing API)
Basically you need to camcel the associated billingItem of your VLAN for that you can use the https://sldn.softlayer.com/reference/services/SoftLayer_Billing_Item/cancelService or the https://sldn.softlayer.com/reference/services/SoftLayer_Billing_Item/cancelItem methods
Related
I want to use Dialogflow for my enterprise usage. So want to know whether Dialog flow will be able to hit Non public URLs?
Since Dialogflow is a service hosted by Google, fulfillment requests specified by Webhook URLs must be able to be reached by Dialogflow for them to be invoked. In addition, the webhook endpoints must expose themselves using SSL/TLS and must be associated with a non-self-signed certificate. When a request is made from Dialogflow, dialogflow can provide authentication credentials to ensure that it is indeed Dialogflow that is making the request.
One pattern for your usage is to expose the Webhooks to the Internet and only allow connections from the Google IP address range and also require authentication (known only to Dialogflow). This would go a long way in preventing malicious access to your Webhook.
An alternative would be to define your Webhook as a GCP hosted endpoint and then you would own the routing back to your internal system from there. That could use a variety of technologies beyond HTTP including Pub/Sub. For example, when Dialogflow invokes the Webhook, a GCP application could be called that posts a message to PubSub. Your Enterprise application could be a subscriber and be notified that it has work to do. It does work and responds with a new message which is received by your GCP hosted Webhook that then returns the response to Dialogflow. As such, there is no surface area for an attacker to try and penetrate.
I have two microservices registrations, which is responsible for registering new users, and users, which hold information about users. Each of them has it's own database.
When a user tries to register, a call to users is made via the API, e.g.
GET users/verify?email=foo%40bar.com
to chech if the email has been already assigned to a profile. Although I could hide the access point users/verify in the public docs, it can still be accessible.
What is the best way to allow only private IPs make requests to the API?
You may use a Gateway, some alternatives are
Tyk
Kong
Netflix/Zuul
There is a nice article at https://thenewstack.io/api-gateways-age-microservices/
Keep it simple. Do it at the firewall level
Whitelist the IP(s) that you want to be able to make requests, reject the rest
I have a service connecting to an enterprise service which I have no control over. The service requires I make a call to it to initiate a ping to a device and then make subsequent calls to it to get the status. After 20 or so seconds I will get the status back.
I have been thinking of a rest pattern and just getting stuck on the fact that it is not truly restful Id like to reach out for feedback and get some opinions. I could just do a normal get /device/status and hit it over and over again? Or i could break up the call into /device/ping and /device/status or something like that. Any ideas are appreciated!
Thanks
For status, REST standards would suggest a format of '/device/{deviceId}/status'. But if the enterprise service you are connecting to does not support multiple devices; you could go for '/device/status' with 'GET' http verb.
You could use '/device/status' with 'HEAD' http verb as an exposure for the ping call
I will suggest to return the a JMS queue URL in location header in API response. Usually, in device management applications, separate JMS server is deployed. Make use of it - if it's there.
Take a hint from here.
.
When an employee leaves the company, we want to have all email forwarded to a colleague to avoid communication lapses, especially with clients. We would like to place the forwarding rule on the account through a SharePoint workflow with a call to the EWS REST API.
I tried a few Google searches and ended up finding some related methods in the API docs, but the closest thing I could find was a command to forward a message directly.
Is there a sane way to do what I'm trying to do, specifically with a REST call? I know this could be set up by Net Ops at the admin level, but we have a specific requirement to do this with a SP workflow. I'm fairly new to SharePoint and web APIs, so any help would be greatly appreciated.
FWIW, we are on SharePoint 2013 and Office 365 Exchange.
If your using OnPrem Exchange there is no EWS Rest interface yet (its coming in Exchange 2016). The Office365 REST api's currently don't support creating rules either.
A few other ways of doing this is use Remote Powershell https://msdn.microsoft.com/en-us/library/office/ff326159(v=exchg.150).aspx and Set-Mailbox https://technet.microsoft.com/en-us/library/bb123981(v=exchg.150).aspx (see example 1)to set a forward on the Mailbox.
You can use EWS (SOAP) to create an Inbox rule https://msdn.microsoft.com/en-us/library/office/ff597938(v=exchg.80).aspx . (If you really want you can build a WebService to fount end that and provide it as a REST service).
Cheers
Glen
Looking through the XirSys API, I don't see a way to simply get my IP address as it visible from XirSys.
Is that possible to get via the exposed API?
The XirSys STUN servers do exactly that, but it's not something you can request from an HTTP request. If you're using a middleware server (for security), however, then you can do this in pretty much any language. See for example: How to get the client IP address in PHP?