I can only log in to the host tenant

Help Orchestrator
1

I have deployed Orchestrator v2022.4 on Azure.
I can login to the host tenant, but can’t log in to the Default tenant or the newly created tenant.
Invalid credentials (#MTI_7) is displayed on login error.
I think the password is correct because I can get the information with the API.
If anyone knows the cause, please let me know.

画像1
画像1648×719 46.6 KB

2 Likes
2

Is the tenant name correct then?

3

Yes, the tenant name is correct.
Also, when I try to create a new tenant and log in, I get the same error.

1 Like
4

Can you make your host login once and show tenants page pls

5

We have an on-prem installation, so this may not be helpfull. But we have just deployed v2022.4 on-prem. We faced a similar problem, where we were able to log-in to the Host, and perform operations on it. But we were unable to log-in to any of our tenants. We recieved 2 different error messages.

  1. invalid credentials
    image
    image663×967 21.9 KB
  2. Unauthorized
    image
    image879×927 34.2 KB

Apparently the config for Identity-server was pointing to an invalid certificate. The identity-server is responsible for authentication Tokens.
We just had to change the value of the SigningCredentialSettings\StoreLocation\Name to match the valid certificate.
config is found here: {InstallationPath}\UiPath\Orchestrator\Identity\appsettings.Production.json

6

hi @miito_0320
Once you deploy the Orchestrator , it will be expose you to create , HOST tenant password and Default tenant password

Make sure that u are used both same or do u have any separate

7

Tenants page is below.
I tried to create another tenant for testing, but I can’t log in as well.

画像2
画像21220×388 43.5 KB

Also, I found that I can connect by removing the access restriction of Azure AppService.
If I add the permission setting of the connection source IP address, I will not be able to log in other than the host tenant.

8

I searched for the file appsettings.Production.json, but couldn’t find it.
I will look for a file with similar settings.

9

I tried changing each password, but the problem was not resolved…

10

I understand the cause. The AppService of the Orchestrator only allowed access to the global IP of the client, but it also needed to allow the global IP of IdentityServer.
I must also allow the global IP of Orchestrator to IdentityServer.

11

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.