You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: development-docs/systemtests/io.strimzi.systemtest.operators.user.UserST.md
+5-5Lines changed: 5 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -97,7 +97,7 @@
97
97
*[user-operator](labels/user-operator.md)
98
98
99
99
100
-
## testTlsValidityDaysWithForceRenewal
100
+
## testTlsValidityDays
101
101
102
102
**Description:** Verifies functionality of the mTLS `validityDays` and `renewalDays` configured inside each KafkaUser.
103
103
@@ -106,12 +106,12 @@
106
106
| Step | Action | Result |
107
107
| - | - | - |
108
108
| 1. | Create `KafkaTopic` to which we will send (and from which we will receive) messages - created in existing Kafka cluster. |`KafkaTopic` is created. |
109
-
| 2. | Create `KafkaUser` with TLS authentication; together with default`validityDays`(200 days) and `renewalDays`(20 days) - configured in User operator. |`KafkaUser` is created with defaults. |
109
+
| 2. | Create `KafkaUser` with TLS authentication; without configuring the`validityDays` and `renewalDays`- values from User Operator are taken. |`KafkaUser` is created with values from User Operator. |
110
110
| 3. | Obtain the `KafkaUser`'s `Secret` and check validity period of the user certificate. | Validity period should be default - 200 days. |
111
111
| 4. | Do message transmission to verify, that we are able to connect to Kafka cluster with the TLS `KafkaUser`. | Messages are successfully sent and received. |
112
-
| 5. | Change the `validityDays` and `renewalDays` in the `KafkaUser``.spec.authentication` to 60 and 10. | The `validityDays` and `renewalDays` should be changed in the `KafkaUser`. |
113
-
| 6. | Because we changed the `validityDays` and `renewalDays`, we need to force renew the certificate using the `strimzi.io/force-renew=true` annotation| The user certificate was renewed. |
114
-
| 7. | Obtain the `KafkaUser`'s `Secret` again and check the validity period of the user certificate. | Validity period should be 60 days. |
112
+
| 5. | Change the `validityDays` and `renewalDays` in the `KafkaUser``.spec.authentication` to 40 and 20. | The `validityDays` and `renewalDays` should be changed in the `KafkaUser`. |
113
+
| 6. | Because of the change of `validityDays` and `renewalDays` (and because of the values inside), the certificate will be renewed| The user certificate was renewed. |
114
+
| 7. | Obtain the `KafkaUser`'s `Secret` again and check the validity period of the user certificate. | Validity period should be 40 days. |
115
115
| 8. | Do message transmission again to verify, that we are able to connect to Kafka cluster with the new user's certificate. | Messages are successfully sent and received using new certificate. |
Copy file name to clipboardExpand all lines: documentation/modules/appendix_crds.adoc
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -2686,10 +2686,10 @@ It must have the value `tls` for the type `KafkaUserTlsClientAuthentication`.
2686
2686
|Must be `tls`.
2687
2687
|validityDays
2688
2688
|integer
2689
-
|Number of days for which the user certificate should be valid. If not configured, Clients CA configuration is used.
2689
+
|Number of days for which the user certificate should be valid. It has to be configured together with `renewalDays`, or none of them should be configured.The number should be bigger than 0 and than `renewalDays`.If not configured, Clients CA configuration is used.
2690
2690
|renewalDays
2691
2691
|integer
2692
-
|Number of days before certificate expiration when the user certificate should be renewed. If not configured, Clients CA configuration is used.
2692
+
|Number of days before certificate expiration when the user certificate should be renewed. It has to be configured together with `validityDays`, or none of them should be configured.The number should be bigger than 0 and smaller than `validityDays`.If not configured, Clients CA configuration is used.
Copy file name to clipboardExpand all lines: packaging/helm-charts/helm3/strimzi-kafka-operator/crds/044-Crd-kafkauser.yaml
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -84,7 +84,7 @@ spec:
84
84
renewalDays:
85
85
type: integer
86
86
minimum: 1
87
-
description: "Number of days before certificate expiration when the user certificate should be renewed. If not configured, Clients CA configuration is used."
87
+
description: "Number of days before certificate expiration when the user certificate should be renewed. It has to be configured together with `validityDays`, or none of them should be configured.The number should be bigger than 0 and smaller than `validityDays`.If not configured, Clients CA configuration is used."
88
88
type:
89
89
type: string
90
90
enum:
@@ -95,7 +95,7 @@ spec:
95
95
validityDays:
96
96
type: integer
97
97
minimum: 1
98
-
description: "Number of days for which the user certificate should be valid. If not configured, Clients CA configuration is used."
98
+
description: "Number of days for which the user certificate should be valid. It has to be configured together with `renewalDays`, or none of them should be configured.The number should be bigger than 0 and than `renewalDays`.If not configured, Clients CA configuration is used."
99
99
required:
100
100
- type
101
101
description: "Authentication mechanism enabled for this Kafka user. The supported authentication mechanisms are `scram-sha-512`, `tls`, and `tls-external`. \n\n* `scram-sha-512` generates a secret with SASL SCRAM-SHA-512 credentials.\n* `tls` generates a secret with user certificate for mutual TLS authentication.\n* `tls-external` does not generate a user certificate. But prepares the user for using mutual TLS authentication using a user certificate generated outside the User Operator.\n ACLs and quotas set for this user are configured in the `CN=<username>` format.\n\nAuthentication is optional. If authentication is not configured, no credentials are generated. ACLs and quotas set for the user are configured in the `<username>` format suitable for SASL authentication."
Copy file name to clipboardExpand all lines: packaging/install/cluster-operator/044-Crd-kafkauser.yaml
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -83,7 +83,7 @@ spec:
83
83
renewalDays:
84
84
type: integer
85
85
minimum: 1
86
-
description: "Number of days before certificate expiration when the user certificate should be renewed. If not configured, Clients CA configuration is used."
86
+
description: "Number of days before certificate expiration when the user certificate should be renewed. It has to be configured together with `validityDays`, or none of them should be configured.The number should be bigger than 0 and smaller than `validityDays`.If not configured, Clients CA configuration is used."
87
87
type:
88
88
type: string
89
89
enum:
@@ -94,7 +94,7 @@ spec:
94
94
validityDays:
95
95
type: integer
96
96
minimum: 1
97
-
description: "Number of days for which the user certificate should be valid. If not configured, Clients CA configuration is used."
97
+
description: "Number of days for which the user certificate should be valid. It has to be configured together with `renewalDays`, or none of them should be configured.The number should be bigger than 0 and than `renewalDays`.If not configured, Clients CA configuration is used."
98
98
required:
99
99
- type
100
100
description: "Authentication mechanism enabled for this Kafka user. The supported authentication mechanisms are `scram-sha-512`, `tls`, and `tls-external`. \n\n* `scram-sha-512` generates a secret with SASL SCRAM-SHA-512 credentials.\n* `tls` generates a secret with user certificate for mutual TLS authentication.\n* `tls-external` does not generate a user certificate. But prepares the user for using mutual TLS authentication using a user certificate generated outside the User Operator.\n ACLs and quotas set for this user are configured in the `CN=<username>` format.\n\nAuthentication is optional. If authentication is not configured, no credentials are generated. ACLs and quotas set for the user are configured in the `<username>` format suitable for SASL authentication."
Copy file name to clipboardExpand all lines: packaging/install/user-operator/04-Crd-kafkauser.yaml
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -83,7 +83,7 @@ spec:
83
83
renewalDays:
84
84
type: integer
85
85
minimum: 1
86
-
description: "Number of days before certificate expiration when the user certificate should be renewed. If not configured, Clients CA configuration is used."
86
+
description: "Number of days before certificate expiration when the user certificate should be renewed. It has to be configured together with `validityDays`, or none of them should be configured.The number should be bigger than 0 and smaller than `validityDays`.If not configured, Clients CA configuration is used."
87
87
type:
88
88
type: string
89
89
enum:
@@ -94,7 +94,7 @@ spec:
94
94
validityDays:
95
95
type: integer
96
96
minimum: 1
97
-
description: "Number of days for which the user certificate should be valid. If not configured, Clients CA configuration is used."
97
+
description: "Number of days for which the user certificate should be valid. It has to be configured together with `renewalDays`, or none of them should be configured.The number should be bigger than 0 and than `renewalDays`.If not configured, Clients CA configuration is used."
98
98
required:
99
99
- type
100
100
description: "Authentication mechanism enabled for this Kafka user. The supported authentication mechanisms are `scram-sha-512`, `tls`, and `tls-external`. \n\n* `scram-sha-512` generates a secret with SASL SCRAM-SHA-512 credentials.\n* `tls` generates a secret with user certificate for mutual TLS authentication.\n* `tls-external` does not generate a user certificate. But prepares the user for using mutual TLS authentication using a user certificate generated outside the User Operator.\n ACLs and quotas set for this user are configured in the `CN=<username>` format.\n\nAuthentication is optional. If authentication is not configured, no credentials are generated. ACLs and quotas set for the user are configured in the `<username>` format suitable for SASL authentication."
description = @Desc("Verifies functionality of the mTLS `validityDays` and `renewalDays` configured inside each KafkaUser."),
573
573
steps = {
574
574
@Step(value = "Create `KafkaTopic` to which we will send (and from which we will receive) messages - created in existing Kafka cluster.", expected = "`KafkaTopic` is created."),
575
-
@Step(value = "Create `KafkaUser` with TLS authentication; together with default `validityDays` (200 days) and `renewalDays` (20 days) - configured in User operator.", expected = "`KafkaUser` is created with defaults."),
575
+
@Step(value = "Create `KafkaUser` with TLS authentication; without configuring the `validityDays` and `renewalDays` - values from User Operator are taken.", expected = "`KafkaUser` is created with values from User Operator."),
576
576
@Step(value = "Obtain the `KafkaUser`'s `Secret` and check validity period of the user certificate.", expected = "Validity period should be default - 200 days."),
577
577
@Step(value = "Do message transmission to verify, that we are able to connect to Kafka cluster with the TLS `KafkaUser`.", expected = "Messages are successfully sent and received."),
578
-
@Step(value = "Change the `validityDays` and `renewalDays` in the `KafkaUser` `.spec.authentication` to 60 and 10.", expected = "The `validityDays` and `renewalDays` should be changed in the `KafkaUser`."),
579
-
@Step(value = "Because we changed the `validityDays` and `renewalDays`, we need to force renew the certificate using the `strimzi.io/force-renew=true` annotation",
580
-
expected = "The user certificate was renewed."),
581
-
@Step(value = "Obtain the `KafkaUser`'s `Secret` again and check the validity period of the user certificate.", expected = "Validity period should be 60 days."),
578
+
@Step(value = "Change the `validityDays` and `renewalDays` in the `KafkaUser` `.spec.authentication` to 40 and 20.", expected = "The `validityDays` and `renewalDays` should be changed in the `KafkaUser`."),
579
+
@Step(value = "Because of the change of `validityDays` and `renewalDays` (and because of the values inside), the certificate will be renewed", expected = "The user certificate was renewed."),
580
+
@Step(value = "Obtain the `KafkaUser`'s `Secret` again and check the validity period of the user certificate.", expected = "Validity period should be 40 days."),
582
581
@Step(value = "Do message transmission again to verify, that we are able to connect to Kafka cluster with the new user's certificate.", expected = "Messages are successfully sent and received using new certificate."),
// check that notBefore and notAfter contains really the default value of validityDays
603
-
assertThat("validity period of the certificate has incorrect value", KafkaUserUtils.getValidityDaysOfCertificate(userCertificate), is(defaultValidityDays));
602
+
assertThat("validity period of the certificate has incorrect value", KafkaUserUtils.getValidityDaysOfCertificate(userCertificate), is(caValidityDays));
604
603
605
604
LOGGER.info("Produce and consume messages before changing the validity - in order to see that everything works as expected.");
0 commit comments