automation-suite
2.2510
true
Automation Suite on OpenShift installation guide
- 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
- Rotating Blob Storage Credentials
- Disabling use of pre-signed URLs when uploading data to Amazon S3 storage
- Configuring process app security
- Setting up Kerberos authentication with basic MSSQL authentication for Process Mining
- 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
Setting up Kerberos authentication with basic MSSQL authentication for Process Mining
Configure Kerberos authentication with SQL authentication for Process Mining on OpenShift.
Note:
When you are performing a new installation and you want to use Kerberos authentication, it is strongly recommended to configure process app security as single_account. For details, refer to Configuring process app security.
When you want to use Kerberos authentication for login to Automation Suite and use basic MSSQL authentication for Process Mining you need to add the following in the processmining section in the input.json file.
"kerberos_auth_config": {
"enabled": false
},
"kerberos_auth_config": {
"enabled": false
},
The following example shows a complete processmining section with Kerberos authentication with basic MSSQL and PostgreSQL authentication:
"processmining": {
"enabled": true,
"advanced_configuration": {},
"airflow": {
"metadata_db_connection_str": "postgresql+psycopg2://kerberos_user:@kerberospostgres.AUTOSUITEAD.LOCAL:5432/AutomationSuite_Airflow"
}
}
"processmining": {
"enabled": true,
"advanced_configuration": {},
"airflow": {
"metadata_db_connection_str": "postgresql+psycopg2://kerberos_user:@kerberospostgres.AUTOSUITEAD.LOCAL:5432/AutomationSuite_Airflow"
}
}