// Benutzung · Grundlagen
Managing credentials
The Credentials page lists every saved credential, grouped by location, so you can see what each one is attached to, reuse them, and clean up ones nothing uses. Secrets are never shown — only what a credential is and where it's used.
Create a credential
Two ways:
- From the Credentials page — under a location, click New credential, give it a name, pick a kind (proxmox / idrac / k8s), and enter the secret.
- While adding a resource — the resource form creates one inline; it shows up here afterwards, named after the resource by default.
A credential belongs to its location and can only be attached to resources in that same location.
Credential shapes by kind
What "the secret" is depends on the kind:
| Kind | Fields | Notes |
|---|---|---|
| proxmox | API token id (api_user) + API token secret (api_secret) |
The id is the full token, USER@REALM!TOKENID (e.g. fleeger@pve!monitoring) — not just the user. The secret is the token's UUID value, shown once when you create it. Sent to Proxmox as PVEAPIToken=<id>=<secret>. Creating the read-only monitoring token is walked through in Connect a Proxmox homelab. |
| idrac | Username + Password | The Redfish/BMC login. |
| k8s | Kubeconfig | Paste or upload a kubeconfig; leave blank to use an in-cluster ServiceAccount when the agent runs inside the cluster. Credentials must be inline (token, client-certificate-data/client-key-data, certificate-authority-data): a kubeconfig with an exec plugin, an auth-provider, or a file path is refused. See Managing a Kubernetes cluster. |
Whether the target's TLS certificate is verified is not part of the credential — it's the Allow invalid/self-signed TLS certs toggle on the resource (proxmox/idrac). See adding a resource.
Reuse one credential across resources
A credential can be attached to many resources at once. When adding or editing a resource, choose Use existing and pick the credential instead of entering a new secret. Or, on the Credentials page, click Attach on a credential and search for the resource.
The payoff: rotate once, everywhere. Use Rename / rotate to change a shared credential's secret in one place, and every resource using it picks up the new secret — no need to update each one.
Spot and clean up orphans
A credential that no resource uses is an orphan — highlighted, and labelled with what it was last attached to (e.g. "was: pve-orig") so you can recognise it. Orphans are dangling secrets worth removing.
- Delete is only enabled for orphaned credentials. To delete one that's still in use, Detach it from each resource first (the next to each attachment), then delete.
- Deleting a whole location removes all of its credentials automatically.
Detaching
Detaching a credential from a resource (the on an attachment, or removing it via the resource's Edit form) leaves the credential in place — it just stops that resource from using it. If that was its last use, it becomes an orphan.