Update external certs docs to support new SANs types

Issue-ID: DCAEGEN2-2508
Signed-off-by: Piotr Marcinkiewicz <piotr.marcinkiewicz@nokia.com>
Change-Id: I4de0beab9e691cc9efe5e8eff39871e6699407fc

1 files changed, 1 insertions, 1 deletions

diff --git a/docs/sections/tls_enablement.rst b/docs/sections/tls_enablement.rst
index 4a049039..3d5a8cd5 100644
--- a/docs/sections/tls_enablement.rst
+++ b/docs/sections/tls_enablement.rst
@@ -176,7 +176,7 @@ From k8splugin 3.4.1 when external TLS is enabled (use_external_tls=true), keyst
        * A string (``output_type``) that indicates certificate output type.
        * A dictionary (``external_certificate_parameters``) with two elements:
            * A string (``common_name``) that indicates common name which should be present in certificate. Specific for every blueprint (e.g. dcae-ves-collector for VES).
-           * A string (``sans``) that indicates list of Subject Alternative Names (SANs) which should be present in certificate. Delimiter - , Should contain common_name value and other FQDNs under which given component is accessible.
+           * A string (``sans``) that indicates list of Subject Alternative Names (SANs) which should be present in certificate. Delimiter - , Should contain common_name value and other FQDNs under which given component is accessible. The following SANs types are supported: DNS names, IPs, URIs, emails.
 
    As a final step of the plugin the generated CMPv2 truststore entries will be appended to AAF CA truststore (see certificate artifacts below).