Getting Error 403 while running Dexter tool on Appdynamics on build 25.10.0-3637

**Describe the bug**
Dexter tool fails with HTTP 403 errors when attempting to extract metrics from the **AppDynamics controllers. running on build 25.10.0-3637** The issue began after these controllers were upgraded to build 25.10.0-3637. Other controllers running on build 25.7.0-3004 doesn't have this issue.

The problem occurs during metric extraction using the Dexter tool against SaaS controllers. Authentication attempts using both internal and Local users result in 403 Forbidden responses. Attempts with temporary access tokens and API clients have also been tested, returning 401 or 403 errors. The controllers are running AppDynamics Controller build 25.10.0-3637.

Technical Indicators:
- Error: "403 (Forbidden)" when accessing metric-data REST API endpoints.
- Error: "401 Unauthorized" when using temporary access tokens.
- Controller versions: AppDynamics Controller build 25.10.0-3637.
- Affected controllers: There are 2 controllers upgraded to build 25.10.0-3637.
- Dexter tool used for metric extraction; authentication via internal and API users tested.

**To Reproduce**
Steps to reproduce the behavior:
Run the dexter job using ***.json file and the job will give Error 403.

**Expected behavior**
Once the job runs successfully without error, there will be output file in excel generated in the Report folder.

**Desktop (please complete the following information):**
- OS: Windows11

**Reports**
When the job run successfully, then the report generate in output folder.

Start by running the Dexter job with the referenced JSON configuration against an AppDynamics SaaS controller on build 25.10.0-3637, then compare its metric-data REST API authentication behavior with build 25.7.0-3004. Done means the job completes without 401 or 403 errors and generates the expected Excel report in the output or Report folder.

Written by the indexing model from the issue text.