#### [Abblix\.Jwt\.Vault](https://www.abblix.com/en/docs/api/abblix-jwt-vault 'index')
### [Abblix\.Jwt\.Vault](https://www.abblix.com/en/docs/api/abblix-jwt-vault/Abblix.Jwt.Vault 'Abblix\.Jwt\.Vault')

## VaultKeyValueOptions Class

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](https://www.abblix.com/en/docs/api/abblix-jwt-vault/Abblix.Jwt.Vault.VaultTransitOptions 'Abblix\.Jwt\.Vault\.VaultTransitOptions'), since one Vault holds both the key that
protects the ring and the ring itself\.

```csharp
public sealed class VaultKeyValueOptions
```

Inheritance [System\.Object](https://learn.microsoft.com/en-us/dotnet/api/system.object 'System\.Object') → VaultKeyValueOptions

### Remarks
The engine must be KV VERSION 2\. Only v2 offers the check\-and\-set write this ring is built on, and it is what
makes exactly one pod win a period: v1 overwrites blindly, which would let two pods each believe they minted
the period's key\.
### Properties

## VaultKeyValueOptions\.Mount Property {#Abblix.Jwt.Vault.VaultKeyValueOptions.Mount}

Mount path of the KV v2 engine \(the conventional mount is `secret`\)\.

```csharp
public string Mount { get; set; }
```

#### Property Value
[System\.String](https://learn.microsoft.com/en-us/dotnet/api/system.string 'System\.String')

## VaultKeyValueOptions\.Path Property {#Abblix.Jwt.Vault.VaultKeyValueOptions.Path}

The path under the mount that holds the ring; each key becomes one secret beneath it\.

```csharp
public string Path { get; set; }
```

#### Property Value
[System\.String](https://learn.microsoft.com/en-us/dotnet/api/system.string 'System\.String')