To begin, export the certificate signing request (CSR) created by pfSense by clicking on the 2nd icon of this request.
You will get a ".req" file.
In our case, we installed a certification authority on Windows Server, as well as the web interface of this CA.
Once installed, connect to the address "https://ca.informatiweb.lan/certsrv" as an administrator (or a user with the right to register a "Web Server" type certificate).
On your certification authority interface, click: Request a certificate.
Click: advanced certificate request.
Open the ".req" file (downloaded from the pfSense machine) with notepad.
Its content looks like this:
Plain Text
-----BEGIN CERTIFICATE REQUEST----- xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx... -----END CERTIFICATE REQUEST-----
Copy its contents by also copying the "BEGIN CERTIFICATE REQUEST" and "END CERTIFICATE REQUEST" lines.
Paste the certificate request into the "Base-64-encoded..." box of your CA's web interface on Windows Server and select the "Web Server" certificate template (or a custom template copied from it) .
In our case, we use our "Custom Web Server" certificate template.
Then click: Send.
Once the certificate is issued (delivered), select "Base 64 encoded" (to obtain the text or Linux version of the certificate) and click on "Download certificate" (to obtain only the certificate and not the certificate + that of the CA).
Now that you have obtained a valid certificate from your certificate authority (CA), you must import it into pfSense by modifying the certificate signing request previously created in pfSense.
To do this, in the "Certificates" tab, click on the pencil icon (to the right of your pending certificate request (external - signature pending)).
The certificate signing request (Signing request data) appears and pfSense asks you for the final certificate data.
Open the "certnew.cer" file downloaded previously from your certification authority under Windows Server with Notepad and copy its contents (which look like this).
Plain Text
-----BEGIN CERTIFICATE----- xxxxxxxxxxxxxxxxxxxxxxxx... -----END CERTIFICATE-----
Note: if the contents of this file are unreadable and do not look like this, it is because you downloaded the certificate in Microsoft format.
If your CA web page is still open, choose "Base 64 Encoded" and click "Download Certificate."
Otherwise, download OpenSSL and use the appropriate command to convert the ".cer" certificate (Microsoft) to ".pem" format (Linux).
Paste the contents of the certificate into the "Final certificate data" box and click: Update.
Your external certificate has been imported into the pfSense certificate store.
Finally, you must specify to pfSense which certificate it should use to secure its web interface.
To do this, go to: System -> Advanced.
In the "webConfigurator" section located at the top of the page, configure these 2 settings:
At the bottom of the page, click on: Save.
As you can see, the small triangle still appears for the moment on the padlock in the address bar.
Wait 20 seconds for the page to automatically refresh.
Now, the padlock appears without the small triangle.
If you click on this padlock, you will see this appear: Secure connection.
Important : Mozilla Firefox uses its own certificate store. If your SSL certificate is considered invalid (certificate issued by an unknown issuer), it is because you have not imported your CA's certificate into the Mozilla Firefox certificate store.
To fix the problem, in Mozilla Firefox, go to: Tools -> Settings -> Privacy and security -> "Certificates" section of the page -> Show certificates -> Authorities -> Import.
As expected, in our case, the SSL certificate used by pfSense is now verified by "InformatiWeb CA" (our certificate authority installed on Windows Server).
Firewall 6/25/2025
Firewall 5/15/2025
Firewall 6/18/2025
Firewall 5/23/2025
Pinned content
Contact
® InformatiWeb-Pro.net - InformatiWeb.net 2008-2022 - © Lionel Eppe - All rights reserved.
Total or partial reproduction of this site is prohibited and constitutes an infringement punishable by articles L.335-2 and following of the intellectual property Code.
No comment