Allow TLS connections (not client authentication)

[devployment]

Looks like the input does not connect to TLS enabled endpoints.

In my case the connection would need to established with something like this

factory.Ssl.Enabled = true;
factory.Ssl.AcceptablePolicyErrors = SslPolicyErrors.RemoteCertificateNameMismatch;

I would suggest to make these two settings options of the input configuration.

If accepted, I can create a PR related to this.

[nblumhardt]

Hi! Thanks for the note. Adding an "Enable SSL" parameter would be great 👍

I'm unsure about the second option; these kinds of settings often undo the protection offered by SSL. Adding a hosts file entry on the client machine to get the certificate name and domain name lined up, or fixing the certificate binding on the server, seem like better options for this. What do you think?

[devployment]

Adding a hosts file entry on the client machine to get the certificate name and domain name lined up, or fixing the certificate binding on the server, seem like better options for this. What do you think?

Couldn't agree more. But to me it's currently unclear what leads to the exception in our current setup. We have a mixture of setups. Some queue hosts are secured by self signed certificates, others by Let's Encrypt certificates.

Currently in the process of getting to the root of the problem. Adding such an option is generally not the best way. But could help in scenarios like the current one. ;P Anyway, just added the package with the changes to our private feed. If nothing blows I'll create the PR for the general setting.