🔐 A simple credential manager to store and reuse multiple PSCredential objects.
Go to file
2018-03-08 12:27:26 +01:00
.vscode Publish Pre-release (#1) 2017-09-21 13:32:15 +02:00
bin Publish Pre-release (#1) 2017-09-21 13:32:15 +02:00
docs Update docs (platyPS) 2018-03-08 10:19:25 +01:00
resources add tests resources 2018-03-08 10:57:37 +01:00
src add pester tests for Resolve-Dependency 2018-03-08 10:57:51 +01:00
tests fix #17 2018-03-08 12:27:26 +01:00
tools fix #17 2018-03-08 12:27:26 +01:00
.gitignore Publish Pre-release (#1) 2017-09-21 13:32:15 +02:00
appveyor.yml bump version 2018-03-06 14:42:01 +01:00
LICENSE Initial commit 2017-07-27 13:40:00 +02:00
README.md update badges (#11) 2017-11-15 10:17:23 +01:00

AppVeyor branch AppVeyor tests branch Coveralls github PowerShell Gallery PowerShell Gallery

forthebadge forthebadge

General

The PSCredentialStore is a simple credential manager for PSCredentials. It stores PSCredentials in a simple json file. You can choose between a private and shared credential store. The private one exists in your profile and can ony accessed by your account on the same machine. The shared store enables you to use different credentials for your scripts without exposing them as plain text.

The shared store isn't 100% secure and I don't recommend using it in production!

PSCredentialStore was developed to simplify the delegation of complex powershell scripts. In this case you often need to store credentials for non interactive usage like in scheduled tasks.

For more details read the about_PSCredentialStore page.

Installation

  • Make sure you use PowerShell 4.0 or higher with $PSVersionTable.
  • Use the builtin PackageManagement and install with: Install-Module PSCredentialStore
  • Done. Start exploring the Module with Import-Module PSCredentialStore ; Get-Command -Module PSCredentialStore

Manual Way

  • Take a look at the Latest Release page.
  • Download the PSCredentialStore.zip.
  • Unpack the zip file and put it in your Powershell module path.
    • Don't forget to change the NTFS permission flag in the context menu.
  • Start with Import-Module PSCredentialStore

Quick Start

1. First we need a blank credential store. You can decide between a private or shared store. The private Credential Store can only be accessed with your profile on the machine you created it.

# Private credential store
New-CredentialStore

# Shared credential rtore
New-CredentialStore -Shared

#Shared credential store in custom Location
New-CredentialStore -Shared -Path 'C:\CredentialStore.json'

2. Now you can manage your credential store items:

# This will prompt for credentials and stores it in a private store
New-CredentialStoreItem -RemoteHost 'dc01.myside.local' -Identifier 'AD'

# You can now use it in other scripts like this:
$DCCreds = Get-CredentialStoreItem -RemoteHost 'dc01.myside.local' -Identifier 'AD'
Invoke-Command -ComputerName 'dc01.myside.local' -Credential $DCCreds -ScripBlock {Get-Process}

The credential store contains also a simple function to establish a connection with several systems or protocols. If you have already installed the underlying framework / modules, you can connect these endpoints:

  • CiscoUcs - Establish a connection to a Cisco UCS fabric interconnect.
  • FTP - Establish a connection to a FTP host.
  • NetAppFAS - Establish a connection to a NetApp Clustered ONTAP filer.
  • VMware - Establish a connection to a VMware vCenter or ESXi host.
  • CisServer - Establish a connection to the CisServer Service on vCenter Host.

Here are some basic examples:

Connect-To -RemoteHost "ucs.myside.local" -Type CiscoUcs
Connect-To -RemoteHost "ftp.myside.local" -Type FTP
Connect-To -RemoteHost "fas.myside.local" -Type NetAppFAS
Connect-To -RemoteHost "esx01.myside.local" -Type VMware
Connect-To -RemoteHost "vcr.myside.local" -Type CisServer