Credentials Store
Securely store and manage all your server credentials locally with full encryption, ensuring safe and seamless authentication — without ever exposing them in your scripts.
Vault Capabilities
Secure Credential Vault
Locally encrypted storage for all server credentials
- Store credentials locally with full encryption
- Username and password stored per credential entry
- Double-click the lock icon to copy FQDN to clipboard
- Credentials never leave the local machine unencrypted
- Seamless access for scripts and runbooks
Hover to see specs
Secure Credential Management
Retrieve credentials safely inside any script or runbook
- Never expose credentials in your scripts again
- Retrieve username directly in PowerShell or Python
- Retrieve password directly in PowerShell or Python
- Supported in both single scripts and runbooks
- Runtime retrieval — credentials injected at execution
- Works with all WinRM-based automation targets
Hover to see specs
How It Works
Add a credential entry to the Credentials Store
Add Credential
Open the Credentials Store and create a new entry. Give it an IP-Address or DNSName+Domain then enter the username and password to store.
Double-click the lock icon to copy the FQDN
Copy FQDN
Double-click the 🔒 lock icon next to any credential entry to instantly copy its FQDN identifier to your clipboard.
Paste the retrieval key into your script
Use in Script
Paste the FQDN into the SE-CredentialsStore.Username.* or SE-CredentialsStore.Password.* retrieval syntax in your script.
Credentials injected securely at execution
Secure Execution
When the script runs, ServerEngine retrieves and injects the credential at runtime. No plaintext passwords ever appear in your code.
Script Integration Syntax
Hover for details
Username Retrieval
Use this key anywhere in your script where a username is required. ServerEngine replaces it with the stored username at runtime — never hardcoded, never exposed in logs.
Hover for details
Password Retrieval
Use this key wherever a password is required. The encrypted value is retrieved from the local vault at execution time and injected securely — your script source stays clean.
💡 Quick Copy Tip
In the Credentials Store, double-click the 🔒 lock icon in the first column to instantly copy its YOUR_CREDENTIAL_FQDN to your clipboard — ready to paste directly into your script.
Security Highlights
Local Encrypted Storage
All credentials are stored locally with full encryption — nothing is sent to external servers or cloud services.
Local Encrypted Storage
The vault lives on your machine, encrypted at rest. No cloud sync, no external exposure — your credentials stay entirely within your infrastructure.
Zero Hardcoded Credentials
Scripts and runbooks reference credentials by key — no plaintext passwords ever appear in your source code or logs.
Zero Hardcoded Credentials
Referencing credentials by FQDN key means your scripts are safe to share, version-control, or audit — the actual secret values are never present in code.
Runtime Injection
Credentials are retrieved and injected at the moment of execution — decrypted only when needed, then immediately discarded.
Runtime Injection
The vault decrypts and injects the credential value only at the exact moment your script needs it — minimizing the window of exposure to near zero.
Runbook Support
Credential retrieval works seamlessly across every step of multi-step runbooks, including steps that run after a reboot.
Runbook Support
Every runbook step — whether it’s step 1 or step 10 after a reboot — can securely retrieve credentials from the vault without re-authentication.
FQDN-Based Identification
Each credential is uniquely identified by its FQDN, making it easy to manage credentials for large server estates.
FQDN-Based Identification
Using the server’s FQDN as the credential key makes the store intuitive to manage — one entry per server, always unambiguous, easy to audit.
One-Click FQDN Copy
Double-click the lock icon on any entry to copy its FQDN instantly — no manual typing, no copy-paste errors.
One-Click FQDN Copy
The double-click-to-copy shortcut means you can go from the Credentials Store to a working retrieval key in your script in seconds — zero friction.