I have tried enabling the Istio jwt authentication and authorization for my backend services with keycloak. This functionality works completely fine on plain http without any issues and I shifted over everything onto https and things started to fail. The same RequestAuthentication rules and AuthorizationPolicy rules doesn’t work with https endpoints. I kind of exposed the keycloak in the same cluster on istio ingress gateway with custom go daddy cert this is a valid cert and not a wildcard cert but for some reason the RequestAuthentication still fails. Is this is cert issue?? How can I make istio to trust the client cert from go daddy?? Can someone help me on this??