Saml2 authentication with UiPath Orchestrator

[codemonkee (Tim)]

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.

• Configuring and Troubleshooting SAML Integration - #14 by codemonkee
• ADFS / SAML Authentication - Access Denied (2019 Pre-Identity Server)

Shameless plug if you can vote for this!

Map SAML groups to Orchestrator Roles

Testing out SAML with Orchestrator 19.10.15 using the default configuration requires you to create individual users with a matching email address. It would be nice if we could map an attribute e.g. “Role” to a collection of groups (http://schemas.microsoft.com/ws/2008/06/identity/claims/groups) with the ability to map groups to an orchestrator role. This would remove the need to manually create the user profiles locally (or adding a domain user with WindowsAuth) and leverage ADFS/SAML to grant …