#Get plain text from securestring powershell password

Notice that the username (userhere) is not encrypted but the password is. That's it! I'll now look at the XML file generated. Here's how you'd save a PSCredential object to a file: Get-Credential | Export-CliXml -Path Mењњredential.xml The encryption is done automatically when Export-CliXml is invoked. To save a PSCredential object to the file system, we'll use Get-Credential to provide an interactive input to supply the username and password and then we'll use Export-CliXml to export that credential object to the file system encrypted. I want this process automated so I can't prompt for the password when needed and I definitely don't want to get lazy and store it in plain text! I need to save it somewhere before the process runs so I can securely retrieve it when I need to. Let's say I have a script that requires an alternate username and password to run some process. Luckily, PowerShell gives us a built-in way to both store and retrieve username and passwords securely using the commands Get-Credential, Export-CliXml and Import-CliXml. Saving and retrieving credentials are the most common reason to encrypt sensitive information. We simply need a certificate installed which can be self-signed.

#Get plain text from securestring powershell windows

DPAPI is a built-in way Windows users can use certificates to encrypt and decrypt information on the fly which is perfect for PowerShell scripting.

#Get plain text from securestring powershell how to

How to Read Credentials from a FileДЄfter working with DSC for a few hours you will be getting tired of entering your credentials over and over again.PowerShell has native support for something called the data protection API (DPAPI). Note that generating the MOF file will fail if you do not set PSDscAllowPlainTextPassword to $True because DSC will attempt to secure the credentials. $ConfigData = AllNodes = NodeName = '*' PSDscAllowPlainTextPassword = $True } NodeName = 'dsc-01' DomainName = '' } ) } Configuration SimpleExampleWithCredentials SimpleExampleWithCredentials -ConfigurationData $ConfigData -DomainCredential ( Get-Credential ) The LCM uses the credentials to execute the appropriate tasks from the configuration. You can supply credentials by adding a parameter to your configuration and using the parameter in a DSC resource. But not all resources will work with those credentials because the LCM will not be able to access remote systems. The Local Configuration Manager executes DSC configurations using the system account. In this post, I will explain how to use credentials in the configuration. This is a crucial requirements when the configuration is applied on a workgroup host and the source location is inaccessible by the system account. For example, if you are copying files or directories using the file resource, the Local Configuration Manager needs appropriate credentials to access the source location. Many resources for Desired State Configuration require credentials to successfully execute the specified task. Tags #Credentials #Desired State Configuration #DSC #PowerShell #PSDSC Handling Plain Text Credentials in PowerShell DSC