Open pki-bot opened 3 years ago
Comment from mharmsen (@mharmsen) at 2014-03-31 20:25:28
Per CS/DS meeting of 03/31/2014 - 10.2 backlog.
Comment from mharmsen (@mharmsen) at 2014-06-04 20:08:11
[06/04/2014] - Moving to Milestone 10.3 due to schedule restrictions.
Comment from mharmsen (@mharmsen) at 2016-12-01 20:45:45
Per Offline Triage of 11/30/2016-12/01/2016: FUTURE - minor
Comment from rpattath (@rpattath) at 2017-02-27 14:01:22
Metadata Update from @rpattath:
Comment from edewata (@edewata) at 2017-06-12 17:18:12
As of PKI 10.4 the pki CLI will display the SSL alert received from the server which might be a sufficient solution.
Comment from edewata (@edewata) at 2017-06-12 17:18:13
Metadata Update from @edewata:
Comment from mharmsen (@mharmsen) at 2017-08-30 23:05:39
Metadata Update from @mharmsen:
Comment from mharmsen (@mharmsen) at 2017-10-25 19:04:40
[20171025] - Offline Triage ==> 10.6
Comment from mharmsen (@mharmsen) at 2017-10-25 19:04:44
Metadata Update from @mharmsen:
Comment from mharmsen (@mharmsen) at 2018-04-10 21:16:02
Per 10.5.x/10.6 Triage: 10.6
edewata: negative case
This issue was migrated from Pagure Issue #934. Originally filed by rpattath (@rpattath) on 2014-03-26 20:37:11:
[root@sigma dogtag]# pki -d /opt/rhqa_pki/certs_db -n CA_adminE -c redhat123 user-mod --fullName="Test user1" testuser1 ProcessingException: Unable to invoke request