feat: add option to use x.509 certificate system-api-user tokens (#11876)

# Which Problems Are Solved

System API users currently authenticate using raw RSA public keys
configured via Path or KeyData. This approach doesn't integrate well
with Kubernetes tooling.

# How the Problems Are Solved

Allow for the `path`/`keyData` to be an X.509 certificate. 

The `NotBefore` and `NotAfter` fields of the certificate are beeing
respected when validating the JWT.

# Additional Changes

# Additional Context

- Closes #11442

---------

Co-authored-by: Livio Spring <[email protected]>
This commit is contained in:
Wim Van Laer
2026-03-23 13:32:27 +00:00
committed by GitHub
co-authored by Livio Spring
parent 85ce8c153b
commit 70adaff793
4 changed files with 321 additions and 17 deletions
@@ -54,6 +54,9 @@ SystemAPIUsers:
KeyData: <base64 encoded value of system-user-1.pub>
```
You can either specify the public key directly in this way or wrap it in an X.509 certificate for better key management
in environments like kubernetes.
You can define memberships for the user as well:
```yaml