OSSMDOC-639: moves ossm-1668 back to known issue

Author: rh-tokeefe

modules/ossm-rn-fixed-issues.adoc

@@ -19,9 +19,6 @@ The following issues been resolved in the current release:
 [id="ossm-rn-fixed-issues-ossm_{context}"]
 == {SMProductShortName} fixed issues
 
-* https://issues.redhat.com/browse/OSSM-1668[OSSM-1668]
-`jwksResolverCA` field is missing in `SMCP`.
-
 * https://issues.redhat.com/browse/OSSM-1325[OSSM-1325] istiod pod crashes and displays the following error message: `fatal error: concurrent map iteration and map write`.
 
 * https://issues.redhat.com/browse/OSSM-1211[OSSM-1211]

modules/ossm-rn-known-issues.adoc

@@ -34,6 +34,13 @@ These are the known issues in {SMProductName}:
 
 * link:https://github.com/istio/istio/issues/14743[Istio-14743] Due to limitations in the version of Istio that this release of {SMProductName} is based on, there may be applications that are currently incompatible with {SMProductShortName}. See the linked community issue for details.
 
+* https://issues.redhat.com/browse/OSSM-1668[OSSM-1668]
+`jwksResolverCA` field is missing in `SMCP`.
++
+If you upgrade from Service Mesh operator 2.1.3 to Service Mesh operator 2.2, then the `jwksResolverCA` field is not supported.
++
+Workaround: Use the `techPreview` `jwksResolverExtraRootCA` field to enable additional JWKS CA certificates.
+
 //Keep OSSM-1655 in RN, closed as "explained" error is expected.
 * https://issues.redhat.com/browse/OSSM-1655[OSSM-1655] Kiali dashboard shows error after enabling mTLS in `SMCP`.
 +