SLS - SCM GW Auth#44967
Conversation
🤖 AI-Powered Code Review AvailableYou can leverage AI-powered code review to assist with this PR! Available Commands:
|
Coverage Report
|
||||||||||||||||||||||||||||||
|
🤖 Analysis started. Please wait for results... |
🤖 AI Review DisclaimerThis review was generated by an AI-powered tool and may contain inaccuracies. Please be advised, and we extend our sincere apologies for any inconvenience this may cause. |
marketplace-ai-reviewer
left a comment
There was a problem hiding this comment.
Hi there, thanks for your updates to the Cortex Data Lake integration! I've left a few suggestions to help polish the code and documentation. Specifically, please improve the exception handling to preserve error context, ensure all deprecated OProxy parameters are fully hidden in the YAML configuration, and make a few minor metadata and release note styling tweaks. Thanks again for your hard work on this!
Additionally, please address the following file-level notes:
Packs/CortexDataLake/Integrations/CortexDataLake/CortexDataLake.yml: The PR description states that OProxy authentication is deprecated. Whilehidden: truewas added tocredentials_refresh_token, the other OProxy-related parameters (credentials_reg_idandcredentials_auth_key) remain visible. Consider hiding them as well if they are no longer used.Packs/CortexDataLake/Integrations/CortexDataLake/CortexDataLake_description.md: Move the## Overviewsection and version-compatibility statement to the README.Packs/CortexDataLake/pack_metadata.json: - Theurlfield should be updated tohttps://www.paloaltonetworks.com/cortex.- Please add the vendor name (e.g.,
Palo Alto Networks) to thekeywordsarray. - Please add
"marketplacev2"to themarketplacesarray.
@kamalq97, @TheL0L please review and approve the results generated by the AI Reviewer by responding 👍 on this comment.
This comment has been minimized.
This comment has been minimized.
|
Validate summary Verdict: PR can be force merged from validate perspective? ✅ |
🔍 AI Triage Report AvailableAn automated triage report has been generated for this pipeline. Status: 📋 Triage Report
|
julieschwartz18
left a comment
There was a problem hiding this comment.
@TheL0L Doc review complete, minor edits. Please check the comments. In the meantime, adding the label docs-approved
| 1. In the War Room, run the command `!GetLicenseID` to get the `license ID`. | ||
| 2. Go to __Settings__ > __ABOUT__ > __License__ to get the `Customer Name`. | ||
| 3. Go to the [HUB](https://apps.paloaltonetworks.com/apps) and login using your **Palo Alto Networks** credentials. | ||
| 3. Go to the [HUB](https://apps.paloaltonetworks.com/apps) and login using your **Palo Alto Networks** credentials. |
There was a problem hiding this comment.
| 3. Go to the [HUB](https://apps.paloaltonetworks.com/apps) and login using your **Palo Alto Networks** credentials. | |
| 3. Go to the [HUB](https://apps.paloaltonetworks.com/apps) and log in using your Palo Alto Networks credentials. |
| 8. Click __Add instance__ to create and configure a new integration instance. | ||
| * __Name__: A textual name for the integration instance. | ||
| * __Authentication Token__: From the authentication process | ||
| * __Registration ID__: From the authentication process |
There was a problem hiding this comment.
| * __Registration ID__: From the authentication process | |
| * __Registration ID__: From the authentication process. |
| * __Authentication Token__: From the authentication process | ||
| * __Registration ID__: From the authentication process | ||
| * The token retrieval URL is inferred based on the tenant's FedRAMP status unless explicitly specified in the __Registration ID__ parameter in the format `REGISTRATION_ID@URL`. | ||
| * __Encryption Key__: From the authentication process |
There was a problem hiding this comment.
| * __Encryption Key__: From the authentication process | |
| * __Encryption Key__: From the authentication process. |
| * __Registration ID__: From the authentication process | ||
| * The token retrieval URL is inferred based on the tenant's FedRAMP status unless explicitly specified in the __Registration ID__ parameter in the format `REGISTRATION_ID@URL`. | ||
| * __Encryption Key__: From the authentication process | ||
| * __Client Secret__: From the authentication process |
There was a problem hiding this comment.
| * __Client Secret__: From the authentication process | |
| * __Client Secret__: From the authentication process. |
| * The token retrieval URL is inferred based on the tenant's FedRAMP status unless explicitly specified in the __Registration ID__ parameter in the format `REGISTRATION_ID@URL`. | ||
| * __Encryption Key__: From the authentication process | ||
| * __Client Secret__: From the authentication process | ||
| * __proxy__: Use system proxy settings |
There was a problem hiding this comment.
| * __proxy__: Use system proxy settings | |
| * __proxy__: Use system proxy settings. |
| * __Client Secret__: From the authentication process | ||
| * __proxy__: Use system proxy settings | ||
| * __insecure__: Trust any certificate (not secure) | ||
| * __Fetch incidents__: Whether to fetch incidents or not |
There was a problem hiding this comment.
| * __Fetch incidents__: Whether to fetch incidents or not | |
| * __Fetch incidents__: Whether to fetch incidents. |
| * __proxy__: Use system proxy settings | ||
| * __insecure__: Trust any certificate (not secure) | ||
| * __Fetch incidents__: Whether to fetch incidents or not | ||
| * __first_fetch_timestamp__: First fetch time (<number> <time unit>, e.g., 12 hours, 7 days, 3 months, 1 year) |
There was a problem hiding this comment.
| * __first_fetch_timestamp__: First fetch time (<number> <time unit>, e.g., 12 hours, 7 days, 3 months, 1 year) | |
| * __first_fetch_timestamp__: First fetch time (<number> <time unit>, e.g., 12 hours, 7 days, 3 months, 1 year). |
| * __insecure__: Trust any certificate (not secure) | ||
| * __Fetch incidents__: Whether to fetch incidents or not | ||
| * __first_fetch_timestamp__: First fetch time (<number> <time unit>, e.g., 12 hours, 7 days, 3 months, 1 year) | ||
| * __Severity of events to fetch (Firewall)__: Select from all,Critical,High,Medium,Low,Informational,Unused |
There was a problem hiding this comment.
| * __Severity of events to fetch (Firewall)__: Select from all,Critical,High,Medium,Low,Informational,Unused | |
| * __Severity of events to fetch (Firewall)__: Select from all, Critical, High, Medium, Low, Informational, or Unused. |
| * __Fetch incidents__: Whether to fetch incidents or not | ||
| * __first_fetch_timestamp__: First fetch time (<number> <time unit>, e.g., 12 hours, 7 days, 3 months, 1 year) | ||
| * __Severity of events to fetch (Firewall)__: Select from all,Critical,High,Medium,Low,Informational,Unused | ||
| * __Subtype of events to fetch (Firewall)__: Select from all,attack,url,virus,spyware,vulnerability,file,scan,flood,packet,resource,data,url-content,wildfire,extpcap,wildfire-virus,http-hdr-insert,http-hdr,email-hdr,spyware-dns,spyware-wildfire-dns,spyware-wpc-dns,spyware-custom-dns,spyware-cloud-dns,spyware-raven,spyware-wildfire-raven,spyware-wpc-raven,wpc-virus,sctp |
There was a problem hiding this comment.
| * __Subtype of events to fetch (Firewall)__: Select from all,attack,url,virus,spyware,vulnerability,file,scan,flood,packet,resource,data,url-content,wildfire,extpcap,wildfire-virus,http-hdr-insert,http-hdr,email-hdr,spyware-dns,spyware-wildfire-dns,spyware-wpc-dns,spyware-custom-dns,spyware-cloud-dns,spyware-raven,spyware-wildfire-raven,spyware-wpc-raven,wpc-virus,sctp | |
| * __Subtype of events to fetch (Firewall)__: Select from all, attack, url, virus, spyware, vulnerability, file, scan, flood, packet, resource, data, url-content, wildfire, extpcap, wildfire-virus, http-hdr-insert, http-hdr, email-hdr, spyware-dns, spyware-wildfire-dns, spyware-wpc-dns, spyware-custom-dns, spyware-cloud-dns, spyware-raven, spyware-wildfire-raven, spyware-wpc-raven, or wpc-virus,sctp. |
| 3. After that every 60 minutes. | ||
|
|
||
| If you wish to try authenticating again, run the 'cdl-reset-authentication-timeout' command and retry. No newline at end of file | ||
| If you wish to try authenticating again, run the 'cdl-reset-authentication-timeout' command and retry. |
There was a problem hiding this comment.
| If you wish to try authenticating again, run the 'cdl-reset-authentication-timeout' command and retry. | |
| To try authenticating again, run the 'cdl-reset-authentication-timeout' command and retry. |
Related Issues
fixes: CIAC-17092
Description
Implemented SCM GW authentication as a replacement for the deprecated OProxy authentication.