From 7f36a29e04df91077ae0e9110028d6ce36ff730c Mon Sep 17 00:00:00 2001 From: Austin Gebauer <34121980+austingebauer@users.noreply.github.com> Date: Thu, 24 Mar 2022 10:09:03 -0700 Subject: [PATCH] docs: fix formatting in upgrade guide notes for oidc provider (#14678) --- .../docs/upgrading/upgrade-to-1.10.x.mdx | 22 +++++++++---------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/website/content/docs/upgrading/upgrade-to-1.10.x.mdx b/website/content/docs/upgrading/upgrade-to-1.10.x.mdx index 22a0c9973c..e26bcc20c4 100644 --- a/website/content/docs/upgrading/upgrade-to-1.10.x.mdx +++ b/website/content/docs/upgrading/upgrade-to-1.10.x.mdx @@ -62,19 +62,19 @@ OIDC provider system to reduce configuration steps and enhance usability. The following built-in resources are included in each Vault namespace starting with Vault 1.10: -- A "default" OIDC provider that's usable by all client applications -- A "default" key for signing and verification of ID tokens -- An "allow_all" assignment which authorizes all Vault entities to authenticate via a - client application + - A `default` OIDC provider that's usable by all client applications + - A `default` key for signing and verification of ID tokens + - An `allow_all` assignment which authorizes all Vault entities to authenticate via a + client application If you created an [OIDC provider](/api-docs/secret/identity/oidc-provider#create-or-update-a-provider) -with the name "default", [key](/api-docs/secret/identity/tokens#create-a-named-key) with the -name "default", or [assignment](/api-docs/secret/identity/oidc-provider#create-or-update-an-assignment) -with the name "allow_all" using the Vault 1.9 tech preview, the installation of these built-in -resources will be skipped. We *strongly* recommend that you delete any resources that have -naming collisions before upgrading to Vault 1.10. Failing to delete resources with naming -collisions could result unexpected default behavior. Additionally, we recommend reading the -corresponding details in the OIDC provider [concepts](/docs/concepts/oidc-provider) document +with the name `default`, [key](/api-docs/secret/identity/tokens#create-a-named-key) with the +name `default`, or [assignment](/api-docs/secret/identity/oidc-provider#create-or-update-an-assignment) +with the name `allow_all` using the Vault 1.9 tech preview, the installation of these built-in +resources will be skipped. We _strongly recommend_ that you delete any existing resources +that have naming collisions before upgrading to Vault 1.10. Failing to delete resources with +naming collisions could result unexpected default behavior. Additionally, we recommend reading +the corresponding details in the OIDC provider [concepts](/docs/concepts/oidc-provider) document to understand how the built-in resources are used in the system. ## Known Issues