- Overview
- Requirements
- Pre-installation
- Preparing the installation
- Downloading the installation packages
- Configuring the OCI-compliant registry
- Granting installation permissions with cluster roles
- Granting installation permissions without cluster roles
- Installing and configuring the service mesh
- Installing and configuring the GitOps tool
- Installing the External Secrets Operator
- Deploying Redis through OperatorHub
- Applying miscellaneous configurations
- Running uipathctl
- Installation
- Post-installation
- Migration and upgrade
- 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 installation
- AI Trust Layer
- Troubleshooting
- 500 errors and rate limiting on S3 requests in ODF
- External Secrets troubleshooting
- Configuring CSI driver tolerations for ODF 4.20
- Temporal as a Service troubleshooting
- AI Center and Document Understanding pods fail to start with TLS certificate verification enabled
- Studio Desktop cannot load Integration Service connectors and activities
- TLS certificate validation errors
- Manual ArgoCD NetworkPolicy mitigation (GHSA-47m3-95c7-g2g8)
- Configuring resource requests and limits for uipathctl-created workloads
Configuring process app security
Configure process app security modes for Process Mining on Automation Suite on OpenShift.
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.