FreeNAS

The CSR does have the signed certificate associated. The certificate information is populated to the System->Certificates page.

Can you elaborate on what "The CSR does have the signed certificate associated." means?

All I want to know is that is it still a cert signing req or a signed cert?

It would help if you wrote down the exact steps you took to get to this point.

Thanks

'gainesville' is a signed certificate.

I created the CSR on the Certificates tab.
I edited the CSR to copy the base 64 request.
I signed the base 64 request externally adding subject alternative names of a short name, fully qualified domain name, and IP address.
I pasted the resulting certificate into the CSR and saved it.
The certificates page then showed the certificate as I pasted in my last edit.
I navigated to system General but the certificate was not available in the certificate dropdown field on that page.

I have restarted nginx and Django but this did not help.

I encountered this as well. Here is what I did:

• Created a CA
• Created a certificate signed by internal CA from above
• Turned on HTTPS
• Created a 4096bit CSR under certificates tab
• Sent CSR to incommon and got a certificate back
• Opened certificate and pasted in certificate
• New certificate does not show in general tab as an option (but internal-ca signed one does)

Then I exported the certificate and private key, saved them, and used 'import certificate' to import them again under a new name. That worked (And is a work-around for anyone encountering this bug)

Running FreeNAS-9.10.2-U2 (e1497f2)

Confirmed that the workaround posted by Alex is working. Exported key and certificate. Deleted. Imported. And was able to assign the certificate for https.

I ran into the same issue. I created a CSR from FreeNAS, edited the cert to obtain the CSR, had that CSR signed by my CA, pasted the resultant certificate from my CA into the certificate field in FreeNAS and observed that the certificate was not available to assign to the GUI (even though it in /etc/certificates.) After exporting the newly created certificate and private key and re-importing them (with a new identifier), the new identifier was available in the GUI for use (and the original cert still was not.)

I am on 11.0 RC3. My CA is a Windows Server CA using a copy of the default Web Server template that has been modified to allow key export.

Interestingly if I dump out the crt files in /etc/certificates for both the original certificate and the imported certificate I get the same decoded file:

openssl x509 -in original.crt -text > c1.txt
openssl x509 -in reimported.crt -text > c2.txt
diff c1.txt c2.txt

I have resumed my work, and shall work on this ticket this week (i.e. today and tmrw)

@Release Engineer: https://github.com/freenas/freenas/pull/244 PR for stable branch.