NetApp PowerShell Credential Bug (Fixed!)

Update: This has been resolved in the 1.3 release of the Toolkit.

I ran into a bug while trying to write a script that would cycle through all of my NetApp filers and change the root password. The issue was that I was unable to pass a PSCredential object to Connect-NaController because passing credentials meant that HTTPS/HTTP would be tried instead of the default and insecure RPC.

After working with Clinton Knight from the NetApp Communities, he determined that the toolkit was attempting to use Internet Explorer’s proxy settings. He was kind enough to provide a workaround, as follows:

[powershell]
[System.Net.WebRequest]::DefaultWebProxy = $null
[/powershell]

Until a permanent fix is introduced to the toolkit, put that snippet at the top of your NetApp PowerShell scripts, and you’ll be able to supply credentials (or -ForceSecure/-ForceUnsecure) to your Connect cmdlets.

• Bug report & fix on the NetApp PowerShell Toolkit Community