Advanced Reporting token not provisioned after successful OAuth handshake — Magento Open Source 2.4.6-p13 after server migration | Community
Skip to main content
Level 1
April 10, 2026
Question

Advanced Reporting token not provisioned after successful OAuth handshake — Magento Open Source 2.4.6-p13 after server migration

  • April 10, 2026
  • 1 reply
  • 7 views

Hi,

I migrated my Magento Open Source 2.4.6-p13 store to a new server and Advanced Reporting stopped working. Clicking the menu item redirects to the Experience League documentation instead of opening the dashboard.

Store: https://pappeat.com
Version: Magento Open Source 2.4.6-p13
PHP: 8.2.30
Base currency: EUR only (verified in config and in all orders)

All Magento-side checks are clean:

  • ✅ Advanced Reporting enabled (analytics/subscription/enabled = 1)

  • ✅ Cron running every minute under correct system user

  • ✅ OAuth endpoints reachable (/oauth/token/request and /oauth/token/access respond correctly)

  • ✅ analytics_subscribe cron runs with status = success

  • ✅ System log confirms: "Request token was exchanged to obtain access token for consumer 12"

  • ✅ OAuth consumer and access token created in oauth_consumer and oauth_token tables

  • ✅ No AWS S3 used as data source

  • ✅ Valid SSL certificate on public HTTPS URL

  • ❌ analytics/general/token remains NULL in core_config_data after every successful handshake

  • ❌ analytics_collect_data never appears in cron_schedule

  • ❌ No errors in system.log or exception.log

The OAuth handshake completes successfully on the Magento side but Adobe's backend does not return the analytics token. This worked correctly on the previous server before migration.

Could Adobe please verify and re-provision the Advanced Reporting subscription for this store on the backend? The issue appears to be that the store's subscription is still linked to the old server/IP and needs to be reset on the Adobe side.

1 reply

MandyGeorge
Community Advisor and Adobe Champion
Community Advisor and Adobe Champion
April 10, 2026

This sounds like something you'll need to open a ticket with Adobe support for. Most of us on the community don't even actually work for adobe, were just other users like yourself.

In your admin console there should be an option to open a support ticket. If you're not an admin, you'll have to ask one of your organization's admins to do it. Adobe's support is pretty good to work with, they should be able to get it sorted.