We have a policy end point in which we route to a backend end point that requires client certificate to be presented by the gateway ( acting as a client here ) . In the routing assertion , I picked the private key that is needed for the gateway to authenticate itself to the backend end point. However the backend end point team states that the API gateway is not presenting the certificate when asked for it, basically there is a redirect to a location on the backend server and even though the follow redirect option is checked on the routing assertion, the routing returns a 302 and is not presenting the certificate to the backend server.
What am I missing here on the routing assertion ? Apart from pointing to the private key and following redirects , is there any other setting on the routing assertion that has to be enabled/disabled to present the client certificate to the backend server requesting the client certificate from the api gateway ?