From f920a277be07eca7f823fd282f31815b638f7596 Mon Sep 17 00:00:00 2001 From: marcin-kulik Date: Tue, 2 May 2023 17:34:42 +0000 Subject: [PATCH] backport of commit f4689b1d85265dcb092e45bbde465d85b2cf1ec4 --- website/content/docs/platform/mssql/installation.mdx | 8 ++++---- 1 file changed, 4 insertions(+), 4 deletions(-) diff --git a/website/content/docs/platform/mssql/installation.mdx b/website/content/docs/platform/mssql/installation.mdx index a19d9394f08d..c30c44dc2261 100644 --- a/website/content/docs/platform/mssql/installation.mdx +++ b/website/content/docs/platform/mssql/installation.mdx @@ -50,8 +50,8 @@ EKM provider to use it. 1. Retrieve the AppRole ID and secret ID for use later when configuring SQL Server: ```bash - vault read auth/approle/role/tde-role/role-id - vault write -f auth/approle/role/tde-role/secret-id + vault read auth/approle/role/ekm-encryption-key-role/role-id + vault write -f auth/approle/role/ekm-encryption-key-role/secret-id ``` 1. Enable the transit secret engine and create a key: @@ -137,8 +137,8 @@ installation. ```sql -- Replace and with the values from -- the earlier vault commands: - -- vault read auth/approle/role/tde-role/role-id - -- vault write -f auth/approle/role/tde-role/secret-id + -- vault read auth/approle/role/ekm-encryption-key/role-id + -- vault write -f auth/approle/role/ekm-encryption-key/secret-id CREATE CREDENTIAL TransitVaultCredentials WITH IDENTITY = '', SECRET = ''