Orchestrator Manager - Token expired issue

Help Orchestrator
1

Hello,

We have an on-prem orchestrator and will be migrating everything to a new orchestrator server. I found the Orchestrator Manager tool Orchestrator Manager | UiPath Marketplace which looks very convenient.
However, I can’t get it to work.

I’ve created an external app, added all the scopes, input the app id and secret into the tool and click get assets > execute. Excel opens with empty rows and I instantly get the error: token expired. It happens within a second so it can’t be a timeout or something, I assume the token is valid for at least 30 mins, but there’s nothing I can do to make it work.

Any ideas?

2

Hi @EvelineL

This looks more like an authentication/configuration issue than an actual token expiry. Please verify the External App scopes, App ID/Secret, and that they are configured for the correct Orchestrator tenant.

Since it fails immediately, I’d also check whether your Orchestrator version is compatible with the Orchestrator Manager version you’re using.

3

@EvelineL can you confirm which scope you have configured in your External Application. Is it Application or User. If you have configured the user scope then change it to application and then check.

And also try to get the same token in the postman, using the same details.

https://{yourDomain}/{organizationName}/identity/connect/token

Json body

grant_type=client_credentials
client_id=<APP_ID>
client_secret=<APP_SECRET>
scope=OR.Assets

Expected Result

{
    "access_token": "...",
    "expires_in": 3600,
    "token_type": "Bearer",
    "scope": "OR.Assets"
}

Also you can have a look on this for more details like how to configure in postman.

4

Hi @EvelineL ,
Please check these once:

  1. Verify the External App type
    • Make sure it is a Confidential Application and that you’re using the correct Client ID and Client Secret.
  2. Check scopes
    • Ensure all required Orchestrator API scopes are granted.
    • After adding scopes, regenerate the secret if needed and update it in the tool.
  3. Validate Orchestrator URL
    • Use the exact URL expected by the tool (including tenant if required).
    • A wrong URL or tenant can cause token validation failures that appear as “token expired”.
  4. Check server time
    • Make sure the machine running Orchestrator Manager and the Orchestrator server have synchronized system clocks. Time drift can make newly issued tokens appear expired.
  5. Test the credentials separately
    • Use Postman or Swagger with the same Client ID/Secret.
    • If token generation fails there as well, the issue is with the app configuration rather than the migration tool.
  6. Tool compatibility
    • Verify that the Marketplace version of Orchestrator Manager supports your specific Orchestrator version. Older tools sometimes fail with newer authentication methods.

Thanks