- Getting started
- Data security and compliance
- Organizations
- Authentication and security
- Understanding authentication models
- Setting up the Azure AD integration
- Licensing
- Tenants and services
- Accounts and roles
- External applications
- Notifications
- Logging
- Troubleshooting
- Migrating to Automation Cloud™
Understanding authentication models
Local user accounts represent each user's account and are internal to the UiPath platform.
The local accounts model provides a self-contained approach to authentication. It requires an invitation from an organization administrator for new users to join. It's suitable for scenarios where you want complete control over user management within your platform. Available authentication methods include Google, Microsoft, and basic authentication (your own email address and password).
-
To allow usage of all available methods (Google, Microsoft, Basic Authentication) for maximum flexibility, choose the All available methods option.
-
To restrict authentication to only Google, choose the Google sign-in option.
-
To restrict authentication to only Microsoft, choose the Microsoft sign-in option.
This model applies to any new organization by default. It is easy to use, quick to set up, and convenient for your users.
The process for creating a user is as follows:
- Organization administrators must obtain the email addresses of users and use them to invite each user to join their organization. They can do this in bulk.
-
Each invited employee accepts the invitation by navigating to the link provided in the invitation email and creates a UiPath user account. They can:
- Use the invited email as a username and create a password.
-
Use an existing account they have with Microsoft (personal, Azure AD-linked account, or Office 365 account), Google (personal or Google Workspace account), or their personal LinkedIn account to sign in to (or federate in to) their UiPath user account.
The ability to use one of the providers mentioned above is convenient for users who do not have to remember additional passwords. And using organization-owned accounts in Azure AD or Google Workspace lets you enforce organization sign-in policies.
In this model you create users in the same way as in the invitation-based model: you issue an invitation to their email address and your users must create a UiPath account. The difference is that you can choose to enforce sign in using either:
- Google or
- Microsoft
So instead of seeing all sign in options, your users see only the one you selected.
For example, here's what your users would see if you chose to enforce sign in with Microsoft:
They still use their UiPath account to sign in. The account must use the email address where the invitation was sent.
The directory accounts model relies on a third-party directory that you integrate with the UiPath platform. This lets you reuse your company's established identity scheme in UiPath.
- Azure Active Directory: If you have a Microsoft Azure or Office 365 subscription, you can integrate Azure with the UiPath platform to use your existing users and groups from Azure Active Directory within UiPath.
- SAML 2.0: Lets you integrate the UiPath platform with your chosen identity provider (IdP). This lets your users connect to UiPath> with single sign-on (SSO) using the accounts that are already registered with your IdP.
Directory user accounts are created and maintained in a directory which is external to UiPath. Directory accounts are only referenced in the UiPath platform and used as identities for your users.
Compatibility with the invitation-based model
You can continue to use all the features of the invitation-based model in conjunction with a directory model. But to maximize the benefits, we recommend relying exclusively on centralized account management from your integrated directory.
The integration with Azure Active Directory (Azure AD) can offer scalable user and access management for your organization, allowing for compliance across all the internal applications used by your employees. If your organization is using Azure AD or Office 365, you can connect your organization directly to your Azure AD tenant to obtain the following benefits:
-
Automatic user onboarding with seamless migration
- All users and groups from Azure AD are readily available for any UiPath platform service to assign permissions, without the need to invite and manage Azure AD users in the organization directory.
- You can provide Single Sign-On for users whose corporate username differs from their email address, which is not possible with the invitation-based model.
- All existing users with local UiPath accounts have their permissions automatically migrated to their connected Azure AD account.
-
Simplified sign-in experience
- Users do not have to accept an invitation or create a UiPath user account to access the organization. They sign in with their Azure AD account by selecting the Enterprise SSO option or using their organization-specific URL. If the user is already signed in to Azure AD or Office 365, they are automatically signed in.
- UiPath Assistant and Studio versions 20.10.3 and higher can be preconfigured to use a custom Orchestrator URL, which leads to the same seamless connection experience.
-
Scalable governance and access management with existing Azure AD groups
- Azure AD security groups or Office 365 groups, also known as directory groups, allow you to leverage your existing organizational structure to manage permissions at scale. You no longer need to configure permissions in services for each user.
- You can combine multiple directory groups into one group if you need to manage them together.
-
Auditing access is simple. After you've configured permissions in all UiPath platform services using Azure AD groups, you utilize your existing validation processes associated with Azure AD group membership.
The API Access option (Admin > tenant) is not available when using the Azure AD model.
If you have processes in place that use the information from the API Access window to authenticate API calls to UiPath services, you must switch to using OAuth for authorization, in which case the information from API Access is no longer required.
To use OAuth, you must register external applications to the UiPath platform.
This model allows you to connect the UiPath platform to your chosen identity provider (IdP) so that:
- your users can benefit from single sign-on (SSO) and
- you can manage existing accounts from your directory in the UiPath platform, without having to re-create identities.
The UiPath platform can connect to any external identity provider that uses the SAML 2.0 standard.
Benefits
-
Automatic onboarding of users to the UiPath platform: All users from your external identity provider are authorized to sign in to the UiPath organization with basic rights when the SAML integration is active. What this means is:
- Users can sign in to your UIPath organization via SSO using their existing company account, as defined in the IdP.
- Without any further setup, they become members of the Everyone user group, which grants them the User organization role by default. To be able to work in the UiPath platform, users require roles and licenses, as appropriate for their role.
-
If you need to restrict access to only some of your users, you can define the set of users who are allowed to access the UiPath platform in your identity provider.
-
User management: You can add users by directly assigning them to groups, to do this all you have to do is enter their email address when adding users to the group.
Typically, organization administrators manage local accounts from Admin > Accounts & Groups > Users tab. But SAML users are directory accounts in the UiPath ecosystem so they are not visible on this page.
After a user has been added to a group or they have signed in at least once (which automatically adds them to the Everyone group), they are available in search in all UiPath services for direct role or license assignment.
- Attribute mapping: If you use UiPath Automation Hub, for example, you can define custom attribute mapping to propagate attributes from your identity provider to the UiPath platform. For example, when an account is first added to Automation Hub, the first name, last name, email address, job title, and department of the user are already populated.
The identity of your users is verified based on your organization directory. From here, based on user permissions assigned through roles and groups, they can access all your UiPath cloud services with only one set of credentials.The below diagram describes the two identity models, how they work with the various user identities, and how federation can be achieved.In the invitation-based model, identity management is performed on a user reference in the organization directory, while users remain in control of their accounts. But if integrated with Azure Active Directory (Azure AD), it's as simple as looking at the contents of your tenant directory in Azure AD, depicted below with an orange arrow.
Here are some factors to consider when choosing the authentication setting for your organization:
|
Factor |
Invitation-based |
Invitation-based with enforced option |
Azure Active Directory |
SAML |
|---|---|---|---|---|
|
Community license |
Available |
Available |
Not available |
Not available |
|
Enterprise license |
Available |
Available |
Available |
Available |
|
Support for local accounts (UiPath account) |
Available |
Available |
Available |
Available |
|
Support for directory accounts |
Not available |
Not available |
Available |
Available |
|
User account management |
Automation Cloud organization administrator |
Automation Cloud organization administrator |
Azure AD administrator |
Administrator of your identity provider |
|
User access management |
Automation Cloud organization administrator |
Automation Cloud organization administrator |
Automation Cloud user management can be delegated entirely to Azure AD |
Automation Cloud organization administrator |
|
Single sign-on |
Available (with Google, Microsoft, or LinkedIn) |
Available (with Google or Microsoft) |
Available (with Azure AD account) |
Available (with IdP account) |
|
Enforce a complex password policy |
Not available |
Available (if enforced from the IdP) |
Available (if enforced from AAD) |
Available (if enforced from the IdP) |
|
Multi-factor authentication |
Not available |
Available (if enforced from the IdP) |
Available (if enforced from AAD) |
Available (if enforced from the IdP) |
|
Reuse your company's existing identities |
Not available |
Not available |
Available |
Available |
|
Large-scale user onboarding |
Not available(all users must be invited) |
Not available (all users must be invited) |
Available (just-in-time account provisioning) |
Available (just-in-time account provisioning) |
|
Access for collaborators from outside your company |
Available (through invitation) |
Available (through invitation for account on enforced IdP) |
Available |
Available (if allowed by the IdP) |
|
Restrict access from inside corpnet |
Not available |
Not available |
Available |
Available (if enforced from the IdP) |
|
Restrict access to trusted devices | Not available |
Not available |
Available |
Available (if enforced from the IdP) |
If your company already uses a directory to manage employee accounts, the following table can help you find the more advantageous authentication option for you.
|
Factor | Invitation-based | Invitation-based with enforced option | Azure Active Directory | SAML |
|---|---|---|---|---|
|
Already using Google Workspace as your identity provider? |
users need a UiPath account, but SSO is also possible |
users need a UiPath account, but enforced SSO with Google is possible |
N/A |
N/A |
|
Already using Office 365 with your identity provider? |
users need a UiPath account |
users need a UiPath account |
you can grant access to Automation Cloud to existing user accounts |
you can grant access to Automation Cloud to existing user accounts |
|
Already using Azure AD as your identity provider? |
users need a UiPath account |
users need a UiPath account |
you can grant access to Automation Cloud to existing user accounts |
we recommend using the AAD integration instead of the SAML integration |
|
Already using another identity provider? |
users need a UiPath account |
users need a UiPath account |
you can grant access to Automation Cloud to existing user accounts |
you can grant access to Automation Cloud to existing user accounts |
