identical CN after rotation and root CA in tls.crt

[delamart]

After experiencing a rotation of the service CA certificate in our OpenShift 4.8 cluster we had some issue with PKCS12 JAVA keystores and truststore. These issues are linked to multiple certificates using the same common name.

You could help avoid these issues with two changes to the operator:

1. generate a new root CA with a new common name rather than re-using the same common name
2. stop putting the root CA in the tls.crt. A trust chain should not include the root certificate.

Point 2 would help because, after rotation, a cross-signed root is added as an intermediate and this certificate also shares it's name with the new root certificate (as it should) but they both are included in the tls.crt secret. By removing the root and only including the intermediate (and leaf certificate) in tls.crt there would be no duplicate common names.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[openshift-bot]

Stale issues rot after 30d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle rotten
/remove-lifecycle stale

[openshift-bot]

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

[openshift-ci]

@openshift-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.

Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.