When PKI console connects to PKI server it creates a new SSL session. If the PKI console is left idle, the SSL session will expire after some time. In that case PKI console should display an error dialog and then exit to the system. The session can be resumed by restarting the PKI console.
Metadata Update from @edewata: - Custom field component adjusted to General - Custom field feature adjusted to '' - Custom field origin adjusted to Community - Custom field proposedmilestone adjusted to '' - Custom field proposedpriority adjusted to '' - Custom field reviewer adjusted to '' - Custom field type adjusted to defect - Custom field version adjusted to '' - Issue priority set to: critical - Issue set to the milestone: 10.4
https://review.gerrithub.io/357755 Added session timeout for PKI console. https://review.gerrithub.io/357756 Updated default SSL connection timeout.
Pushed to master:
Metadata Update from @edewata: - Issue assigned to edewata - Issue close_status updated to: fixed - Issue set to the milestone: 10.4.3 (was: 10.4) - Issue status updated to: Closed (was: Open)
Metadata Update from @mharmsen: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1446875
Issue linked to Bugzilla: Bug 1446875
Metadata Update from @mharmsen: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1446875, https://bugzilla.redhat.com/show_bug.cgi?id=1446877 (was: https://bugzilla.redhat.com/show_bug.cgi?id=1446875)
The client cert auth in PKI console is no longer working because of commit 70520762af91b5dab41415028b1a6bfe66d42628.
Metadata Update from @edewata: - Issue set to the milestone: 10.4 (was: 10.4.3) - Issue status updated to: Open (was: Closed)
Fixed the regression in master:
Metadata Update from @edewata: - Issue set to the milestone: 10.4.7 (was: 10.4)
Metadata Update from @edewata: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Metadata Update from @mharmsen: - Issue set to the milestone: 10.4.8 (was: 10.4.7)
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/2763
If you want to receive further updates on the issue, please navigate to the GitHub issue and click on Subscribe button.
Subscribe
Thank you for understanding, and we apologize for any inconvenience.
Login to comment on this ticket.