Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
Add support for securely storing credentials via 'ProtectedData' Module #378
changed the title from
Add support for securely storing credentials via 'ProtectedDdata' Module
Add support for securely storing credentials via 'ProtectedData' Module
Apr 29, 2015
That is also an option. Does it support persistence across user logins on the same system?
I was thinking more along the lines of supporting an encrypted, hard coded password, that would require a separate key/cert to decrypt it, upon execution, which avoids using the .NET Data Protection API, which isn't versatile if you have the report running on several servers in a large and/or geographically disbursed environment.
PowerShell v5 natively supports almost all of the features of the ProtectedData module.
Either way, I was mainly thinking of a more efficient and secure way to maintain credentials; it very well may be the case that
We use the credentials feature of Task Scheduler that's been part of Task
On Wed, Apr 29, 2015 at 11:09 PM, Kevin Kirkpatrick <
This would not change the existing functionality, but extend it to give more flexibility.
I guess the simplest use case to highlight the need for this would be if you had an account that only had read-only rights to vCenter (e.g. your "every day" account that you use on your workstation), and wanted to use a privileged account to read event logs from vCenter.
I submitted #485 as a method to do this. I wasn't aware of