As long as the entry in the database contains real line breaking you should be 
fine.  I’m not sure when the process to generate the keystore outside of the 
API is triggered, but it will very obviously bomb if it has troubles with the 
key.

If you upload the cert again with the encoded line breaks but the same name and 
domain suffix it should trample over the DB entry and rebuild the keystore.


On May 14, 2014, at 9:17 AM, Michael Phillips <mphilli7...@hotmail.com> wrote:

> So I did not include the "%0D", but went back and added the line breaks in 
> the database manually. You think that's enough or do I need to delete and 
> re-upload with the %0D?
> 
>> Subject: Re: Intermediate CA
>> From: david.bie...@appcore.com
>> Date: Tue, 13 May 2014 07:34:46 -0500
>> To: users@cloudstack.apache.org
>> 
>> Looks a little akward in the email, but all of it goes into a single URL 
>> encoded like.  %20 for space, %0D for line breaks.
>> 
>> On May 13, 2014, at 12:27 AM, Michael Phillips <mphilli7...@hotmail.com> 
>> wrote:
>> 
>>> David, excellent example. 
>>> So all you needed to do was to replace the spaces in the cert with "%20", 
>>> and do nothing for the line breaks?
>>> 
>>>> From: david.bie...@appcore.com
>>>> Subject: Re: Intermediate CA
>>>> Date: Mon, 12 May 2014 12:18:39 -0500
>>>> To: users@cloudstack.apache.org
>>>> 
>>>> There is still no way to do it in the GUI.  That method works well.  Or 
>>>> you can do it in cloud monkey like this.
>>>> 
>>>> http://permalink.gmane.org/gmane.comp.apache.cloudstack.user/11711
>>>> 
>>>> 
>>>> On May 7, 2014, at 9:13 PM, Michael Phillips <mphilli7...@hotmail.com> 
>>>> wrote:
>>>> 
>>>>> All,
>>>>> Is it still necessary to follow this guide 
>>>>> http://www.chipchilders.com/blog/2013/1/2/undocumented-feature-using-certificate-chains-in-cloudstack.html
>>>>>  to import an SSL cert with an intermediate cert or can it be done direct 
>>>>> via the GUI?                                         
>>>> 
>>>                                       
>> 
>                                         

Reply via email to