Improve user experience for cloud strict encrypt connector when configuring unsecured connection #16664
Labels
area/connectors
Connector related issues
connectors/source/mysql-strict-encrypt
connectors/source/postgres-strict-encrypt
from/connector-ops
needs-triage
team/destinations
Destinations team's backlog
type/enhancement
New feature or request
Tell us about the problem you're trying to solve
The strict encrypt postgres and mysql connectors correctly fail configuration check if the connection is effectively not guaranteed to be always encrypted (e.g with No Tunnel and with ssl set to "preferred").
Currently an error saying "Unsecured connection not allowed" is shown.
Improve user experience to reduce support calls from cloud customers.
Describe the solution you’d like
We can add a more informative message. Suggested: "If you do not have SSH tunneling set up, please use one of these SSL modes:….".
In addition, if spec UI allows we can apply form validation and mark setting as red, similarly to how a missing host or database name is handled:
This can provide visual guidance to users.
Need to see if spec allows creating a logic based on both tunnel and ssl setting.
Describe the alternative you’ve considered or used
A clear and concise description of any alternative solutions or features you've considered or are using today.
Additional context
Add any other context or screenshots about the feature request here.
Are you willing to submit a PR?
Remove this with your answer :-)
The text was updated successfully, but these errors were encountered: