- Overview
- Requirements
- Pre-installation
- Installation
- Post-installation
- Migration and upgrade
- Upgrading Automation Suite
- Migrating standalone products to Automation Suite
- Step 1: Restoring the standalone product database
- Step 2: Updating the schema of the restored product database
- Step 3: Moving the Identity organization data from standalone to Automation Suite
- Step 4: Backing up the platform database in Automation Suite
- Step 5: Merging organizations in Automation Suite
- Step 6: Updating the migrated product connection strings
- Step 7: Migrating standalone Orchestrator
- Step 8: Migrating standalone Insights
- Step 9: Migrating standalone Test Manager
- Step 10: Deleting the default tenant
- Performing a single tenant migration
- Migrating between Automation Suite clusters
- Migrating from Automation Suite on EKS/AKS to Automation Suite on OpenShift
- Monitoring and alerting
- Cluster administration
- Product-specific configuration
- Orchestrator advanced configuration
- Configuring Orchestrator parameters
- Configuring appSettings
- Configuring the maximum request size
- Overriding cluster-level storage configuration
- Configuring NLog
- Saving robot logs to Elasticsearch
- Configuring credential stores
- Configuring encryption key per tenant
- Cleaning up the Orchestrator database
- Skipping host library creation
- 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
- Robot cannot connect to an Automation Suite Orchestrator instance
- Log streaming does not work in proxy setups
- Velero backup fails with FailedValidation error
- Accessing FQDN returns RBAC: access denied error
Automation Suite on EKS/AKS installation guide
Configuring process app security
To restrict the data users have access to when editing transformations, you can set the process app security type for Process Mining process apps in the input.json file. You can configure app security using the app_security_mode setting. This is an overview of the possible values of the app_security_mode setting.
It is recommended to use the 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.
This requires SQL authentication on the Process Mining data warehouse SQL Server. 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. The SQL user used in the connection strings used to connect to the
|
Steps
- 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.Note:The SQL user used in the connection strings used to connect to the
masterdatabase must have enough permissions to create login, users and roles.