Skip to content

Commit a4eeebb

Browse files
authored
Merge pull request #2613 from mulesoft/W-14848493-Update-tls-configuration44-dm
W-14848493-Update-tls-configuration44-dm
2 parents 6153ff1 + 50447c1 commit a4eeebb

File tree

1 file changed

+14
-1
lines changed

1 file changed

+14
-1
lines changed

modules/ROOT/pages/tls-configuration.adoc

Lines changed: 14 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -66,7 +66,20 @@ The keystore contains one or two passwords:
6666

6767
== Client Configuration
6868

69-
If the `tls:context` is empty (no `tls:key-store` or `tls:trust-store` defined), then the default values of the JVM are used, which usually include a truststore with certificates for all the major certifying authorities.
69+
If the `tls:context` has an empty truststore defined, then the default values of the JVM are used, which usually include a truststore with certificates for all the major certifying authorities. Consider the following scenarios:
70+
71+
* When the truststore is defined inline:
72+
----
73+
<tls:context name>
74+
<tls:trust-store />
75+
</tls:context>
76+
----
77+
* When the truststore is defined with a global element:
78+
----
79+
<tls:context name="example">
80+
<tls:trust-store />
81+
</tls:context>
82+
----
7083

7184
If the client requires a certificate from the server that it is trying to connect to, then add the `tls:trust-store` element. Set `path` to the location of the truststore file that contains the certificates of the trusted servers.
7285

0 commit comments

Comments
 (0)