Abblix.Jwt.Vault Namespace
| Classes | |
|---|---|
| AppRoleAuthenticationOptions | The AppRole auth method: the host proves who it is with a role and secret identifier pair. |
| KubernetesAuthenticationOptions | The Kubernetes auth method: the pod proves who it is with the service-account token Kubernetes projected into it, and Vault answers with a token for the named role. |
| ServiceCollectionExtensions | Registers the HashiCorp Vault / OpenBao Transit custodian for any host that signs or decrypts JSON Web Tokens, whether or not it is an OpenID Provider. |
| VaultAuthenticationOptions | Makes the package obtain its own Vault token by logging in against an auth method, and keep it alive: renew before the lease ends, log in again when the lease cannot be extended further. Configuring this section replaces a statically supplied Token; leaving it absent keeps today's posture, where the host hands a token over and owns its lifetime. |
| VaultKeyValueOptions | Points the key ring at a Vault / OpenBao KV version 2 secrets engine, on the same server the custodian uses: its address and token come from VaultTransitOptions, since one Vault holds both the key that protects the ring and the ring itself. |
| VaultTransitOptions | Points the custodian at a HashiCorp Vault / OpenBao Transit secrets engine: where it is and how to authenticate to it, and nothing about which keys to use. Which keys, and therefore whether their private halves ever enter this process, is the placement choice that follows the custodian registration. |
| VaultTransport | The shared HTTP transport to a Vault / OpenBao server. |