Used by Membrane's TLS components to validate remote certificates presented during SSL/TLS handshakes.
Syntax
truststore:
algorithm: <string>
checkRevocation: <string>
location: <string>
password: <string>
provider: <string>
type: <string>truststore: algorithm: <string> checkRevocation: <string> location: <string> password: <string> provider: <string> type: <string>
Attributes
| Name | Required | Default | Description | Examples |
|---|---|---|---|---|
| algorithm | false | - | Trust manager algorithm used to validate certificate chains. | - |
| checkRevocation | false | - | Comma-separated PKIX revocation options: ONLY_END_ENTITY, PREFER_CRLS, NO_FALLBACK, SOFT_FAIL. | ONLY_END_ENTITY,SOFT_FAIL |
| location | false | - | A file/resource containing the PKCS#12 keystore (*.p12). | - |
| password | false | - | The password used to open the keystore/truststore. | - |
| provider | false | - | Provider to use when loading the keystore. | - |
| type | false | - | Keystore type (e.g., PKCS12, JKS), or PEM to load location as one or more bare X.509 certificates (.cer/.crt/.pem) instead of a keystore container. PEM only makes sense for a truststore, since a bare certificate carries no private key. location may hold more than one certificate - either PEM blocks or DER certificates concatenated back to back - and every one of them becomes a separate trust anchor; this is how to trust a CA chain (root plus intermediates) when the peer's messages only ever carry its leaf certificate. | - |