Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Relocate SSNv2 range objects for new CA instances #4885

Merged
merged 2 commits into from
Oct 31, 2024
Merged

Relocate SSNv2 range objects for new CA instances #4885

merged 2 commits into from
Oct 31, 2024

Commits on Oct 31, 2024

  1. Relocate SSNv2 range objects for new CA instances 

    pkispawn has been modified to create ou=ranges subtree for SSNv1
and optionally ou=ranges_v2 subtree for SSNv2 if it's enabled for
new CA instances. The pki-server <subsystem>-db-init and
<subsystem>-range-update commands have been updated to use the
proper subtree to store the range objects. Hard-coded subtrees in
the create.ldif have been removed.

Similar changes are made to KRA as well, but since there are no
tests for KRA with SSNv2 it's not officially supported yet.
    @edewata
    edewata committed Oct 31, 2024
    Configuration menu
    Copy the full SHA
    b602685 View commit details
    Browse the repository at this point in the history

  2. Update test scripts for SSNv2 

    The test scripts have been updated to use ou=ranges_v2 subtree
for SSNv2 range objects.
    @edewata
    edewata committed Oct 31, 2024
    Configuration menu
    Copy the full SHA
    94fcf40 View commit details
    Browse the repository at this point in the history