Smarts NCM: Push job fails when "Prompt User" & "Run Upon Operator's Initiation" are selected; Error: Failed to decrypt job credential
search cancel

Smarts NCM: Push job fails when "Prompt User" & "Run Upon Operator's Initiation" are selected; Error: Failed to decrypt job credential

book

Article ID: 331146

calendar_today

Updated On:

Products

VMware Smart Assurance

Issue/Introduction

Symptoms:


Unable to perform push jobs

We use Prompt User under Scheduled Credentials Configuration Option.  There are no issues when using Run Upon Approval method, the issue occurs when we select Run Upon Operator initiation. Both methods are available under Prompt User Configuration.






Environment

VMware Smart Assurance - NCM

Cause

The reason this happens is because it's not able to decrypt job credentials and send data properly to DS. Following are the errors seen in powerup.log.

2015-03-18 11:25:35,877 DEBUG [com.powerup.configmgr.deviceservice.daemon.util.CryptoHelper] (WorkManager(2)-6) Using AES
2015-03-18 11:25:35,877 ERROR [com.powerup.configmgr.server.services.scheduler.impl.JobCredentialWorker] (WorkManager(2)-6) Failed to decrypt job credential
2015-03-18 11:25:35,878 ERROR [com.powerup.configmgr.server.services.scheduler.impl.SchedulerDataStore] (WorkManager(2)-6) Fail to retrieve job credential
com.powerup.common.exception.CMBusinessException: 
at com.powerup.configmgr.server.services.scheduler.impl.JobCredentialWorker.decryptMap(JobCredentialWorker.java:127)

or

2015-03-24 23:40:46,615 ERROR [com.powerup.configmgr.server.services.scheduler.impl.PushPerformer] (WorkManager(2)-8) Cannot decrypt user name
javax.crypto.BadPaddingException: Given final block not properly padded

Resolution

The issue exists from NCM 9.1 to NCM 9.4 HF1. 

We have identified the issue as a bug and the fix will be released as part of NCM 9.4 upcoming patch.