Figured it out! some special characters within the certificate body itself were not correctly encoded.
In the end, all special characters, as well as all line breaks should be encoded to reflect the exact certificate output and format. Will look at improving the doc available out there as this isn't crystal clear. ________________________________ From: Patrick W. <war...@hotmail.com> Sent: Monday, September 5, 2016 4:50 PM To: dev@cloudstack.apache.org Subject: Re: api uploadsslcert encoding issue I'm using 4.5.2 Yes you are right, I saw this issue: https://issues.apache.org/jira/browse/CLOUDSTACK-6864 but it was resolved in 4.4 Moreover I've tried the double encoding trick. ________________________________ From: Will Stevens <williamstev...@gmail.com> Sent: Monday, September 5, 2016 4:42 PM To: dev@cloudstack.apache.org Subject: Re: api uploadsslcert encoding issue What acs version are you using? I believe there was a problem with double encoding in some older releases. Maybe someone else can weigh in who knows for sure. On Sep 5, 2016 10:27 AM, "Patrick W." <war...@hotmail.com> wrote: > Has someone managed to upload a certificate, its chain and its key in a > single call, using the uploadsslcert API command? > > I've done attempts with cloudmonkey, in python, etc. tried all possible > formatting and encoding combinations but I always get errors > > - Expected X509 certificate. Failed due to String index out of range: > - Error parsing certificate data Invalid certificate format. Expected X509 > certificate > - Error parsing certificate data Invalid Certificate format. Failed due to > problem parsing cert: java.security.cert.CertificateException: > java.io.IOException: corrupted stream - out of bounds length found > > Has anybody succeeded with this? if yes, I'd be interested to reuse the > exact same approach. > > thanks! >
