Error: Logon error: Access denied during SAML login to AWI - Automic Automation

Products

• CA Automic Workload Automation - Automation Engine

Issue/Introduction

While attempting to log into the Automic Web Interface (AWI) using SAML authentication, the login fails with an access denied error. This typically occurs when multiple environments (e.g., Dev and Prod) share the same connection name in the configuration files.

Symptoms

• Users receive the following error on the AWI login page: Logon error: Access denied
• The connection may appear to route to the wrong environment or fail after identity provider (IdP) authentication.

Environment

• Automic Automation Engine
• Automic Web Interface (AWI)
• SAML SSO Integration

Cause

Each connection defined in the uc4config.xml must have a unique name. If a Dev environment and a Prod environment both use the default name (e.g., "AUTOMIC"), the SAML assertion or web app cache may conflict, resulting in a failed login.

 

Resolution

Ensure that every system connection has a unique name across the environment landscape.

1. Navigate to the AWI configuration folder and open uc4config.xml.
2. Locate the <connection> elements and assign a unique name to the prod system (e.g., change name="AD" to name="AP").

   Note: The maximum length for the connection name is 8 characters.

3. Update the Automation Engine (AE) configuration file (ucsrv.ini) on the production server to match the new unique name.
4. Update the configuration file (ini) for every Agent connected to that system to reflect the new name.
5. Reboot the server to clear any existing cache.
6. Verify the AWI login using the new unique connection name.

Additional Information

For more details on setting up SAML, refer to the Setting up Single Sign-On - SAML documentation page.