Still need client certificate even when set authenticatePeer: no

Solution Verified - Updated -

Issue

I am deploying the AMQ Interconnect on ocp env, I followed [Deploying AMQ Interconnect on OpenShift Container Platform]
(https://access.redhat.com/documentation/en-us/red_hat_amq/7.3/html-single/deploying_amq_interconnect_on_openshift_container_platform/index)
and deployed amq-interconnect-1-tls-auth.yaml, but I found even set the authenticatePeer: no , looks like the server still need the client certificate, log as below:

2020-03-03 14:02:18.671505 +0000 SERVER (info) [C6] Accepted connection to 0.0.0.0:amqps from 10.129.0.1:41672
2020-03-03 14:02:19.165936 +0000 SERVER (info) [C6] Connection from 10.129.0.1:41672 (to 0.0.0.0:amqps) failed: amqp:connection:framing-error SSL Failure: error:140890C7:SSL routines:ssl3_get_client_certificate:peer did not return a certificate
listener {
    host: 0.0.0.0
    port: amqps
    sslProfile: service_tls
    authenticatePeer: no
    requireSsl: true
    saslMechanisms: EXTERNAL
}

Environment

  • Red Hat AMQ Interconnect 1.6.1

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content