#170 Don't report a spurious error if no SCEP pkiMessage is ready yet
Merged by rcritten. Opened by rcritten.
rcritten/certmonger bz1253009  into  master

On a brand new request in the state op_pkcsreq there will be no
pkiMessage to send yet because there is no CSR yet.

It correctly detects this state but also displays the message:

Error reading request.  Expected PKCS7 data containing a
PKCSReq pkiMessage, got nothing.

This is confusing if the request eventually succeeds.

It really only needs to report this if it is passed in a file name
to read the message from, otherwise silently return
CM_SUBMIT_STATUS_NEED_SCEP_MESSAGES.

The same issue existed in the op_get_cert_initial state.

https://bugzilla.redhat.com/show_bug.cgi?id=1253009

rebased onto 8a4778325f6c7ed030e203308a145c193c48c4b4

Pull-Request has been merged by rcritten

Metadata