dogtagpki / pki

The Dogtag Certificate System is an enterprise-class Certificate Authority (CA) which supports all aspects of certificate lifecycle management, including key archival, OCSP and smartcard management.
https://www.dogtagpki.org
GNU General Public License v2.0
365 stars 135 forks source link

CLI options for HTTP connection #2034

Open pki-bot opened 4 years ago

pki-bot commented 4 years ago

This issue was migrated from Pagure Issue #1475. Originally filed by edewata (@edewata) on 2015-07-09 23:37:50:


Currently if the CLI does not receive a response from the server (e.g. incorrectly using SSL port for non-secure connection) it will wait until timeout (1 minute) and retry the connection three more times, so the total will be 4 minutes.

$ pki -c Secret123 -n caadmin kra-user-cert-add pkidbuser --serial 0x1
ERROR: CA subsystem not available
CA server URI [http://kra.example.com:8080]: http://ca.example.com:8443
Jul 09, 2015 5:06:15 PM org.apache.http.impl.client.DefaultHttpClient tryExecute
INFO: I/O exception (org.apache.http.NoHttpResponseException) caught when processing request to {}->http://ca.example.com:8443: The target server failed to respond
Jul 09, 2015 5:06:15 PM org.apache.http.impl.client.DefaultHttpClient tryExecute
INFO: Retrying request to {}->http://ca.example.com:8443
Jul 09, 2015 5:07:15 PM org.apache.http.impl.client.DefaultHttpClient tryExecute
INFO: I/O exception (org.apache.http.NoHttpResponseException) caught when processing request to {}->http://ca.example.com:8443: The target server failed to respond
Jul 09, 2015 5:07:15 PM org.apache.http.impl.client.DefaultHttpClient tryExecute
INFO: Retrying request to {}->http://ca.example.com:8443
Jul 09, 2015 5:08:15 PM org.apache.http.impl.client.DefaultHttpClient tryExecute
INFO: I/O exception (org.apache.http.NoHttpResponseException) caught when processing request to {}->http://ca.example.com:8443: The target server failed to respond
Jul 09, 2015 5:08:15 PM org.apache.http.impl.client.DefaultHttpClient tryExecute
INFO: Retrying request to {}->http://ca.example.com:8443
NoHttpResponseException: ca.example.com:8443 failed to respond

There should be options to change this behavior:

Proposed milestone: 10.3

pki-bot commented 4 years ago

Comment from mharmsen (@mharmsen) at 2015-07-13 23:55:15

Per CS/DS meeting of 07/13/2015: 10.3

pki-bot commented 4 years ago

Comment from edewata (@edewata) at 2017-02-27 13:58:41

Metadata Update from @edewata: