Issue Summary:

When a site has Location-based IP allowlisting enabled (e.g., allowing only traffic from Australia), Rovo Chat may fail to read or interact with page context in Confluence (view mode) or work item data in Jira. This occurs because the internal service calls made by Rovo do not correctly forward the original user's IP address to the security enforcement layer. As a result, the request is seen as coming from an untrusted internal service IP (Cloudflare) rather than the user's allowed location, causing the request to be blocked.

Steps to Reproduce

1. Enable Location-based IP allowlisting on an Atlassian Cloud site (e.g., set the policy to allow only Australia).
2. As a user physically located in Australia (within the allowed range), open a Confluence page in View Mode.
3. Open Rovo Chat and ask a question about the current page (e.g., "Summarize this page").

Expected Results

Rovo should recognize the user is within the allowed location and successfully retrieve the page context.

Actual Results

Rovo reports it cannot read or interact with the page data.

Workaround

In Confluence, users can click Edit on the page. Rovo is typically able to interact with the content successfully while the page is in edit mode.
Currently there is no known workaround for this behavior if the user doesn't have Edit access. A workaround will be added here when available