Major Upcoming Changes CheckPoint.NET
I have been developing a standard .NET class library for communicating with the Check Point API. This change will be making it so psCheckPoint uses this class library instead of implementing it all itself.
v1.0.0+
Yes. Just install and import any release prior to 1.0.0. You can even have both versions installed and just import the version you want to use before running the commands.
Installing: Install-Module -Name psCheckPoint -MaximumVersion 0.9 [-scope CurrentUser]
Importing Module: Import-Module psCheckPoint -MaximumVersion 0.9
While I am trying not to change commands to much some changes have to be made. Below is the list of known differences.
The option -NoCertificateValidation has been removed and replaced with both -CertificateHash and -CertificateValidation. The equivalent of -NoCertificateValidation is -CertificateValidation None but I highly recommend not using this option in a production environment. Instead use -CertificateHash <HASH> to verify the server's certificate.
If you need to find out the hash of your management server or gateway you can use the command Get-CheckPointHash. If you have problems running this to get the hash run [System.Net.ServicePointManager]::ServerCertificateValidationCallback = { $true } first.
Previously the objects returned where basic objects with just the properties included. Now we will be returning the CheckPoint.NET objects. Most common properties have the same name in these new classes and as such shouldn't cause too many problems, details of these changes will be listed below. That said there is a lot more to these returned objects, which you can use if you want. Have a look at CheckPoint.NET documentation to see more.
Date and time fields like those found in the meta-info of objects is now returned as a DateTime class.
This command no longer contains a Session parameter. Objects will be reloaded from the same session that they were found/created from.
Export has been re-written including addressing a number of bugs in the original HTML output. It now outputs either raw JSON or HTML only and as such ConvertTo-CheckPointHTML has been removed. Valid input objects has changed to either a string (Where used will be done on each string), or any standard Check Point object. You can no longer pipe in output from Get-CheckPointWhereUsed, but as before Where Used is automatically done unless disabled.
Both of these options have been removed and replaced with -Ignore [No|Warnings|Errors]. No being the default.
Both New-CheckPointHostInterface and Remove-CheckPointHostInterface commands have not been migrated. You can however access and modify interfaces via the returned Host object.
If you were using these command and would like them back please log a Issue ticket and I will look at getting them added back in.
-Debug option on commands will no longer output the raw JSON data. New command Debug-CheckPointSession has been added for this reason. It can be used to write all raw JSON data to a text file for debugging purposes.
Debug-CheckPointSession -Path debug.txt
...
Debug-CheckPointSession -Disable