Add-SecureSetting
Stores secured user settings in the registry
Tweet
Getting Started
Pipeworks Quickstart
The Pipeworks Manifest
From Script To Software Service
What Pipeworks Does
Scripting Securely with SecureSettings
NOHtml Sites
Play with Pipeworks
PowerShell in ASP.NET
Mess With Markdown
Making Editing Easier With Markdown
Show Scripts as HTML
Making Tables with Out-HTML
Working with Write-Link
Connecting the Clouds
Get-Paid with Stripe
Getting GitIt
Get-Web Content From Anywhere
Pick up the Phone with Pipeworks
Implicit Texting with Twilio
The Wonders of Wolfram Alpha
Using Azure Table Storage in Pipeworks
Simplified SQL
Building with Blob Storage
Publishing Pipeworks to Azure
Looking Up Locations With Resolve-Location
Join Windows and Web
Why Windows
Scripting with Superglue
Integrated Intranet
Simpler SEO
Add-SecureSetting
(View Source)
Adds an encrypted setting to the registry
Stores secured user settings in the registry
Related Links
Get-SecureSetting
Parameters
Credential
A credential. The credential will stored in the registry as a pair of secured values.
Hashtable
A table of values. The table will be converted to a string, and this string will be stored in the registry.
Name
The name of the secure setting
SecureString
An existing secure string to the registry.
String
A string value to store. This will be converted into a secure string and stored in the registry.
Examples
Example 1
----------------------- EXAMPLE 1 -------------------------- PS C:\>Add-SecureSetting AStringSetting 'A String'
Example 2
----------------------- EXAMPLE 2 -------------------------- PS C:\>Add-SecureSetting AHashtableSetting @{a='b';c='d'}
Example 3
----------------------- EXAMPLE 3 -------------------------- PS C:\>Add-SecureSetting ACredentialSetting (Get-Credential)
Example 4
----------------------- EXAMPLE 4 -------------------------- PS C:\>Add-SecureSetting ASecureStringSetting (Read-Host "Is It Secret?" -AsSecureString)
