Unable to obtain configuration from: ‘[PII of type ‘System.String’ is hidden. For more details, see Bing]’

We have just installed a brand new on-premises orchestrator and it’s failing with the bellow error. Anyone has any idea of what it is?

2023-05-26 17:55:11.5675 UiPath.IdentityServer.Web.Middleware.ExceptionHandlingMiddleware IDX20803: Unable to obtain configuration from: ‘[PII of type ‘System.String’ is hidden. For more details, see Bing]’.
InvalidOperationExceptionIDX20803: Unable to obtain configuration from: ‘[PII of type ‘System.String’ is hidden. For more details, see Bing]’. at Microsoft.IdentityModel.Protocols.ConfigurationManager1.GetConfigurationAsync(CancellationToken cancel) at Microsoft.AspNetCore.Authentication.JwtBearer.JwtBearerHandler.HandleAuthenticateAsync() at Microsoft.AspNetCore.Authentication.JwtBearer.JwtBearerHandler.HandleAuthenticateAsync() at Microsoft.AspNetCore.Authentication.AuthenticationHandler1.AuthenticateAsync()
at Microsoft.AspNetCore.Authentication.AuthenticationService.AuthenticateAsync(HttpContext context, String scheme)
at Microsoft.AspNetCore.Authorization.Policy.PolicyEvaluator.AuthenticateAsync(AuthorizationPolicy policy, HttpContext context)
at Microsoft.AspNetCore.Authorization.AuthorizationMiddleware.Invoke(HttpContext context)
at UiPath.IdentityServer.Web.Extensions.Configuration.ClearCacheConfiguration.<>c.<b__1_0>d.MoveNext()
— End of stack trace from previous location —
at Swashbuckle.AspNetCore.SwaggerUI.SwaggerUIMiddleware.Invoke(HttpContext httpContext)
at Swashbuckle.AspNetCore.Swagger.SwaggerMiddleware.Invoke(HttpContext httpContext, ISwaggerProvider swaggerProvider)
at UiPath.IdentityServer.Web.Middleware.CancellationTokenRegisterMiddleware.InvokeAsync(HttpContext httpContext)
at UiPath.IdentityServer.Web.Extensions.Configuration.GlobalSecurityConfiguration.<>c.<b__1_3>d.MoveNext()
— End of stack trace from previous location —
at NWebsec.AspNetCore.Middleware.Middleware.CspMiddleware.Invoke(HttpContext context)
at NWebsec.AspNetCore.Middleware.Middleware.MiddlewareBase.Invoke(HttpContext context)
at NWebsec.AspNetCore.Middleware.Middleware.MiddlewareBase.Invoke(HttpContext context)
at NWebsec.AspNetCore.Middleware.Middleware.MiddlewareBase.Invoke(HttpContext context)
at Duende.IdentityServer.Hosting.IdentityServerMiddleware.Invoke(HttpContext context, IEndpointRouter router, IUserSession userSession, IEventService events, IIssuerNameService issuerNameService, ISessionCoordinationService sessionCoordinationService) in //src/IdentityServer/Hosting/IdentityServerMiddleware.cs:line 116
at Duende.IdentityServer.Hosting.MutualTlsEndpointMiddleware.Invoke(HttpContext context, IAuthenticationSchemeProvider schemes) in /
/src/IdentityServer/Hosting/MutualTlsEndpointMiddleware.cs:line 94
at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context)
at Duende.IdentityServer.Hosting.DynamicProviders.DynamicSchemeAuthenticationMiddleware.Invoke(HttpContext context) in //src/IdentityServer/Hosting/DynamicProviders/DynamicSchemes/DynamicSchemeAuthenticationMiddleware.cs:line 47
at Duende.IdentityServer.Hosting.BaseUrlMiddleware.Invoke(HttpContext context) in /
/src/IdentityServer/Hosting/BaseUrlMiddleware.cs:line 27
at UiPath.IdentityServer.Web.Middleware.OrgLevelIssuerMiddleware.InvokeAsync(HttpContext httpContext, ITargetedFeatureFlagService targetedFeatureFlagService, IOptionsSnapshot`1 appSettings, OrgLevelIssuerHelperService orgLevelIssuerHelperService)
at UiPath.IdentityServer.Web.Middleware.PublicOriginMiddleware.Invoke(HttpContext context)
at UiPath.IdentityServer.Web.Middleware.ExceptionHandlingMiddleware.InvokeAsync(HttpContext httpContext)

Here is how the application pool is set up

@Joel_Medeiros

Looks like a certificate error.Please check

https://docs.uipath.com/orchestrator/standalone/2022.10/installation-guide/identity-server-troubleshooting

Hope this helps

Cheers

1 Like

Hi @Anil_G,

You are right on the money again. The certificate is missing the server names on the “Subject Alternative Name”. It’s a multi-node on-premises deployment, we have to have all of the nodes there. I have to engage other folks to fix it.

Thanks for helping out.

1 Like

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