Just installed CA Process Automation, no longer able to log in
search cancel

Just installed CA Process Automation, no longer able to log in

book

Article ID: 18445

calendar_today

Updated On:

Products

CA Workload Automation AE - Business Agents (AutoSys) CA Workload Automation AE - Scheduler (AutoSys) Workload Automation Agent CA Process Automation Base

Issue/Introduction

ITPAM was just installed. Immediately after the installation logging in was successful, but using the same username and password no longer allows logging in. Error message states invalid username or password but nothing has changed


When you install ITPAM, there is a field on the Embedded Entitlements Manager (EEM) Security Settings screen with the name of Default Active Directory Domain:


Figure 1




Environment

ITPAM 4.2 and later releases with an EEM connected to an Active Directory server

Cause

One common cause for this us setting a domain in the Active Directory Default Domain field during installation. 

This field is only used if EEM is setup for multiple Active Directory domains

This field is used to indicate which of the multiple domains will be considered the default.


If a value was entered for this field during installation, but EEM is not connected to AD using multiple AD domains, the your very first login to ITPAM will be successful. However subsequent login attempts will fail with the error message "Invalid username or password"

Resolution

To remove the value and re-enable logins to ITPAM, please do the following:

  1. Log on to the ITPAM server and stop the orchestrator service 

  2. Open the Oasisconfig.properties file in a text editor. This file is locate under \CA\PAM\server\c2o\.config 

  3. Search for the word "active" - no quotes. On approximately line 66 you will see the parameter
    oasis.security.activeDirectory.defaultDomain=yourDomain

  4. Change line 66 so that "yourDomain" is deleted and the line now reads as
    oasis.security.activeDirectory.defaultDomain=

  5. Save the changes, close the file, restart the ITPAM orchestrator service

You will now be able to log in to ITPAM.

Attachments