Credentials Store

How it works

The Credentials Store holds a username and password per target, identified by its FQDN (fully-qualified domain name). Entries are encrypted at rest and stay local — nothing is sent to any cloud service. ServerEngine uses them to authenticate WinRM jobs and remote sessions, and your scripts can pull them in at runtime.

Add a credential

1. 1

   Open the Credentials Store

   Add a new entry with the target's username, password, hostname/short name, and domain. The FQDN is derived as shortName.domain.
2. 2

   Mark the platform

   Choose Windows (WinRM) or Linux (SSH) so ServerEngine connects with the right protocol. SSH targets can authenticate with a password or an SSH key.
3. 3

   Group for bulk use

   Organize hosts into server groups so a single job or schedule can target them all at once.

Runtime credential injection

Instead of hardcoding secrets, reference a stored credential by its FQDN inside a script. ServerEngine substitutes the real values at execution time and discards them afterwards — so your scripts stay safe to commit to version control.

# These tokens are replaced with the real values when the job runs
$user = SE-CredentialsStore.Username.(esxi01.demo.local)
$pass = SE-CredentialsStore.Password.(esxi01.demo.local)

$secure = ConvertTo-SecureString $pass -AsPlainText -Force
$cred   = New-Object System.Management.Automation.PSCredential($user, $secure)

Connect-VIServer -Server esxi01.demo.local -Credential $cred