Docs: GUI custom login feature (#30799)

* saving because laptop is bad and should feel bad

* save

* make supported login types partial

* add api-docs partial

* update custom login docs

* reword tip?

* add delete section

* address feedback, update using a direct link section

* move tips down

* remove table lines and see if that fixes build?

* revert changes to custom-messages mdx

* add line break?

* format fixes

* empty commit again

* check vercel?

* add line break

* update "namespace" to be "namespace_path"

* reduce use of "preferred"

* address feedback

* use "settings" to match GUI verbiage

* missed a couple feedback comments

* add "single" and "multiple"

* fix link rendering

* fix namespace-path typos for namespace params referencing namespace context

* address feedback

---------

Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com>

Author: 2 people

website/content/docs/auth/github.mdx

@@ -6,6 +6,8 @@ description: The GitHub auth method allows authentication with Vault using GitHu
 
 # GitHub auth method
 
+@include 'tips/custom-authn.mdx'
+
 The `github` auth method can be used to authenticate with Vault using a GitHub
 personal access token. This method of authentication is most useful for humans:
 operators or developers using Vault directly via the CLI.

website/content/docs/auth/jwt/index.mdx

@@ -9,6 +9,8 @@ description: >-
 
 @include 'x509-sha1-deprecation.mdx'
 
+@include 'tips/custom-authn.mdx'
+
 ~> **Note**: Starting in Vault 1.17, if the JWT in the authentication request
 contains an `aud` claim (typical case) the associated `bound_audiences` for the
 "jwt" role must **exactly** match at least one of the `aud` claims declared for

website/content/docs/auth/ldap.mdx

@@ -8,6 +8,8 @@ description: |-
 
 # LDAP auth method
 
+@include 'tips/custom-authn.mdx'
+
 @include 'x509-sha1-deprecation.mdx'
 
 The `ldap` auth method allows authentication using an existing LDAP

website/content/docs/auth/okta.mdx

@@ -8,6 +8,8 @@ description: |-
 
 # Okta auth method
 
+@include 'tips/custom-authn.mdx'
+
 The `okta` auth method allows authentication using Okta and user/password
 credentials. This allows Vault to be integrated into environments using Okta.
 

website/content/docs/auth/radius.mdx

@@ -8,6 +8,8 @@ description: |-
 
 # RADIUS auth method
 
+@include 'tips/custom-authn.mdx'
+
 The `radius` auth method allows users to authenticate with Vault using an
 existing RADIUS server that accepts the PAP authentication scheme.
 

website/content/docs/auth/saml/index.mdx

@@ -10,6 +10,8 @@ description: >-
 
 @include 'alerts/enterprise-and-hcp.mdx'
 
+@include 'tips/custom-authn.mdx'
+
 The `saml` auth method allows users to authentication with Vault using their identity
 within a [SAML V2.0](https://saml.xml.org/saml-specifications) identity provider.
 Authentication is suited for human users by requiring interaction with a web browser.

website/content/docs/auth/token.mdx

@@ -6,6 +6,8 @@ description: The token store auth method is used to authenticate using tokens.
 
 # Token auth method
 
+@include 'tips/custom-authn.mdx'
+
 ~> **NOTE:** The Token auth method cannot be configured with Vault's built-in [Login MFA](/vault/docs/auth/login-mfa) feature.
 
 The `token` auth method is built-in and automatically available at `/auth/token`. It

website/content/docs/auth/userpass.mdx

@@ -8,6 +8,8 @@ description: >-
 
 # Userpass auth method
 
+@include 'tips/custom-authn.mdx'
+
 The `userpass` auth method allows users to authenticate with Vault using
 a username and password combination.