Invalid Credentials, failed to login while calling APIs in Automation Suite

News Knowledge Base
1

Orchestrator Authenticate API Calls are failing with 'Invalid Credentials, failed to login'.

Orchestrator Authenticate API Calls are failing with 'Invalid Credentials, failed to login'.

Note: This issue is specific to the Automation suite deployment.

Root cause:

The automatic addition of a "default" tenant during the creation of a new organization poses the risk of unanticipated consequences when initiating API calls.

Alternatively:

Users might unintentionally generate tenants with identical names across various organizations within the Automation suite, leading to misleading results.

As a result, when utilizing the Authenticate API with accurate credentials, the aforementioned error may manifest.

Resolution:

To mitigate this issue, the Automation suite adopts a distinct formatting for storing tenant names in the database. Despite this, the graphical user interface (GUI) continues to display it as "Default" or the custom Tenant name that the customer may have created.

One may explore the Database or Call the Get Tenant API(/odata/Tenants) to view the correct name.

An example of calling APIs is listed below:

  • The Request URL appears to be something like below:
https://{FQDN}/{Org}/{TenantName}/orchestrator_/odata/Tenants

Note: Please feel free to update the Endpoint

  • The outcome shall contain the Display Name and the Name, example below:
"Name": "defaulttenant",

"Key": "a56afddce99be1fdc48",

"DisplayName": "Support",

  • The Value of the Name Field defines the Actual name of the tenant which is supposed to be used in the Authenticate API.
  • Post fetching the above, update the TenancyName parameter in the /api/Account/Authenticate API and this should resolve the issue:
{

 "tenancyName": "string",

 "usernameOrEmailAddress": "string",

 "password": "string"

}