Reset Search
 

 

Article

KB40495 - Certificate authentication using command-line launcher fails with Pulse Secure Desktop client (5.2R5 to 5.2R7)

« Go Back

Information

 
Last Modified Date3/17/2017 2:34 PM
Synopsis
This article describes an issue where certificate authentication using command-line launcher fails with Pulse Secure Desktop Client (5.2R5 to 5.2R7).
Problem or Goal
Upon upgrading the Pulse Secure Desktop client to 5.2R5 / 5.2R6 / 5.2R7, certificate authentication using command-line launcher fails with the following error message:
 
Invalid Client Certificate

In the Pulse client debug logs, following messages will be logged:
Pulse_Launcher  jcSelectionRule.cpp:345 - 'JamCertLib' Certificate XXXX does not meet the 
required 'is trusted by the server' condition, skipping it (rank 0)
Pulse_Launcher  jamCert.cpp:405 - 'JamCertLib' No client certificate satisfied the minimal requirements.
Pulse_Launcher  launcher.cpp:381 - 'PulseLauncher::connectIVE' jcCertUtils::GetClientCertificates() failed
Pulse_Launcher  launcher.cpp:243 - 'PulseLauncher::exec' connect/disconnect failed: 6
Pulse_Launcher  main.cpp:121 - 'Pulse Launcher' launcher.exec() 6
Cause
This issue occurs due to a bug introduced in Pulse Secure Desktop client version 5.2R5 to support automatic certificate selection.

Affected versions:

Pulse Secure Desktop client version 5.2R5 to 5.2R7
Solution
This issue will be resolved in Pulse Secure Desktop client version 5.2R8 (tentative for Q2 2017).  KB will be updated once release dates are available. 
Related Links
Attachment 1 
Created ByLokesh T K

Feedback

 

Was this article helpful?


   

Feedback

Please tell us how we can make this article more useful.

Characters Remaining: 255