How to Resolve Failed to Decrypt Private Key Error in Embedded Entitlements Manager.
search cancel

How to Resolve Failed to Decrypt Private Key Error in Embedded Entitlements Manager.

book

Article ID: 18487

calendar_today

Updated On:

Products

CA Directory CA IT Asset Manager CA Software Asset Manager (CA SAM) ASSET PORTFOLIO MGMT- SERVER CA Service Management - Service Desk Manager CA Workload Automation AE - Business Agents (AutoSys) CA Workload Automation AE - Scheduler (AutoSys) Workload Automation Agent CA Process Automation Base

Issue/Introduction

Follow these steps to resolve the 'Failed to decrypt private key from iAuth.conf' when setting up EEM in a failover environment.

Environment

Release:
Component: ETEIAM

Resolution

  1. Navigate to the /etc/hosts file in your environment.

  2. Open the file for editing.

  3. Locate the line with the IP address of the server.

  4. Edit the line and place the hostname before the FQDN (Fully Qualified Domain Name)

    Example:

    192.168.0.1 <Hostname>

  5. Save the /etc/hosts file.

  6. Proceed with steps to enable EEM failover.

The reason for this change is as follows:

We store the public and the private key pair in iAuthority.conf. Since the private key is confidential it is stored in a munged format. The seed formatting is the hostname, not the FQDN name.