Failed to log on using the given credentials in WCC ECLI - AutoSys Workload Automation

Products

• CA Workload Automation AE - Scheduler (AutoSys)

Issue/Introduction

When attempting to run commands (such as autoping or autorep) via the WCC Enterprise Command Line (ECLI), the execution fails with a "StatusCode: 500" and a message stating "Failed to log on using the given credentials."
This occurs despite the AutoSysCommandWrapper having the correct setuid permissions.

Symptoms

• WCC ECLI returns: Failed to log on using the given credentials. StatusCode: 500
• Scheduler logs ($AUTOUSER/out/*.log) show: Authentication failed via scheme Basic: JAAS login failed
• AutoSysCommandWrapper permissions are correctly set to 4755 (rwsr-xr-x) and owned by root.

 

Environment

• AutoSys Workload Automation AE
• Workload Control Center (WCC)

Cause

The Credential User (or Monitor ID) configured in WCC is a service account that does not have the necessary OS-level "Allow log on locally" or equivalent logon rights on the AutoSys Scheduler server.
Even if the password is correct, the operating system rejects the authentication request from the application.

Resolution

1. Identify the account being used for the ECLI credentials in WCC (typically under the Credentials tab).
2. Log in to the AutoSys Scheduler server (e.g., ####-p-####sch01) as an administrator.
3. Ensure the service account exists in the OS or LDAP and has been granted Logon Rights to the server.
4. Verify the user can successfully log in to the Scheduler server directly and execute AutoSys commands from the command line.
5. If using a service account, consider switching to a standard LDAP user to test if the "Logon Rights" are the primary blocker.
6. Once permissions are corrected, validate the credential in WCC and retest the ECLI.

 

Additional Information

Please see the section: Credentials Application

To speak with a customer representative or a Support Engineer see Contact Support. Scroll to the bottom of the page and click on the respective region.