diff --git a/x-pack/docs/en/security/authentication/oidc-guide.asciidoc b/x-pack/docs/en/security/authentication/oidc-guide.asciidoc index 032194c365af8..ee318a8c3a133 100644 --- a/x-pack/docs/en/security/authentication/oidc-guide.asciidoc +++ b/x-pack/docs/en/security/authentication/oidc-guide.asciidoc @@ -552,7 +552,7 @@ OP or a third party (see <>). In order to do so, you must exp OpenID Connect authentication endpoint within {kib}, so that the {kib} server will not reject these external messages. - +[[oidc-without-kibana]] === OpenID Connect without {kib} The OpenID Connect realm is designed to allow users to authenticate to {kib} and as diff --git a/x-pack/docs/en/security/authentication/saml-guide.asciidoc b/x-pack/docs/en/security/authentication/saml-guide.asciidoc index b994a0709293f..5249a5a1b3e45 100644 --- a/x-pack/docs/en/security/authentication/saml-guide.asciidoc +++ b/x-pack/docs/en/security/authentication/saml-guide.asciidoc @@ -843,6 +843,7 @@ It is possible to have one or more {kib} instances that use SAML, while other instances use basic authentication against another realm type (e.g. <> or <>). +[[saml-troubleshooting]] === Troubleshooting SAML Realm Configuration The SAML 2.0 specification offers a lot of options and flexibility for the implementers