Details
-
Enhancement
-
Resolution: Unresolved
-
Critical
-
None
-
2.10 GA
-
3
-
False
-
False
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Not Started
-
Undefined
Description
Currently the TLS Client Certificate Validation policy explains that APicast needs to be configured to terminate TLS as a requirement. The steps are detailed in the sub-chapter "4.1.26.1.1. Setting up APIcast to work with the policy" using a secret and mounting the secret in APIcast. This will enable TLS termination globally (for all Products).
The request is to explain that there are 2 ways to configure the TLS termination:
a) Globally (as currently described in the chapter 4.1.26.1.1. Setting up APIcast to work with the policy)
b) Per Product with the already built-in TLS Termination policy. This second option is the only way to confiture TLS termination when deploying APIcast self managed with the Operator since it is not possible to mount volumes in APIcast deployed with the Operator.
Attachments
Issue Links
- is related to
-
THREESCALE-7033 Allow injection of custom environment (apicast operator)
- Closed
-
THREESCALE-6167 Provide more complete steps in the Documentation for the "TLS Termination" Policy
- SME Review