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.

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

Bug2190283-AddCRLServlet-SEVERE-NOT-SUPPORTED-messages #4427

Merged

Commits on Apr 27, 2023

  1. Bug2190283-AddCRLServlet-SEVERE-NOT-SUPPORTED-messages

    This patch fixes the following issue:
    It appears that the following parameter in ca's CS.cfg is set to true
    by default:
    ca.publish.rule.instance.ocsprule-ccrsa-1-rhcs10-example-com-32443.enable
    which triggers the CA to attempt publishing of its CRLs directly
    from CA->OCSP and causing the following SEVERE error messages:
    
    SEVERE: CRL issuing point CN=CA Signing Certificate, nott found.
    
    The CA->OCSP direct push of CRLs appears to not be working.
    CA->ldap publishing (and ocsp pulling from ldap) is working and
     should be used instead.
    
    In addition, this patch also fixes it so that the following will no
    longer appear (it has no reason to. See bug description for explanation):
    [CRLIssuingPoint-MasterCRL] WARNING: LdapSimpleMap: crl issuer dn:...
    org.mozilla.jss.netscape.security.x509.X509CRLImpl cannot be cast to java.security.cert.X509Certificate
    
    fixes https://bugzilla.redhat.com/show_bug.cgi?id=2190283
    ladycfu committed Apr 27, 2023
    Configuration menu
    Copy the full SHA
    9e36938 View commit details
    Browse the repository at this point in the history