enable server certificate vaildation #9#40
Merged
1 commit merged intoMay 13, 2026
Merged
Conversation
|
❌ The last analysis has failed. |
Vasia1101
approved these changes
May 11, 2026
Vasia1101
approved these changes
May 11, 2026
VladyslavSavchuk
approved these changes
May 12, 2026
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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.
JIRA
Code reviewers
Second Level Review
Summary of issue
SonarQube знайшов вразливість безпеки (Security Vulnerability) через примусово вимкнену валідацію SSL/TLS сертифікатів при HTTP-запитах до зовнішніх ресурсів.
Summary of change
ServerCertificateCustomValidationCallback = trueу файліWebParsingUtils.cs(тепер використовується стандартна системна перевірка сертифікатів).TrustServerCertificate=TrueнаFalseвappsettings.IntegrationTests.json.Closes #9
Testing approach
Локальний запуск (F5). Перевірено, що бекенд успішно стартує, Swagger доступний на порту 5001 (HTTPS), а звернення до зовнішніх API тепер вимагають валідного сертифіката. Білд проходить без помилок.
CHECK LIST