- Overview
- Requirements
- Installation
- Post-installation
- Migration and upgrade
- Upgrading Automation Suite on EKS/AKS
- Step 1: Moving the Identity organization data from standalone to Automation Suite
- Step 2: Restoring the standalone product database
- Step 3: Backing up the platform database in Automation Suite
- Step 4: Merging organizations in Automation Suite
- Step 5: Updating the migrated product connection strings
- Step 6: Migrating standalone Orchestrator
- Step 7: Migrating standalone Insights
- Step 8: Deleting the default tenant
- B) Single tenant migration
- Migrating from Automation Suite on Linux to Automation Suite on EKS/AKS
- Monitoring and alerting
- Cluster administration
- Product-specific configuration
- Using the Orchestrator Configurator Tool
- Configuring Orchestrator parameters
- Orchestrator appSettings
- Configuring appSettings
- Configuring the maximum request size
- Overriding cluster-level storage configuration
- Configuring credential stores
- Configuring encryption key per tenant
- Cleaning up the Orchestrator database
- Troubleshooting
- The backup setup does not work due to a failure to connect to Azure Government
- Pods in the uipath namespace stuck when enabling custom node taints
- Unable to launch Automation Hub and Apps with proxy setup
- Pods cannot communicate with FQDN in a proxy environment
- Test Automation SQL connection string is ignored
Configuring process app security
input.jsonapp_security_mode setting. Below is an overview of the possible values of the app_security_mode setting.
system_managed option.
|
Value |
Description |
system_managed (default)
|
A SQL user is created automatically per process app. This ensures that users editing transformations in Process Mining can only query data that belongs to the process apps for which they have edit permissions.
Note:
This requires SQL authentication on the Process Mining data warehouse SQL Server. The SQL user used in the connection strings used to connect to the
AutomationSuite_ProcessMining_Warehouse database must have at least the following server-level and database-level roles both during and post-installation to enable
per app security:
|
|
|
One account is created that is used for all process apps. This means that when editing transformations in Process Mining, users can query data from other process apps. Note:
The SQL user used in the connection strings used to connect to the
AutomationSuite_ProcessMining_Warehouse must have at least the following database-level roles and permissions both during and post-installation to enable per app
security:
|
-
Turn on SQL Authentication for the Process Mining data warehouse SQL Server. See the official Microsoft documentation on Change server authentication mode.
-
Grant ALTER ANY LOGIN to the provisioning user of Process Mining.
-
Grant access to the
masterdatabase to the provisioning user of Process Mining.Attention:The SQL user used in the connection strings used to connect to themasterdatabase must have enough permissions to create login, users and roles.
