Daan,
the new certificate and key are stored in datab
ase, and imported int
o realhostip.keystore
if t
he certificate is u
ploaded together with a key.
2016年2月17日星期三，Daan Hoogland 写道：
> H,
>
> If I upload a new certificate from the infrastructure tab, the timestamp of
> the certificates in the
Both work but the certificate never gets installed in the cpvm, it gets
loaded in memory directly through the command. thanks.
On Wed, Feb 17, 2016 at 7:01 PM, Remi Bergsma
wrote:
> Hi Daan,
>
> Did you try the api call instead of the UI? I believe the UI has a bug (it
> filters the private key
H,
If I upload a new certificate from the infrastructure tab, the timestamp of
the certificates in the consoleproxy in /usr/local/cloud/systemvm/certs
stay the same, even after destroying teh cpvm. Am I doing something wrong
or expecting the wrong thing to happen?
thanks,
--
Daan
Hi Daan,
Did you try the api call instead of the UI? I believe the UI has a bug (it
filters the private key and it doesn't appear in the db). API call worked for
me.
Regards, Remi
Sent from my iPhone
> On 17 Feb 2016, at 18:52, Daan Hoogland wrote:
>
> forgot to mention: version 4.7.1 I d
forgot to mention: version 4.7.1 I don't think that matters but still.
On Wed, Feb 17, 2016 at 2:19 PM, Daan Hoogland
wrote:
> H,
>
> If I upload a new certificate from the infrastructure tab, the timestamp
> of the certificates in the consoleproxy in /usr/local/cloud/systemvm/certs
> stay the s
