Error 603 from Cloud migration tool when exporting data from on-prem Orchestrator

Help Orchestrator
, , , ,
1

Hello,
I’m trying to use the Cloud migration tool to migrate an on-prem Orchestrator to a cloud Orchestrator but I can’t even connect the tool to the on-prem Orchestrator to export the data yet.

I tried to connect the migration tool to the on-prem Orchestrator using “admin” username and password. The username and password works when I sign in to the Orchestrator on my browser but on the migration tool I get the error “Invalid credentials, please verify your credentials and tenant name. (#603)”. What would be the cause and how can I solve it?

I tried asking chatGPT and it said that the Resource Owner Password Credentials Flow (Password Flow / ROPC) in the on-prem Orchestrator might be disabled and has to be enabled for the migration tool to be able to connect. Could this be the case?

Also I want to make sure that the tenant name is correct. I use the name that I see under “choose the organization” when I log in (using microsoft). Is it the correct logical tenant name or where can I check the tenant name for sure?

Thank you in advance for your answers!

2

Hi @Kwanmongkol_Rodsiri

  • Cloud Migration Tool does not work with SSO/Microsoft login
  • ROPC (username/password auth) must be enabled on on-prem Orchestrator
  • Use a local Orchestrator admin user
  • Tenant name = logical tenant name from Orchestrator → Tenants (not display name)

That’s why you’re getting error #603.

3

Hello @Kwanmongkol_Rodsiri

Often on-prem installations will have the default tenant name Default.
Have you tried using that?

Also check that prerequisites are met.

image
image1152×593 61.5 KB

Regards
Soren

4

The #603 Invalid credentials error in the Cloud Migration Tool is expected when using SSO / Microsoft login.

Usually migration tool does not support SSO and requires username–password (ROPC) authentication.
Use a local Orchestrator admin account (not Azure/Microsoft login) and make sure ROPC is enabled on the on-prem Orchestrator.Make sure you use default tenant name.