- Release notes
- Getting started
- Installation
- Configuration
- Integrations
- 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
Debugging LDAP Settings
If you regard any issues with the LDAP settings when you are using in UiPath Process Mining, you can debug the LDAP settings. Debugging need to be done on the server where you are setting up LDAP, for instance a production server.
ldp.exe
.
Step |
Action |
---|---|
1 |
Connect to the server using, for example, remote desktop. |
2 |
On the server, search for
ldp.exe and double click to start the tool.
|
3 |
Go to the Connection menu and select Connect…. |
4 |
Enter the name server name where the AD is hosted. |
5 |
Depending on the server, you might also need to change the port number and enable SSL. Some common port numbers are 389, 636, 3268, and 3269. |
6 |
Click on OK. |
ldp.exe
will show information about the server. In the title bar the following details you need to use are displayed: the url the
base of the ldap
setting in UiPath Process Mining.
See illustration below.
ldp.exe
window. You can use this information to fix connection problems.
Once successfully connected, you can test the user you will use in the LDAP setting.
Follow these steps to test the LDAP user.
Step |
Action |
---|---|
1 |
Go to the Connection menu and select Bind…. |
2 |
Enter the details of the user and select Bind with credentials. |
3 |
Click on OK. |
A message is displayed to indicate whether the bind was successful. See illustration below.
If there are any authentication issues, these are displayed as well. Use this information to fix the authentication issues.
Go to the Settings tab of the Superadmin page of your UiPath Process Mining installation.
bindDN
property of the ldap
Server setting must be the user displayed as the ‘Authenticated as’ user in ldp.exe
. This might include “DOMAINNAME\”
as a prefix.
PGDCTEST\\
estuser
. See illustration below.
ldp.exe
in the ldap
Server setting in UiPath Process Mining.
See illustration below for an example.
"ExternalAuthenticationProviders": {
"ldap": {
"url": "ldap://PROCESSGOLDTEST.pgdctest.local:389",
"base": "DC=pgdctest,DC=com",
"bindDN": "PGDCTEST\)\)\) estuser",
"bindCredentials": "Passw0rd!",
}
}
"ExternalAuthenticationProviders": {
"ldap": {
"url": "ldap://PROCESSGOLDTEST.pgdctest.local:389",
"base": "DC=pgdctest,DC=com",
"bindDN": "PGDCTEST\)\)\) estuser",
"bindCredentials": "Passw0rd!",
}
}
dsquery
command.
Below is an example of finding the correct AD group for the username “Test User”. In the command prompt, use the following command:
dsquery user -name "Test User"
This will give you the DN of the user:
dsquery
again to find the AD groups you can use in UiPath Process Mining:
dsquery * "CN=Test User,CN=users,dc=pgdctest,dc=local" -attr memberOf
Any of the groups can now be used in UiPath Process Mining. In this example the groups are:
CN=Enterprise Admins,CN=Users,DC=pgdctest,DC=local
CN=Administrators,CN=Builtin,DC=pgdctest,DC=local