This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

RESTful API and PowerShell Scripting

Anybody have some experiences with that?

I'd like to have a Powershell-Script that enables/disables Firewall or NAT Rules -> that means for example do this curl:

curl -X PATCH --header 'Content-Type: application/json' --header 'Accept: application/json' --header 'Authorization: Basic dG9rZW46WmZqblZtZkd0bVppZ3lYRURLZkJRZWl1dnpqRUlTTFM=' -d '{"auto_pf_in":"","auto_pfrule":false,"comment":"","destination":"","destination_nat_address":"","destination_nat_service":"","group":"","ipsec":false,"log":false,"mode":"none","name":"","service":"","source":"","source_nat_address":"","source_nat_service":"","status":true}' 'https://utm.local:4444/api/objects/packetfilter/nat/REF_PacNatHttpsFromAny'


I did already search a little bit and I found out that I have to use the Invoke-RestMethod with Powershell. I'm able to do GET things with powershell now but I don't know how to do PATCH or POST Things with Powershell...

Anybody can help?


regards

This thread was automatically locked due to age.

Parents

0 TimBoggs over 6 years ago

You might find this post helpful: https://community.sophos.com/products/unified-threat-management/f/management-networking-logging-and-reporting/98167/how-can-i-make-network-definition-a-member-of-network-group-using-restful-api

I just started down this path myself and I am still having issues, but I have basic connectivity working:

#The base API URL and then the plan was to add variable for more nodes.
$apiURL = 'https://sophos:4444/api'
$networkURI = $apiURL + '/objects/network/network/'

#Recommended you setup a token for scripting instead of using username/password. Either way it has to be converted to Base64
$token = 'tokenFromAPIScreen'
$tokenBase64 = [Convert]::ToBase64String([System.Text.Encoding]::Default.GetBytes("token:" + $token))

#One recommended method for building headers, you can just create an array with all the values
$headers = @{}
$headers.add("Authorization",'Basic ' + $tokenBase64)

#This sets the TLS levels. By default I think it tries ssl which is disabled on our UTM
$AllProtocols = [System.Net.SecurityProtocolType]'Tls,Tls11,Tls12'
[System.Net.ServicePointManager]::SecurityProtocol = $AllProtocols

#This should return a list of network objects, with their Name / IP Address / Network Mask
Invoke-RestMethod -Uri $networkURI -Method Get -Headers $headers | ft name,address,netmask
Cancel
Vote Up 0 Vote Down

Cancel
0 SWeissflog over 6 years ago in reply to TimBoggs

It's no problem using powershell and RESTful API for GET commands but do you have any luck with patch, put or post?

Maybe anybody have a sample for that (e.g. activating Firewall Rule or WLAN Network)

regards
Cancel
Vote Up 0 Vote Down

Cancel
0 TimBoggs over 6 years ago in reply to SWeissflog

Here is a script I wrote to modify network definitions,

It covers creating new objects and modifying existing objects.
Cancel
Vote Up 0 Vote Down

Cancel
0 SWeissflog over 6 years ago in reply to TimBoggs

Thanks, we found out that it simple was a syntax mistake (missing $) with powershell...

We're able to switch NAT-/Firewallrules, WLAN-Networks... on/off now with one Powershell Script (-> check and change the current status on<->off) :-)

If anybody is interested ->pm or answer here

regards
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 SWeissflog over 6 years ago in reply to TimBoggs

Thanks, we found out that it simple was a syntax mistake (missing $) with powershell...

We're able to switch NAT-/Firewallrules, WLAN-Networks... on/off now with one Powershell Script (-> check and change the current status on<->off) :-)

If anybody is interested ->pm or answer here

regards
Cancel
Vote Up 0 Vote Down

Cancel

Children

No Data