[GitHub] [pulsar] Jim-Lambert-Bose opened a new issue #4893: Go client: mTLS error returned for an expired broker cert is difficult to decipher.

[GitBox <gi...@apache.org>]

Jim-Lambert-Bose opened a new issue #4893: Go client: mTLS error returned for an expired broker cert is difficult to decipher.
URL: https://github.com/apache/pulsar/issues/4893
 
 
   **Describe the bug**
   Under mTLS, when the client cert contains an invalid pulsar broker cert the Go client returns: `ERROR | ClientImpl:179 | Checking/Getting Partition Metadata while creating producer with result == 5` which is impossible to decipher as an expired server cert error.
   
   **To Reproduce**
   1. Enable TLS and mTLS
   2. Start broker with expired cert
   3. connect via pulsar client and mTLS
   4. client returns error: `ERROR | ClientImpl:179 | Checking/Getting Partition Metadata while creating producer with result == 5`
   
   **Expected behavior**
   Go client should return something straightforward.  Perhaps: "pulsar broker cert is expired as of MM/DD/YYYY"

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services