Skip to content

Fix/XSUP-66433/ManageEngine refresh token update#43753

Merged
MosheEichler merged 10 commits intomasterfrom
fix/XSUP-66433-manage-engine-refresh-token
Apr 12, 2026
Merged

Fix/XSUP-66433/ManageEngine refresh token update#43753
MosheEichler merged 10 commits intomasterfrom
fix/XSUP-66433-manage-engine-refresh-token

Conversation

@MosheEichler
Copy link
Copy Markdown
Contributor

status

  • In Progress
  • Ready
  • In Hold - (Reason for hold)

Related Issues

https://jira-dc.paloaltonetworks.com/browse/XSUP-66433

Description

Fix ManageEngine integration stopping log ingestion after a few days due to Zoho rotating refresh token not being updated.
Fixed an issue where in the get_events command defaulted start_date to now and end_date to now - 60s, making the time window inverted and returning no events when called without explicit dates.

Must have

  • Tests
  • Documentation

… start/end date defaults, fix debug logs

- Fix root cause of XSUP-66433: Zoho OAuth rotating refresh tokens were
  never updated in context. ctx.get('refresh_token') was always truthy so
  the new token from the API response was silently discarded. After Zoho
  invalidated the original token (within days), the integration stopped
  ingesting events while still appearing connected.
- Fix get_events() start_date/end_date fallback defaults being swapped,
  causing start > end when no dates provided (no events returned)
- Fix manage-engine-test command handler: change second 'if' to 'elif'
- Fix debug log: log len(events_page) instead of full event list
- Fix debug log typo: 'intervarl' -> 'interval'
@MosheEichler MosheEichler requested a review from DeanArbel March 31, 2026 12:08
@MosheEichler MosheEichler added release-notes-only Indicates that this pull request has ONLY release notes to review for documentation process ready-for-ai-review The PR is ready for reviewing the PR with the AI Reviewer. labels Mar 31, 2026
@content-bot
Copy link
Copy Markdown
Contributor

🤖 AI-Powered Code Review Available

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

Available Commands:

  • @marketplace-ai-reviewer start review - Initiate a full AI code review
  • @marketplace-ai-reviewer re-review - Incremental review for new commits

@marketplace-ai-reviewer marketplace-ai-reviewer removed the ready-for-ai-review The PR is ready for reviewing the PR with the AI Reviewer. label Mar 31, 2026
@marketplace-ai-reviewer
Copy link
Copy Markdown
Contributor

🤖 Analysis started. Please wait for results...

@github-actions
Copy link
Copy Markdown

github-actions bot commented Mar 31, 2026

Coverage

Coverage Report
FileStmtsMissCoverMissing
Packs/ManageEngine/Integrations/ManageEngineEventCollector
   ManageEngineEventCollector.py114793%110, 117–118, 171–172, 203, 233
TOTAL114793% 

Tests Skipped Failures Errors Time
18 0 💤 0 ❌ 0 🔥 2.261s ⏱️

@marketplace-ai-reviewer
Copy link
Copy Markdown
Contributor

🤖 AI Review Disclaimer

This 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.

Copy link
Copy Markdown
Contributor

@marketplace-ai-reviewer marketplace-ai-reviewer left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi! Thanks for your contribution with the ManageEngine pack. I took a look at the changes and noticed a couple of quick fixes needed in the pack metadata. Specifically, please ensure the vendor name is added to the keywords list and include the mandatory created key. Let me know if you have any questions!

Additionally, please address the following file-level notes:

  • Packs/ManageEngine/pack_metadata.json: - Missing vendor name in keywords.
  • Missing mandatory key created.

@DeanArbel please review and approve the results generated by the AI Reviewer by responding 👍 on this comment.

@MosheEichler MosheEichler marked this pull request as ready for review March 31, 2026 12:34
@MosheEichler MosheEichler added the ready-for-pipeline-running Whether the pr is ready for running the whole pipeline, including testing on SAAS machines label Mar 31, 2026
@MosheEichler MosheEichler enabled auto-merge (squash) March 31, 2026 12:35
@MosheEichler MosheEichler disabled auto-merge March 31, 2026 14:36
MosheEichler and others added 2 commits April 12, 2026 11:27
Co-authored-by: Richard Bluestone <53567272+richardbluestone@users.noreply.github.com>
@MosheEichler MosheEichler enabled auto-merge (squash) April 12, 2026 08:27
@content-bot
Copy link
Copy Markdown
Contributor

Validate summary
The following errors were thrown as a part of this pr: .
If the AG100 validation in the pre-commit GitHub Action fails, the pull request cannot be force-merged.

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

@MosheEichler MosheEichler merged commit 2cf9231 into master Apr 12, 2026
20 of 21 checks passed
@MosheEichler MosheEichler deleted the fix/XSUP-66433-manage-engine-refresh-token branch April 12, 2026 10:14
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

docs-approved ready-for-pipeline-running Whether the pr is ready for running the whole pipeline, including testing on SAAS machines release-notes-only Indicates that this pull request has ONLY release notes to review for documentation process

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants