VaultAuthenticationOptions Class
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.
public sealed class VaultAuthenticationOptionsInheritance System.Object → VaultAuthenticationOptions
Remarks
Exactly one of the method subsections must be set. The section is null when a host does not configure it - there is deliberately no default instance, because an empty section and an absent one must stay distinguishable for the feature to have an off switch.
Properties
VaultAuthenticationOptions.AppRole Property
Log in with an AppRole's role and secret identifiers, which is the arrangement for a host outside Kubernetes or one whose Vault does not trust the cluster.
public Abblix.Jwt.Vault.AppRoleAuthenticationOptions? AppRole { get; set; }Property Value
VaultAuthenticationOptions.Kubernetes Property
Log in with the pod's projected service-account token, which is the arrangement for a host running on Kubernetes: the kubelet rotates the file and this package re-reads it on every login.
public Abblix.Jwt.Vault.KubernetesAuthenticationOptions? Kubernetes { get; set; }