Can somebody help us how to move ahead with this issue?
It seems like nobody is picking this up?
Kind Regards,
David
2016-10-26 13:43 GMT+02:00 David Dejaeghere :
> Does anybody have a clue on how to continue with this?
>
> Kind Regards,
>
> David
>
> 2016-10-24 10:10 GMT+02:00 David Dejaeghere
Does anybody have a clue on how to continue with this?
Kind Regards,
David
2016-10-24 10:10 GMT+02:00 David Dejaeghere :
> These are both the subjects for the old and new root ca cert.
>
> Subject: "CN=tokio-PAPRIKA-CA,DC=tokio,DC=local"
> Subject Public Key Info:
>
These are both the subjects for the old and new root ca cert.
Subject: "CN=tokio-PAPRIKA-CA,DC=tokio,DC=local"
Subject Public Key Info:
Public Key Algorithm: PKCS #1 RSA Encryption
RSA Public Key:
Modulus:
d5:51:19:a0:7e:2
Hi,
Can you give an example of what's different between the two subjects?
On Sun, Oct 23, 2016 at 9:03 AM, David Dejaeghere <
david.dejaegh...@gmail.com> wrote:
> Does somebody have an idea how to replace our certificates when the new
> ROOT ca certificate has a different subject?
> The UI is do
Does somebody have an idea how to replace our certificates when the new
ROOT ca certificate has a different subject?
The UI is down because of this.
2016-10-19 11:42 GMT+02:00 David Dejaeghere :
> Hello,
>
> When installing FreeIPA we used the CA from our Windows servers.
> This one recently expi
Hello,
When installing FreeIPA we used the CA from our Windows servers.
This one recently expired and we created a new one. It seems that the new
root CA has another subject name and this seems to be an issue when we want
to install new certs on our FreeIPA hosts.
ipa-cacert-manage install certn
