Skip to content

Ipquality ip fix#42944

Open
content-bot wants to merge 1 commit intomasterfrom
contrib/RamboV_ipquality_ip_fix
Open

Ipquality ip fix#42944
content-bot wants to merge 1 commit intomasterfrom
contrib/RamboV_ipquality_ip_fix

Conversation

@content-bot
Copy link
Contributor

Original External PR

external pull request

Contributor

@RamboV

Summary
The IPQualityScore integration in Cortex Marketplace is currently failing with an “Invalid or unauthorized key” error during execution.

Issue Details
Although the same IPQualityScore API key works successfully when tested directly via Postman, the integration returns an authorization error when executed within Cortex XSOAR. This indicates a mismatch between how the API key is validated in the integration versus direct API usage.

Impact
Customers attempting to use the IPQualityScore integration are unable to successfully authenticate, preventing threat intelligence enrichment and disrupting workflows that depend on this integration.

Changes / Investigation
This PR updates the integration configuration and/or request handling to ensure the API key is passed and validated correctly by the IPQualityScore service, aligning Cortex behavior with successful direct API calls.

Related Marketplace Page
https://cortex.marketplace.pan.dev/marketplace/details/IPQualityScore/

fixes: https://jira-dc-proxy.xdr.pan.local/browse/CIAC-15590

* fixed ip email and url command

* Added Release Notes

* Add URL fixes to IPQualityScore integration

Updated the IPQualityScore integration with URL fixes.

* reverting the release version

* Generated the release notes

* modified the metadata version to 1.0.15 as per the suggestion

---------

Co-authored-by: siddharthamudigondamudigonda <siddharth_mudigonda@discovery.com>
@content-bot content-bot added Contribution Thank you! Contributions are always welcome! docs-approved Partner Contribution Form Filled Whether contribution form filled or not. pending-contributor The PR is pending the response of its creator Partner Support Level Indicates that the contribution is for Partner supported pack Internal PR Partner-Approved ready-for-pipeline-running Whether the pr is ready for running the whole pipeline, including testing on SAAS machines labels Feb 5, 2026
@content-bot
Copy link
Contributor Author

🤖 AI-Powered Code Review Available

Hi @MosheEichler, you can leverage AI-powered code review to assist with this PR!

Available Commands:

  • @content-bot start review - Initiate a full AI code review
  • @content-bot re-review - Incremental review for new commits

@content-bot
Copy link
Contributor Author

🤖 AI-Powered Code Review Available

You can leverage AI-powered code review to assist with this PR!

Available Commands:

  • @content-bot start review - Initiate a full AI code review
  • @content-bot re-review - Incremental review for new commits

@github-actions
Copy link

github-actions bot commented Feb 5, 2026

Coverage

Coverage Report
FileStmtsMissCoverMissing
Packs/IPQualityScore/Integrations/IPQualityScore
   IPQualityScore.py1175354%31, 34–43, 47–49, 51, 64, 68, 112, 114, 154, 156, 187, 190–192, 194, 196–199, 201–203, 205–210, 214–219, 225–230, 234–235
TOTAL1175354% 

Tests Skipped Failures Errors Time
3 0 💤 0 ❌ 0 🔥 2.914s ⏱️

@content-bot
Copy link
Contributor Author

Validate summary
The following errors were reported as warnings: DO106.
The following errors were thrown as a part of this pr: ST111.
The following errors cannot be ignored: ST111.
If the AG100 validation in the pre-commit GitHub Action fails, the pull request cannot be force-merged.
The following errors don't run as part of the nightly flow and therefore can be force merged: ST111.

Verdict: PR can be force merged from validate perspective? ✅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Contribution Form Filled Whether contribution form filled or not. Contribution Thank you! Contributions are always welcome! docs-approved Internal PR Partner Support Level Indicates that the contribution is for Partner supported pack Partner Partner-Approved pending-contributor The PR is pending the response of its creator ready-for-pipeline-running Whether the pr is ready for running the whole pipeline, including testing on SAAS machines skip-ai-review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants