Remove last vestiges of Unified CRL #272
Labels
bug
Something isn't working
Milestone
Comments
cipherboy
added a commit
to cipherboy/openbao
that referenced
this issue
Jun 15, 2024
In Vault Enterprise's split-storage clustering (Performance Secondary), the PKI engine needed a way of maintaining a single, unified CRL across all Perf Secondary clusters and accepting revocations given to any cluster for certs stored on any other cluster. The combination of Unified CRLs and Revocation Queues solved this problem for Vault Enterprise, but the code largely lived in Vault Community. Since OpenBao lacks these clustering semantics and is unlikely to add them, remove this code. Resolves: openbao#272 Signed-off-by: Alexander Scheel <[email protected]>
cipherboy
added a commit
to cipherboy/openbao
that referenced
this issue
Jun 20, 2024
In Vault Enterprise's split-storage clustering (Performance Secondary), the PKI engine needed a way of maintaining a single, unified CRL across all Perf Secondary clusters and accepting revocations given to any cluster for certs stored on any other cluster. The combination of Unified CRLs and Revocation Queues solved this problem for Vault Enterprise, but the code largely lived in Vault Community. Since OpenBao lacks these clustering semantics and is unlikely to add them, remove this code. Resolves: openbao#272 Signed-off-by: Alexander Scheel <[email protected]>
cipherboy
added a commit
to cipherboy/openbao
that referenced
this issue
Jun 20, 2024
In Vault Enterprise's split-storage clustering (Performance Secondary), the PKI engine needed a way of maintaining a single, unified CRL across all Perf Secondary clusters and accepting revocations given to any cluster for certs stored on any other cluster. The combination of Unified CRLs and Revocation Queues solved this problem for Vault Enterprise, but the code largely lived in Vault Community. Since OpenBao lacks these clustering semantics and is unlikely to add them, remove this code. Resolves: openbao#272 Signed-off-by: Alexander Scheel <[email protected]>
cipherboy
added a commit
to cipherboy/openbao
that referenced
this issue
Jul 10, 2024
In Vault Enterprise's split-storage clustering (Performance Secondary), the PKI engine needed a way of maintaining a single, unified CRL across all Perf Secondary clusters and accepting revocations given to any cluster for certs stored on any other cluster. The combination of Unified CRLs and Revocation Queues solved this problem for Vault Enterprise, but the code largely lived in Vault Community. Since OpenBao lacks these clustering semantics and is unlikely to add them, remove this code. Resolves: openbao#272 Signed-off-by: Alexander Scheel <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
See e.g., https://github.com/openbao/openbao/blob/main/builtin/logical/pki/path_fetch_issuers.go#L1214-L1223 -- and similar locations.
There's many places where cross-cluster Unified CRLs still exist in the code base, despite being a Vault Enterprise (and in particular, Performance Secondary) scenario. We should remove these, prior to GA.
The text was updated successfully, but these errors were encountered: