Bug 1474664 - NPE in HttpClient utility output
NPE in HttpClient utility output
Status: CLOSED DUPLICATE of bug 1461528
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: pki-core (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: RHCS Maintainers
Asha Akkiangady
Depends On:
  Show dependency treegraph
Reported: 2017-07-25 03:05 EDT by Geetika Kapoor
Modified: 2017-08-31 11:29 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2017-08-31 11:29:35 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Geetika Kapoor 2017-07-25 03:05:23 EDT
Description of problem:

NPE in HttpClient utility in below mentioned cases:

1. During cmc request if KRA is not reachable or is shutdown.
2. In case encryption is not set in KRA, so there is no common way to communicate between KRA and CA 

KRA rest info:

 CA rest info:

3. if key wrap algorithm is not set correctly, HttpClient fails with NPE.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1. This can be easily reproduce by shutting down KRA subsystem and try to perform any CMC archival test case.Example: self signed

Actual results:

1. NPE

Expected results:

Additional info:

Failures and NPE:

[root@pki1 certs_db]# HttpClient user-signed/HttpClient-cmc-crmf.self.cfg

Total number of bytes read = 3425
after SSLSocket created, thread token is NSS FIPS 140-2 User Private Key
client cert is not null
handshake happened
writing to socket
Total number of bytes read = 234

The response in binary format is stored in user-signed/cmc.self.Resp

[root@pki1 certs_db]# cat user-signed/cmc.self.Resp
The Certificate System has encountered an unrecoverable error.
Error Message:<BR>
Please contact your local administrator for assistance.
Comment 2 Christina Fu 2017-08-21 14:50:05 EDT
This looks like a duplicated bug for:
which has just been fixed.
Comment 3 Matthew Harmsen 2017-08-31 11:29:35 EDT

*** This bug has been marked as a duplicate of bug 1461528 ***

Note You need to log in before you can comment on or make changes to this bug.