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

[madolynndata]

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

[MOlausson]

@madolynndata can you share how you run the process-migrator? The error you shared suggest that the $MyOrganisation parameter is not resolved, so the tool would try to authenticate against that literal.

[madolynndata]

@MOlausson I run the process-migrator for PowerShell inside VSCode.

I have test running it from PowerShell, Cmd, outside VSCode. The $MyOrganisation is the same as 'https://dev.azure.com/myorg/' (for the cloud part) or my internal url for the Server side.

I have tried with and without any argument.

PS C:\Users\me\repos\azdo> C:\Users\me\AppData\Roaming\npm\process-migrator --mode=migrate --config=./configuration.json

[norschel]

@madolynndata I would first try temporarily disabling the validity check for TLS certificates. To do this, set the environment variable NODE_TLS_REJECT_UNAUTHORIZED=0.

It is quite common for some companies to use security products that break SSL/TLS in order to check traffic, which then causes the certificates to no longer be valid.

I just had a similar error with my own certificates on a test system.