Change VERIFY_SSL default setting with specified cert file #44
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
gronka
approved these changes
May 14, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
social-auth-core version 4.6.0 updated their request() function which broke our method of telling the Requests library to trust other certificates when connecting to UIT+. The update blocks our ability to set the verify= argument. The tricky part is that DEFAULT_CA_FILE can change since it typically points to a python module, so setting SOCIAL_AUTH_VERIFY_SSL isn't a good option here.
This change overrides the VERIFY_SSL setting, and this should last longer in future code changes to social-auth. This also works with older versions of social-auth, like what is in our local dev environments.
CHW-702