Skip to content

Refactor Ca class to handle certificate-level validity #12765

@im-konge

Description

@im-konge

In #12658 the possibility for specifying validityDays and renewalDays for mTLS KafkaUser was added, however there was a comment about the approach which was used there - #12658 (comment).
The comment is mainly about passing the KafkaUser's validityDays and renewalDays to the ClientsCa (or Ca) constructor, which actually should be validity/renewal of the Clients CA. Instead of doing this, we should refactor the Ca class to have the validity/renewal of the Clients CA and pass the (in this case) KafkaUser's validity/renewal as part of the "generate certificate" method.

So the handling which validity/renewal values should be used will be moved to the "generate certificate" method.

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No fields configured for Task.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions