Issue Summary

When IP allowlisting is enabled in Confluence, the "link" field in the Confluence database returns “No content found” along with a 403 error stating that the IP address is not in the allowlist.

The issue resolves when Rovo is added to the IP allowlist, even though Rovo is not enabled on the customer’s site. This suggests an unexpected dependency between the database link field functionality and Rovo services.

Steps to Reproduce

1. Ensure you have access to Confluence Cloud.
2. Enable IP allowlisting for the Confluence product
3. Navigate to a Confluence database.
4. Attempt to use or search within the "link" field.
5. Observe the error: You’re not allowed to access content because your IP address is not in the allowlist.”
   The field returns “No content found.”
6. Add Rovo to the IP allowlist.
7. Retry accessing the "link" field.
8. Results are now returned successfully.
9. Note that Rovo is not enabled on the site, so this dependency should not exist.

Expected Results

The "link" field should function normally when IP allowlisting is enabled, without requiring Rovo to be included in the allowlist, especially when Rovo is not enabled on the site.

Actual Results

The "link" field returns a 403 error and “No content found” unless Rovo is added to the IP allowlist, even though the site does not use Rovo.

Workaround

Enable IP allowlist for Rovo and then it will work