Saml2 authentication with UiPath Orchestrator

Help Orchestrator
, , ,
1

HI,

I’m receiving the following error after configuring the SAML2 authentication details. I’m able to redirect to our company identity server and complete the authentication. While returning to the UiPath orchestrator I’m getting the below error.

Please guide to resolve the error

2021-12-23 18:19:51.6198 UiPath.IdentityServer.Web.Controllers.UI.ExternalIdentityController External login info was null. Tenancy info: (null).

2021-12-23 18:17:38.9741 UiPath.IdentityServer.Web.Middleware.ExceptionHandlingMiddleware An error has occurred.
InvalidOperationException*The SPA default page middleware could not return the default page '/index.html' because it was not found, and no other middleware handled the request.
Your application is running in Production mode, so make sure it has been published, or that you have built your SPA manually. Alternatively you may wish to switch to the Development environment.
*   at Microsoft.AspNetCore.SpaServices.SpaDefaultPageMiddleware.<>c__DisplayClass0_0.<Attach>b__1(HttpContext context, Func`1 next)
   at Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware.Invoke(HttpContext context)
   at UiPath.IdentityServer.Web.Security.Antiforgery.AntiForgeryTokenMiddleware.Invoke(HttpContext context)
   at Microsoft.AspNetCore.Routing.EndpointMiddleware.Invoke(HttpContext httpContext)
   at Microsoft.AspNetCore.Localization.RequestLocalizationMiddleware.Invoke(HttpContext context)
   at Microsoft.AspNetCore.Authorization.AuthorizationMiddleware.Invoke(HttpContext context)
   at UiPath.IdentityServer.Web.Extensions.Configuration.ClearCacheConfiguration.<>c.<<DontUseRequestCache>b__1_0>d.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   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.Middleware.ExceptionHandlingMiddleware.InvokeAsync(HttpContext httpContext)
2

@anandhan

Can you check below documentation?

Thanks

3

I have already followed this documentation and configured based on the instruction. currently facing issues after authentication

4

Can you share some specifics on your configuration both on the Identify Server and SAML2 side, masking any sensitive details in part or whole? Ideally leaving the structure of the values intact as a simple type or extra / when there shouldn’t be could be the culprit.

I’m assuming this is a On-Prem / Private installation? What version of Orchestrator?

I’ve gone through the motions of configuring SAML (Azure) and Azure AD in 2019.10 and 2020.10 in a sandbox. 2020 Introduced the Identity Server, and I had no issues with it. I’ll be configuring SAML for my other environments in the coming weeks.

Don’t think these would be helpful in your current stage, but thought I would link them as they might give some ideas, I ran into more challenges with 2019 so that’s where most of my insight is.

Shameless plug if you can vote for this!

1 Like