Fix exposed connector URL in error message

[rithin-pullela-aws]

Description

This pull request addresses a security concern where user input, in this case specifically the connector URL was being exposed in error messages. Exposing such information can inadvertently leak sensitive data and does not align with security best practices.

Fix:
Updated the error handling logic to avoid printing the connector URL in error messages, thereby preventing potential information disclosure.

Related Issues

Resolves #[Issue number to be closed when this PR is merged]

Check List

• New functionality includes testing.
• New functionality has been documented.
• API changes companion pull request created.
• Commits are signed per the DCO using --signoff.
• Public documentation issue/PR created.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

[mingshl]

this exception message is throwing when user try to create a model using the connectors, so we can hide the url to avoid exposing endpoint info to users, but please suggest either update the trusted endpoint in connectors or check the connector url. I think these suggestions would be helpful

[rithin-pullela-aws]

this exception message is throwing when user try to create a model using the connectors, so we can hide the url to avoid exposing endpoint info to users, but please suggest either update the trusted endpoint in connectors or check the connector url. I think these suggestions would be helpful

@mingshl, this error is thrown when we try to create the connector. So I believe the error message is good enough. Connector URL is not matching the trusted connector endpoint regex

[rithin-pullela-aws]

I created an issue #3954 to expand this solution to other places where we expose use input.

[mingshl]

this exception message is throwing when user try to create a model using the connectors, so we can hide the url to avoid exposing endpoint info to users, but please suggest either update the trusted endpoint in connectors or check the connector url. I think these suggestions would be helpful

@mingshl, this error is thrown when we try to create the connector. So I believe the error message is good enough. Connector URL is not matching the trusted connector endpoint regex

then you can suggest to update the trusted endpoint in the cluster setting

[dhrubo-os]

this exception message is throwing when user try to create a model using the connectors, so we can hide the url to avoid exposing endpoint info to users, but please suggest either update the trusted endpoint in connectors or check the connector url. I think these suggestions would be helpful

@mingshl, this error is thrown when we try to create the connector. So I believe the error message is good enough. Connector URL is not matching the trusted connector endpoint regex

then you can suggest to update the trusted endpoint in the cluster setting

I think based on the input users can decide if they need to add trusted endpoint or not. What if they had some spelling mistake in their url?

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 80.60%. Comparing base (a894ff1) to head (44e3aaf).
Report is 3 commits behind head on main.

Additional details and impacted files

@@             Coverage Diff              @@
##               main    #3953      +/-   ##
============================================
- Coverage     80.61%   80.60%   -0.02%     
+ Complexity     7945     7943       -2     
============================================
  Files           694      694              
  Lines         34872    34872              
  Branches       3885     3885              
============================================
- Hits          28113    28109       -4     
- Misses         5032     5033       +1     
- Partials       1727     1730       +3     

Flag	Coverage Δ
ml-commons	80.60% <100.00%> (-0.02%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.