Configuring host authentication settings

As a system administrator, you can choose the authentication and related default security settings for your entire installation. These settings are inherited by all organizations as default.

Note:

This article walks you through the steps for configuring global authentication and security settings. If you want to configure organization-level settings, i.e., settings that apply to one organization, see documentation on organization-level authentication settings.

See an .

Global authentication settings (host level)

The platform allows you to configure an external identity provider to control how your users sign in. Settings here apply to all organizations.

Note:

The instructions indicated in the following table are for a new installation or if you are configuring one of the external providers for the first time.

If you upgraded and were already using one or more of the external providers listed below, the configuration is migrated, but you might need to perform some reconfiguration tasks. If so, follow the instructions in Reconfiguring authentication after upgrade instead.

The following table provides an overview of the different host-level external providers available:

External Provider Integration	Authentication	Directory Search	Administrators Provisioning
Active Directory and Windows Authentication	Administrators can use SSO with Windows Authentication using the Kerberos protocol	Administrators can search for users from the Active Directory	For a user to be able to login, either the user or a group that the user is a member of should already be added to the UiPath platform. Active Directory users and groups are available in the UiPath platform through directory search.
Azure Active Directory	Administrators can use SSO with Azure AD using the OpenID Connect protocol	Not supported	Users must be manually provisioned into the UiPath organization with an email address matching their Azure AD account.
Google	Users can use SSO with Google using the OpenID Connect protocol	Not supported	Users must be manually provisioned into the UiPath organization with an email address matching their Google account.
SAML 2.0	Users can use SSO with any Identity Provider that supports SAML	Not supported	Users must be manually provisioned into the UiPath organization with a username/email/external provider key (as configured in their external identity provider configuration) matching their SAML account.

Note: Differences between integrating Azure AD at host-level and organization-level: The host-level Azure AD external identity provider only enables SSO functionality. The organization-level Azure AD integration enables SSO, directory search, and automatic user provisioning.

Installation key

The installation key is a token used to allow SSO connections to Orchestrator for integrated applications.

1. Log in to the Management portal as a system administrator.
2. On the Security Settings page, the current installation key is displayed and you can click the Copy icon to copy it to your clipboard:
   
   

   

   
   
3. (Optional) To generate a new installation key, click Generate new.

   A success message appears from the top right indicating that a new key was generated.