You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@ozone.apache.org by "István Fajth (Jira)" <ji...@apache.org> on 2022/10/24 15:23:00 UTC

[jira] [Updated] (HDDS-7387) Re-organize existing certificate revocation logic in the current codebase

     [ https://issues.apache.org/jira/browse/HDDS-7387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

István Fajth updated HDDS-7387:
-------------------------------
        Parent:     (was: HDDS-7333)
    Issue Type: Improvement  (was: Sub-task)

> Re-organize existing certificate revocation logic in the current codebase
> -------------------------------------------------------------------------
>
>                 Key: HDDS-7387
>                 URL: https://issues.apache.org/jira/browse/HDDS-7387
>             Project: Apache Ozone
>          Issue Type: Improvement
>            Reporter: István Fajth
>            Assignee: István Fajth
>            Priority: Major
>
> In the current codebase we have certificate revocation related logic, that has to be organized around the new way of distributing the CRL.
> The aim here is to cut off everything that is not required to provide the CRL on the WebUI, but leaves the functionality to share the fact of revocation between SCMs, and to ensure that all SCMs are able to provide a consistent view of the CRL itself signed by the subordinate CA certificate the SCM has.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@ozone.apache.org
For additional commands, e-mail: issues-help@ozone.apache.org