2015-05-20 07:28 PM - edited 2015-05-21 03:05 AM
I've configured my Cluster Vserver to be able to authenticate via a self signed certificate. I'm able to use Perl NMSDK to connect and it works good. I want to use Powershell cmdlets for this. How can I do this? I've tried Connect-NcCluster but I don't see any option to specify a certificate there.
I'm also open to use NMSDK for Posh if someone can guide how to use it. I've tried that too but I can't get it working.
Can anyone help?
2015-07-15 06:17 AM
I don't believe that a certificate can be used to authenticate using Connect-NcController. You might try using the Add-NcCredential cmdlet to securely save credentials.
Using the Invoke-NcSsh cmdlet you can use certificate based authentication, however that does not enable you to use the other PowerShell Toolkit commands.
Hope that helps!
2015-07-15 07:57 AM
Hi Sinhaa -
You've discovered the key difference between the Perl API bindings in the NMSDK and the PowerShell toolkit. The NMSDK, and with the Perl bindings in particular, easily exposes the entire SDK from basic connection methods, the lowlevel XML building mechanisms, and a single function wrapper around each individual ZAPI function call that handles both the XML building from and recoveyr into convenient Perl data structures. The entire API is accessible including higher privilege level options and commands.
The PowerShell toolkit is much more a convenience wrapper around common functions for those in a Windows environment. It doesn't expose the entire API, it doesn't expose all the parameters of the APIs that it does wrap (for instance, you can't access or use options only available in Advanced or Diagnostic mode), and security is somewhat Windows centric in that it uses a saved credential model similar to other Windows systems.
As my company tends to be more Windows centric the PowerShell toolkit tends to be the default utility used for most automation, but I drop to the Perl NMSDK bindings for almost everything I do of substance because I need the abilities it provides. I've asked through many channels for the PowerShell toolkit to at least add Advanced mode privilige options for a number of the cmdlets it provides. Haven't yet seen any indication that those will be forthcoming.