- Release notes
- Getting started
- Installation
- Configuration
- Integrations
- Authentication
- Set up single sign-on through Azure Active Directory
- Set up single sign-on through Integrated Windows Authentication
- Adding Superadmin AD Groups
- Adding End-user AD Groups
- Two-Factor Authentication
- Working with Apps and Discovery Accelerators
- AppOne menus and dashboards
- AppOne setup
- TemplateOne 1.0.0 menus and dashboards
- TemplateOne 1.0.0 setup
- TemplateOne menus and fashboards
- TemplateOne 2021.4.0 setup
- Purchase to Pay Discovery Accelerator menus and dashboards
- Purchase to Pay Discovery Accelerator Setup
- Order to Cash Discovery Accelerator menus and dashboards
- Order to Cash Discovery Accelerator Setup
- Basic Connector for AppOne
- SAP Connectors
- Introduction to SAP Connector
- SAP input
- Checking the data in the SAP Connector
- Adding process specific tags to the SAP Connector for AppOne
- Adding process specific Due dates to the SAP Connector for AppOne
- Adding automation estimates to the SAP Connector for AppOne
- Adding attributes to the SAP Connector for AppOne
- Adding activities to the SAP Connector for AppOne
- Adding entities to the SAP Connector for AppOne
- SAP Order to Cash Connector for AppOne
- SAP Purchase to Pay Connector for AppOne
- SAP Connector for Purchase to Pay Discovery Accelerator
- SAP Connector for Order-to-Cash Discovery Accelerator
- Superadmin
- Dashboards and charts
- Tables and table items
- Application integrity
- How to ....
- Working with SQL connectors
- Introduction to SQL connectors
- Setting up a SQL connector
- CData Sync extractions
- Running a SQL connector
- Editing transformations
- Releasing a SQL Connector
- Scheduling data extraction
- Structure of transformations
- Using SQL connectors for released apps
- Generating a cache with scripts
- Setting up a local test environment
- Separate development and production environments
- Useful resources
Set up single sign-on through Azure Active Directory
This page describes how to set up Single Sign-on through Microsoft Azure Active Directory.
If Single Sign-On through Azure Active Directory is enabled and correctly configured, a button is displayed at the bottom of the Login page. See the illustration below.
Follow these steps to register and configure your app in the Microsoft Azure Portal.
Step |
Action |
---|---|
1 |
Go to the Microsoft Azure App Registrations page and click New Registration. |
2 |
• In the Register an application page, fill the Name field with the desired name of your Uipath Process Mining instance. • In the Supported account types section, select which accounts can use UiPath Process Mining. • Set the Redirect URI by selecting Web from the drop-down and filling in the URL of the UiPath Process Mining instance plus the suffix
/auth/signin-aad/ . For example, https://example.com/auth/signin-aad/ .
• Click on Register to register your UiPath Process Mining instance in Azure AD. The app is added to the list of applications. |
3 |
Locate the app in the applications list. Click on the app to open the settings page. |
4 |
Click on Authentication in the Manage menu. • Locate the Implicit grant and hybrid flows section. • Select the ID tokens (used for implicit and hybrid flows) option. |
5 |
Click on Token configuration in the Manage menu. • Use + Add groups claim to add a groups claim. • Select the appropriate options in the Select group types to include in Access, ID, and SAML tokens options list. Note: this determines which groups to include in the list of groups sent to Process Mining. You can choose to sent all Security groups, all Directory roles, and/or All groups. You can also choose to send just a specific set of groups.
• In the Customize token properties by type options make sure that the Group ID setting is is selected since Process Mining expects Azure groups to always be a GUID. |
6 |
Click on API permissions in the Manage menu. • Click on + Add a permission and add the
User.Read permission.
|
-
Go to the Settings tab of the Superadmin page of your UiPath Process Mining installation. See illustration below.
-
Add the required Azure AD settings in the
ExternalAuthenticationProviders
setting of the Server Settings. Below is a description of the JSON keys of theazureAD
object.Key
Description
Mandatory
clientIdentifier
The Application (client) ID as displayed in the Essentials section on the app Overview page in Microsoft Azure Portal. See illustration below.
Yes
tenant
The Directory (tenant) ID as displayed in the Essentials section on the app Overview page in Microsoft Azure Portal.
Yes
loggingLevel
Enables you to specify whether you want to add information regarding the login process to the log in the[PLATFORMDIR]/logs/iisnode
folder. Possible values:• info;
• warn;
• error.
Note: It is recommended to enable this only when you experience problems with logging in.No
See illustration below for an example of the Server Settings with theExternalAuthenticationProviders
setting with theazureAD
object., "ExternalAuthenticationProviders": { "azureAd": { "clientIdentifier": "d1a1d0f4-ce09-4232-91b9-7756d613b78a" , "tenant": "f636b271-d616-44d1-bb23-43a73b6eb571" } }
, "ExternalAuthenticationProviders": { "azureAd": { "clientIdentifier": "d1a1d0f4-ce09-4232-91b9-7756d613b78a" , "tenant": "f636b271-d616-44d1-bb23-43a73b6eb571" } } - Click on SAVE to save the new settings.
- Press F5 to refresh the Superadmin page. This loads the new settings and enables Azure AD groups to be created based on these settings.
Auto-login
AutoLogin
Server Setting, the user will be automatically logged in using the current active SSO method.
AutoLogin
is set to none
. If you want to enable auto-login for end-users and/or Superadmin users, you can specify this in the AutoLogin
in the Superadmin Settings tab. See The Settings Tab.
In order to use Integrated Azure Active Directory authentication, you must create one or more AD groups to allow members to login. For Superadmin users, or app developers you can create AD groups on the Superadmin users tab. See Adding Superadmin AD Groups.
For end-user authentication, AD groups can be created on the End user administration page. See Adding End-user AD Groups.