mirror of
https://github.com/optim-enterprises-bv/vault.git
synced 2025-11-02 19:47:54 +00:00
docs: clarified the MS SQL EKM provider's authentication behavior, and the implications for AppRole configuration (#24437)
This commit is contained in:
committed by
GitHub
parent
10f7011ca3
commit
1dfce2a271
@@ -47,6 +47,12 @@ EKM provider to use it.
|
|||||||
token_policies=tde-policy
|
token_policies=tde-policy
|
||||||
```
|
```
|
||||||
|
|
||||||
|
-> **Note:** After authenticating to Vault with the AppRole, the EKM provider
|
||||||
|
will re-use the token it receives until it expires, at which point it will
|
||||||
|
authenticate using the AppRole credentials again; it will not attempt to renew
|
||||||
|
its token. The example AppRole configuraiton here will work for this, but keep
|
||||||
|
that in mind if you choose to use a different AppRole configuration.
|
||||||
|
|
||||||
1. Retrieve the AppRole ID and secret ID for use later when configuring SQL Server:
|
1. Retrieve the AppRole ID and secret ID for use later when configuring SQL Server:
|
||||||
|
|
||||||
```bash
|
```bash
|
||||||
|
|||||||
Reference in New Issue
Block a user