Custom Connector - com.ca.pam.extensions.framework.util.ExtensionEncryption.init Encryption Key does not exist

book

Article ID: 192102

calendar_today

Updated On:

Products

CA Privileged Access Manager (PAM) CA Privileged Access Manager - Cloakware Password Authority (PA) PAM SAFENET LUNA HSM CA Privileged Access Manager - Server Control (PAMSC)

Issue/Introduction

Configured Custom Connector 3.3 but catalina log reports "Encryption Key does not exist"

02-Jun-2020 19:23:59.798 INFO [main] org.apache.catalina.startup.HostConfig.deployWAR Deploying web application archive [C:\Program Files\Apache Software Foundation\Tomcat 9.0_Tomcat91\webapps\capamef.war]
02-Jun-2020 19:24:00.799 INFO [main] org.apache.jasper.servlet.TldScanner.scanJars At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
02-Jun-2020 19:24:00.845 INFO [main] com.ca.pam.extensions.framework.util.ExtensionFrameworkContextListener.contextInitialized Initializing framework context listener.
02-Jun-2020 19:24:00.845 INFO [main] com.ca.pam.extensions.framework.util.PropertiesLoader.loadProperties PropertiesLoader loading properties file: /extension_framework.properties
02-Jun-2020 19:24:00.861 INFO [main] com.ca.pam.extensions.framework.util.PropertiesLoader.loadProperties PropertiesLoader loaded properties successfully
02-Jun-2020 19:24:00.861 INFO [main] com.ca.pam.extensions.framework.util.ExtensionEncryption.init Encryption is enabled
02-Jun-2020 19:24:00.861 INFO [main] com.ca.pam.extensions.framework.util.ExtensionEncryption.retrieveEncryptionKey Retrieve the encryption key
02-Jun-2020 19:24:00.861 SEVERE [main] com.ca.pam.extensions.framework.util.ExtensionEncryption.init Encryption Key does not exist

Cause

This usually happens on Windows environment.
extension_framework.properties file has invalid "extension.keystore.file" value.
As a result, capamef application fails to access the custom connector keystore hence the "Encryption Key does not exist"

Environment

Release : 3.3

Component : PRIVILEGED ACCESS MANAGEMENT

Resolution

Bad sample


Good sample:


note the "\\" instead of "\" in the filepath.

Attachments