OIDC: short-lived credentials instead of stored keys
How OpenID Connect lets one system prove its identity to another without a stored secret, why that removes a real risk, and where Voroa stands on it today.
What this covers
The usual way one system authenticates to another is a long-lived key, copied into a settings screen and left there for years. That key is a standing risk: it does not expire, it is often over-privileged, and if it leaks nobody finds out. OpenID Connect replaces it with a short-lived token issued at the moment it is needed and valid for minutes. The receiving system verifies who issued it and what it represents, rather than matching a stored string, so there is no secret sitting around to steal.
Voroa does not support OIDC-based authentication today, and does not publish an API for another system to authenticate against.