From 014bacae0fbb76c6e6baf83f267258211e28d3cc Mon Sep 17 00:00:00 2001 From: pawel Date: Thu, 7 Nov 2019 11:15:00 +0100 Subject: Update authentication types description Issue-ID: DCAEGEN2-1913 Signed-off-by: pawel Change-Id: Ic8b611a65c1c7eb781265b2481f60952b7abfb24 --- docs/sections/services/ves-http/installation.rst | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) (limited to 'docs/sections/services/ves-http/installation.rst') diff --git a/docs/sections/services/ves-http/installation.rst b/docs/sections/services/ves-http/installation.rst index 3f8f943a..0e399301 100644 --- a/docs/sections/services/ves-http/installation.rst +++ b/docs/sections/services/ves-http/installation.rst @@ -34,9 +34,7 @@ Authentication Support VES Collector support following authentication types * *auth.method=noAuth* default option - no security (http) - * *auth.method=certOnly* is used to enable mutual TLS authentication (https) * *auth.method=certBasicAuth* is used to enable mutual TLS authentication or/and basic HTTPs authentication - * *auth.method=basicAuth* is used to enable basic HTTPs authentication Default ONAP deployed VESCOllector is configured for "noAuth". If VESCollector instance need to be deployed with authentication enabled, follow below setup @@ -218,7 +216,7 @@ In this case blueprint can be deleted explicitly using this command. cfy blueprint delete ves-tls -Known Issue : When VESCollector is required to be deployed with authentication enabled *auth.method=certOnly* or *auth.method: certBasicAuth* or *auth.method: basicAuth* +Known Issue : When VESCollector is required to be deployed with authentication enabled *auth.method: certBasicAuth* the blueprint currently disables healthcheck parameters configuration (below). This causes no readiness probe to be deployed in K8S when VES Collector is deployed with authentication enabled. -- cgit 1.2.3-korg