Certificates with no SAN result in 500 about django-ca HOT 5 CLOSED

Hi, thanks for the report. This is when you want to add a new certificate? Can you share a CSR that causes the error, as well as your Python and Django versions!

from django-ca.

The cert is successfully signed but then I can't view it, I get a server 500 in the admin interface.

Python: 3.5.2
Django-CA: 1.7.0-24-gcc8924f
cert.txt
csr.txt

from django-ca.

I am running into a similar prb - only not with altnames, which are handled handsomely - but with SignedCertificateTimestamp objects (OID 1.3.6.1.4.1.11129.2.4.2) and CertificatePolicies. I patched it in models.py as per attachment (requirements.txt is also attached). Basically I am concatenating repr(foo) any time an handler for OID foo cannot be found. Ugly, but it keeps 500 errors at bay.

requirements.txt
unknownOID-patch.txt

from django-ca.

Ok, so I ran into the very same problem (I imported letsencrypt's intermediate X3 cert). Getting around it required adding sukjectAltName to ignored fields and changing the return value of the corresponding method in X509MixIn (see attachment)

bugdiff.txt

from django-ca.

@MonsieurCellophane nice looking patch, can you create a pull request?

from django-ca.