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
After the work related to #7153 (comment) we no longer need a client cert by default to connect to a TLS enabled universe. We need to simplify our custom certs flow to make the client cert part optional. When the user creates an onprem universe that points to a custom cert and checks "client to node encryption in transit", we should not fail the operation if the custom cert does not contain a client cert.
The text was updated successfully, but these errors were encountered:
No changes are needed from backend too.
Verified the code flow and client certificates are considered optional everywhere.
Also verified by creating on-prem universe with client to node encryption enabled using custom certificates (without client cert). Was able to successfully create and connect to the universe.
After the work related to #7153 (comment) we no longer need a client cert by default to connect to a TLS enabled universe. We need to simplify our custom certs flow to make the client cert part optional. When the user creates an onprem universe that points to a custom cert and checks "client to node encryption in transit", we should not fail the operation if the custom cert does not contain a client cert.
The text was updated successfully, but these errors were encountered: