2017-09-21 13:32:15 +02:00
|
|
|
| AppVeyor Overall | AppVeyor Master | AppVeyor Dev | Coveralls.io | Download |
|
|
|
|
|
| :--------------: | :-------------: | :----------: | :-----------: | :--------:|
|
|
|
|
|
| [](https://ci.appveyor.com/project/OCram85/PSCredentialStore) | [](https://ci.appveyor.com/project/OCram85/PSCredentialStore/branch/master) | [](https://ci.appveyor.com/project/OCram85/PSCredentialStore/branch/dev) | [](https://coveralls.io/github/OCram85/PSCredentialStore?branch=master) | [](https://www.powershellgallery.com/packages/PSCredentialStore)
|
|
|
|
|
|
|
|
|
|
General
|
|
|
|
|
=======
|
|
|
|
|
|
2017-10-16 19:47:19 +02:00
|
|
|
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
|
2017-09-21 13:32:15 +02:00
|
|
|
ony accessed by your account on the same machine. The shared store enables you to use different credentials for your
|
2017-10-16 19:47:19 +02:00
|
|
|
scripts without exposing them as plain text.
|
2017-09-21 13:32:15 +02:00
|
|
|
|
|
|
|
|
**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.
|
|
|
|
|
|
2017-10-16 19:47:19 +02:00
|
|
|
For more details read the [about_PSCredentialStore](/src/en-US/about_PSCredential.help.txt) page.
|
2017-09-21 13:32:15 +02:00
|
|
|
|
|
|
|
|
Installation
|
|
|
|
|
============
|
|
|
|
|
|
|
|
|
|
PowerShellGallery.com (Recommended Way)
|
|
|
|
|
---------------------------------------
|
|
|
|
|
|
|
|
|
|
* 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](https://github.com/OCram85/PSCredentialStore/releases/latest) page.
|
|
|
|
|
* Download the `PSCredentialStore.zip`.
|
2017-10-16 19:47:19 +02:00
|
|
|
* Unpack the zip file and put it in your Powershell module path.
|
2017-09-21 13:32:15 +02:00
|
|
|
* Don't forget to change the NTFS permission flag in the context menu.
|
|
|
|
|
* Start with `Import-Module PSCredentialStore`
|
|
|
|
|
|
|
|
|
|
Quick Start
|
|
|
|
|
-----------
|
|
|
|
|
|
2017-10-16 19:47:19 +02:00
|
|
|
**1.** First we need a blank credential store. You can decide between a *private* or *shared* store. The private
|
2017-09-21 13:32:15 +02:00
|
|
|
Credential Store can only be accessed with your profile on the machine you created it.
|
|
|
|
|
```powershell
|
2017-10-16 19:47:19 +02:00
|
|
|
# Private credential store
|
2017-09-21 13:32:15 +02:00
|
|
|
New-CredentialStore
|
|
|
|
|
|
2017-10-16 19:47:19 +02:00
|
|
|
# Shared credential rtore
|
2017-09-21 13:32:15 +02:00
|
|
|
New-CredentialStore -Shared
|
|
|
|
|
|
2017-10-16 19:47:19 +02:00
|
|
|
#Shared credential store in custom Location
|
2017-09-21 13:32:15 +02:00
|
|
|
New-CredentialStore -Shared -Path 'C:\CredentialStore.json'
|
|
|
|
|
```
|
|
|
|
|
|
2017-10-16 19:47:19 +02:00
|
|
|
**2.** Now you can manage your credential store items:
|
2017-09-21 13:32:15 +02:00
|
|
|
```powershell
|
|
|
|
|
# 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}
|
|
|
|
|
```
|
|
|
|
|
|
2017-10-16 19:47:19 +02:00
|
|
|
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:
|
2017-09-21 13:32:15 +02:00
|
|
|
|
|
|
|
|
* **CiscoUcs** - Establish a connection to a Cisco UCS fabric interconnect.
|
|
|
|
|
* Required Modules: [`Cisco.UCS.Core`, `Cisco.UCSManager`](https://software.cisco.com/download/release.html?i=!y&mdfid=286305108&softwareid=284574017&release=2.1.1)
|
|
|
|
|
* **FTP** - Establish a connection to a FTP host.
|
|
|
|
|
* Required Modules: [`WinSCP`](https://www.powershellgallery.com/packages/WinSCP)
|
|
|
|
|
* **NetAppFAS** - Establish a connection to a NetApp Clustered ONTAP filer.
|
|
|
|
|
* Required Modules: [`DataONTAP`](http://mysupport.netapp.com/tools/info/ECMLP2310788I.html?productID=61926)
|
|
|
|
|
* **VMware** - Establish a connection to a VMware vCenter or ESXi host.
|
|
|
|
|
* Required Modules: [`VMware.VimAutomation.Core`](https://www.powershellgallery.com/packages/VMware.PowerCLI)
|
2017-10-23 07:43:16 +02:00
|
|
|
* **CisServer** - Establish a connection to the CisServer Service on vCenter Host.
|
|
|
|
|
* Required Modules: [`VMware.VimAutomation.Cis.Core`](https://www.powershellgallery.com/packages/VMware.PowerCLI)
|
2017-09-21 13:32:15 +02:00
|
|
|
|
|
|
|
|
Here are some basic examples:
|
|
|
|
|
|
|
|
|
|
```powershell
|
|
|
|
|
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
|
2017-10-23 07:43:16 +02:00
|
|
|
Connect-To -RemoteHost "vcr.myside.local" -Type CisServer
|
2017-09-21 13:32:15 +02:00
|
|
|
```
|
