- 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: Migrating standalone Test Manager
- Step 9: Deleting the default tenant
- Performing a single tenant migration
- Migrating from Automation Suite on Linux to Automation Suite on EKS/AKS
- Monitoring and alerting
- Cluster administration
- Product-specific configuration
- 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
- EKS backup failure due to Velero version
- Velero backup fails with FailedValidation error
- Accessing FQDN returns RBAC access denied error
- Manual ArgoCD NetworkPolicy mitigation (GHSA-47m3-95c7-g2g8)
Reference for process app security configuration options for Process Mining in Automation Suite, including app_security_mode settings in input.json.
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.
It is recommended to use the system_managed option.
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. Passwords are rotated on every use.
This requires SQL authentication on the Process Mining data warehouse SQL Server. The SQL user used in the connection strings to connect to the AutomationSuite_ProcessMining_Warehouse database must have at least the following roles, both during and after installation, to enable per-app security:
- Server role:
securityadminorMS_LoginManager. For details, refer to Fixed server-level roles. - Database-level roles:
db_securityadminanddb_accessadmin. For details, refer to Database-level roles.
single_account
One account is created and 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 to connect to the AutomationSuite_ProcessMining_Warehouse database must have at least the following database-level roles and permissions, both during and after installation, to enable per-app security:
- Database-level roles:
db_securityadminanddb_accessadmin. For details, refer to Database-level roles. - Read/write access: On schema, tables, and views.
Steps
- Turn on SQL Authentication for the Process Mining data warehouse SQL Server. For details, refer to 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.