Connection Failure with Personal Access Token in Both On-Premise and Cloud Environments

Hello,

I am encountering an issue where no operations seem to work in both on-premise and cloud environments. The system fails to connect to my organization account using a personal access token, despite the token being configured to allow access to all accessible organizations.

Error Message:

[ERROR] Failed to connect to account $MyOrganisation using personal access token provided, check url and token

Steps to Reproduce:

Configure a personal access token with access to all organizations.
Attempt to perform an operation using the process-migrator tool.
Observe the failure and the error message mentioned above.

Additional Context:

I have tried changing both the source and target organization servers and services, but the issue persists.
The token has been verified to be correct and has the necessary permissions.

Environment Details:

Process-Migrator Version: Latest release (no specific tag associated)
Operating System: Windows 11
Any other relevant environmental details or configurations.

Questions:

1. Are there any known issues with personal access tokens in the current version?
2. Could there be specific configurations or permissions required that are not currently documented?

Thank you for your assistance.

Originally posted by @madolynndata in #46

Start by reproducing the failure with the process-migrator tool using the reported personal access token against both on-premise and cloud organization servers on Windows 11. Compare the connection configuration and error output for each environment; done means identifying the required URL, token, or permission change and documenting or fixing the cause.