search cancel

Error : back-end Server (sernername) Certificate presented is bad SPS


Article ID: 7964


Updated On:


CA Single Sign On Secure Proxy Server (SiteMinder) CA Single Sign On SOA Security Manager (SiteMinder) CA Single Sign-On SITEMINDER



When trying to reverse proxy to Wildfly 8.2 Jboss on https port from
CA Access Gateway (SPS). Though both Apache on CA Access Gateway (SPS)
and Jboss are listening on https ports, but when the reverse proxy
rule is configured to forward request to Jboss on https port it fails
with a noodle error.

   The back-end Server(sernername) Certificate presented is bad

spsagenttrace.log :

  [Tried to send the request to backend web server three times.Throwing the exception to client. ]

  [Noodle::doGet][com.rsa.ssl.SSLException: Certificate for <>
  is not trusted or bad certificate
  at Source)]

When proxy rule is configured to forward request to Jboss on http port it works.




The back-end Server Certificate was not in the ca-bundle.cert of the
CA Access Gateway (SPS).




CA Access Gateway (SPS) 12.6 SP1




Adding the self-signed certificate of the back-end server in the
ca-bundle.cert file resolved the issue (1).


Additional Information



    Configuring SSL on HttpClient Noodle Manually

      Download and Install the Certificates from the Certificate Authority