Fix authenticate bug and add unverified context #13428
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
This PR introduces a new configuration parameter unverified_context, which determines whether an unverified SSL context should be used. By default, this parameter is set to False.
Purpose
When using custom certificates for the email server, prefect email functionality may fail due to certificate verification issues. To address this, the new unverified_context parameter allows users to initialize an unverified SSL context in such cases, facilitating successful email transmission.
Bug Fix
Additionally, this PR fixes a bug related to the handling of insecure email servers, ensuring we will authenticate in the case of having username and password.
Related PRs and issues in prefect_email repository
PR 81
Issue 13089
PR 70
Issue 13091
Example
Checklist
<link to issue>
"maintenance
,fix
,feature
,enhancement
,docs
.For documentation changes:
netlify.toml
for files that are removed or renamed.For new functions or classes in the Python SDK:
mkdocs.yml
navigation.