We are trying to route via HTTP from the Gateway (version 9.1) to a server that uses a SHA2 certificate. (The public cert is attached.) If we make a request to the server from chrome, the request is successful. When we make the request via the Gateway, we get the following error:
Problem routing to https://mn-srvcdev.tcfbank.com:8021/. Error msg: Unable to obtain HTTP response from https://mn-srvcdev.tcfbank.com:8021/: Certificate not verified. Caused by: Server cert 'firstname.lastname@example.org,cn=api-dev.tcfbank.com,ou=information security,o=tcf financial,l=minneapolis,st=minnesota,c=us' found but not trusted for SSL.
While adding the certificate into the Gateway using "Manage Certificates" task, on the last tab, you need to select the certificate to be a Trusted Anchor.