Hi All,
I came across this thread when troubleshooting a similar problem, and
wanted to drop in the solution we came up with for posterity:
1) If you're dealing with an API, and the API comes back with an "incorrect
padding" error while parsing an SSL Cert, it usually means that the
formatting go
On Sun, 29 Jan 2017 at 00:00 James Beedy wrote:
> Ok, progress. I've encoded my cert and key to base64 strings and specified
> them in my haproxy config, and seem to be getting past the padding error.
> My issue now, is that I am not seeing the cert/key in /etc/ssl/private on
> the haproxy host o
Ok, progress. I've encoded my cert and key to base64 strings and specified
them in my haproxy config, and seem to be getting past the padding error.
My issue now, is that I am not seeing the cert/key in /etc/ssl/private on
the haproxy host once deployed. I'm thinking specifying the ssl cert/key
wil
I'm having issues with padding when trying to specify key/cert as config
options for Haproxy, and have experienced the same issue in the past, when
trying to specify key/cert for the Openstack charms. Could someone give an
example of what the correct padding of a base64 encoded ssl cert might look
