#934 pki user-mod authenticating using an expired cert should fail with a more descriptive error message
Closed: migrated 3 years ago by dmoluguw. Opened 10 years ago by rpattath.

[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


Per CS/DS meeting of 03/31/2014 - 10.2 backlog.

[06/04/2014] - Moving to Milestone 10.3 due to schedule restrictions.

Per Offline Triage of 11/30/2016-12/01/2016: FUTURE - minor

Metadata Update from @rpattath:
- Issue set to the milestone: FUTURE

7 years ago

As of PKI 10.4 the pki CLI will display the SSL alert received from the server which might be a sufficient solution.

Metadata Update from @edewata:
- Custom field reviewer adjusted to ''
- Custom field version adjusted to ''
- Issue close_status updated to: None

6 years ago

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.5 (was: FUTURE)

6 years ago

[20171025] - Offline Triage ==> 10.6

Metadata Update from @mharmsen:
- Issue set to the milestone: 10.6 (was: 10.5)

6 years ago

Per 10.5.x/10.6 Triage: 10.6

edewata: negative case

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/1500

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Metadata Update from @dmoluguw:
- Issue close_status updated to: migrated
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata