-
Notifications
You must be signed in to change notification settings - Fork 599
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Talos API: Support OIDC #5192
Comments
As Talos API is really low-level, and e.g. networking might be restricted (blocking OIDC requests), what we considered as an option: having external system handle OIDC and issue client certs. Also we could add additional certs to the machine configuration so that Talos will accept client certs issued by extra CAs (which might live in the external PKI system) |
The idea would be a similar support as kube-apiserver - if enabled, the Talos API itself only periodically fetches JWKS. Users can keep using client certs for auth, or if they present a valid JWT, only the things in the tokens are considered (so assuming fat tokens, no profile lookup by the apiserver) |
I'm in the process of designing exactly this. However, as Andrey says, it's going to take a number of changes in the way we handle authentication. It's definitely something we want to support, but it will take some time. |
See rfcs/8 |
Seems to be a dup of #3306 ? |
This issue is stale because it has been open 180 days with no activity. Remove stale label or comment or this will be closed in 7 days. |
This issue was closed because it has been stalled for 7 days with no activity. |
Feature Request
On a fresh install,
talosconfig
contains a 10 year valid certificate, signed by the CA frommachine.ca.crt
.While it's possible to create a shorter-living and more restricted
talosconfig
, by picking a shorter--crt-ttl
and a more restricted role via--roles
:… there's no OIDC support in Talos API.
The text was updated successfully, but these errors were encountered: