[Zscaler] Modified category blacklist #3548
Open
+4
−2
Conversation
This file contains 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
MohamedMerimi
changed the title
helene-nguyen
changed the title
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.
Hello,
I updated the script so that domains are added to "Custom URLs" instead of "URLs retaining parent category" in Zscaler.
Specifically:
In get_zscaler_blocked_domains, the script now reads the blocked domain list from the urls field instead of dbCategorizedUrls.
In send_to_zscaler, both creation and deletion events use "urls" in the payload instead of "dbCategorizedUrls".
These changes ensure that domains appear under "Custom URLs" within the chosen Zscaler category.
Proposed changes
Related issues
Checklist
Further comments