We just updated the license in Orchestrator, but found that both the previously created tenant and the tenant created after updating the license cannot log in to Orchestrator. Is there a solution to this?
Attempting to modify the password also results in an error prompt.
Our UiPath Ochetrator version is 2021.10.0. and we use the guide and execute the sql to reset default tenant 's admin account to 890iopqa ,but it is not work. I also used the forget password function, but it prompted me that the partition is invalid.Is it possible that it was caused by other reasons. Thanks.
During and after Orchestrator installation, private key related errors will show up if the application pool user is not added to the signed certificate private key. These are the steps to do so.
- Check the certificate which is used in Orchestrator website bindings.
- Go to Windows → type “run” → mmc
- Once the mmc window is up-> Add Snap-in → Add certificate → Local Computer
- Go to Personal → Certificate → Select the certificate which is used by Orchestrator website.
- Right Click Certificate → All tasks → Manage Private keys → Add group “IIS_IUSRS”
- Open cmd.exe as Administrator and run iisreset command.
import-module WebAdministration $siteName = ‘UiPath Orchestrator’ $binding = (Get-ChildItem -Path IIS:\SSLBindings | Where Sites -eq $siteName) $certLoc = “cert:\LocalMachine\MY$($binding.Thumbprint)” $cert = Get-Item $certLoc $keyPath = $env:ProgramData + "\Microsoft\Crypto\RSA\MachineKeys" $keyName = $cert.PrivateKey.CspKeyContainerInfo.UniqueKeyContainerName $keyFullPath = $keyPath + $keyName $acl = (Get-Item $keyFullPath).GetAccessControl(‘Access’) $permission=“IIS_IUSRS”,“Full”,“Allow” $accessRule = New-Object -TypeName System.Security.AccessControl.FileSystemAccessRule -ArgumentList $permission $acl.AddAccessRule($accessRule) Set-Acl -Path $keyFullPath -AclObject $acl
- “The provided partition is invalid. (#MTI_1)”
Resolution: In order to identify the root cause of the issue, check the logs in the Event Viewer.
Event viewer logs are where windows stores system logs. They can sometimes show more detailed error messages than those that are typically shown to the user.
If the below error occurs:
Authentication failedMicrosoft.IdentityModel.Tokens.SecurityTokenInvalidSigningKeyException: IDX10249: X509SecurityKey validation failed. The associated certificate has expired. ValidTo (UTC): ‘System.DateTime’, Current time (UTC): ‘System.DateTime’.
at void Microsoft.IdentityModel.Tokens.Validators.ValidateIssuerSecurityKey(SecurityKey securityKey, SecurityToken securityToken, TokenValidationParameters validationParameters)
at void System.IdentityModel.Tokens.Jwt.JwtSecurityTokenHandler.ValidateIssuerSecurityKey(SecurityKey key, JwtSecurityToken securityToken, TokenValidationParameters validationParameters)
at ClaimsPrincipal System.IdentityModel.Tokens.Jwt.JwtSecurityTokenHandler.ValidateTokenPayload(JwtSecurityToken jwtToken, TokenValidationParameters validationParameters)
at ClaimsPrincipal System.IdentityModel.Tokens.Jwt.JwtSecurityTokenHandler.ValidateToken(string token, TokenValidationParameters validationParameters, out SecurityToken validatedToken)
at async Task UiPath.Orchestrator.Security.Auth.IdentityUser.IdentityUserAccessTokenAuthenticationHandler.HandleAuthenticateAsync()
Then there is an issue with the certificate and that means that the Orchestrator is not able to communicate with Identity, hence unable to get the credentials.
Perform the below steps:
- Renew the client certificate
- Login with a domain administrator account
- Windows start menu and type run (or Windows key + R)
- Type “mmc” and press enter
- File > Add/Remove Snap-In
- Double click on “Certificates”
- Choose “Computer account” and click Next
- Choose “Local Computer: (the computer this console is running on) and click Finish
- Click on ok to add the Certificates Snap-In
- Expand Certificates > Personal > Certificate on the left panel
- Right-click on the client certificate (Intended Purposes: Client Authentication)
- Navigate to All Tasks > advanced Operations > renew this certificate with the same key (if your domain CA doesn’t accept this action, choose the request certificate option with the same key or new key)
- Double click the certificate and change the register to “Details” and scroll down to “Thumbprint”
- Now open Windows Explorer and navigate to “\Identity” and open the file “appsettings.Production.json” with an editor like Notepad
- Make sure that the “Name” value in the “AppSettings” category is set to the “Thumbprint” of the new certificate (without blanks)
- Open the IIS Manager
- On the left panel click on the server name entry (!NOT! the website entry)
- Click on the right panel “Restart” in the “Actions” section
Thanks Marian. We manually updated the certificate and it works. The problem has been resolved. Thanks very much for your support again,
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.