From c408a34a212512b09aab8ab7c363dbd10cf1cbda Mon Sep 17 00:00:00 2001 From: Lisa Cawley Date: Wed, 11 Mar 2020 09:13:25 -0700 Subject: [PATCH] [DOCS] Fixes link to custom realm examples (#53205) --- x-pack/docs/en/security/authentication/custom-realm.asciidoc | 5 ++--- 1 file changed, 2 insertions(+), 3 deletions(-) diff --git a/x-pack/docs/en/security/authentication/custom-realm.asciidoc b/x-pack/docs/en/security/authentication/custom-realm.asciidoc index 3985e745704..a2a965d4f89 100644 --- a/x-pack/docs/en/security/authentication/custom-realm.asciidoc +++ b/x-pack/docs/en/security/authentication/custom-realm.asciidoc @@ -11,8 +11,7 @@ extension as part of an ordinary elasticsearch plugin. ==== Implementing a custom realm Sample code that illustrates the structure and implementation of a custom realm -is provided in the https://github.com/elastic/shield-custom-realm-example[custom-realm-example] -repository on GitHub. You can use this code as a starting point for creating your +is provided in https://github.com/elastic/elasticsearch/tree/{branch}/x-pack/qa/security-example-spi-extension. You can use this code as a starting point for creating your own realm. To create a custom realm, you need to: @@ -86,7 +85,7 @@ bin/elasticsearch-plugin install file:////my-realm-1.0.zip . Add a realm configuration of the appropriate realm type to `elasticsearch.yml` under the `xpack.security.authc.realms` namespace. -You must define your realm within the namespace that matchesto the type defined +You must define your realm within the namespace that matches the type defined by the extension. The options you can set depend on the settings exposed by the custom realm. If you are configuring multiple realms, you should also explicitly set the