From ce2cdc3660cc7c0514cda8f164f918db6dcafa83 Mon Sep 17 00:00:00 2001 From: John Blum Date: Fri, 19 Apr 2019 14:06:18 -0700 Subject: [PATCH] Change wording regarding GemFire/Geode Security (Auth) & SSL configuration. --- .../src/docs/asciidoc/configuration-annotations.adoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/spring-geode-docs/src/docs/asciidoc/configuration-annotations.adoc b/spring-geode-docs/src/docs/asciidoc/configuration-annotations.adoc index 572c108d..d2bbdd73 100644 --- a/spring-geode-docs/src/docs/asciidoc/configuration-annotations.adoc +++ b/spring-geode-docs/src/docs/asciidoc/configuration-annotations.adoc @@ -164,7 +164,7 @@ in SBDG must be triggered before the ClientCache _auto-configuration_ class, whi (i.e. you must also explicitly declare the `@EnableSecurity` annotation in this case since you overrode the _auto-configuration_ of the cache, and, well, implicitly Security as well). -Again, this is a GemFire/Geode limitation in how Security (Auth) and SSL meta-data is supplied to GemFire/Geode. +Again, this is due to the way Security (Auth) and SSL meta-data must be supplied to GemFire/Geode. See the <> for more details.