Complete solution to AutoFirma errors and certificate detection

Si AutoFirma does not detect your certificateStart by checking where it's installed and whether it has the necessary private key for signing. An empty list could be due to the selected store, the profile used, a card that wasn't read correctly, or the requirements of the procedure.

It's also important to distinguish between two situations: AutoFirma might not display certificates when opened directly, or the problem might only appear when an online portal tries to use it. This difference helps determine whether you should check the certificate itself or the communication between the browser and the application.

Check if AutoFirma detects the certificate outside the process

Open AutoFirma from the applications menu, select a test document without sensitive information, and press SignCheck if your certificate appears on the selection screen.

If it appears and you can complete the signature, you've verified that AutoFirma can use it for that local transaction. This doesn't guarantee that every location will accept it, but it helps to isolate the certificate from a potential problem with the online process.

If it doesn't appear, check the available options for change the certificate storeDepending on the environment, you may be able to access the system storage, Firefox, a file, or a card such as the electronic ID card (DNIe).

If the certificate is only missing at a specific location, check which certificates that procedure accepts. Do not reinstall the entire application before identifying when the selection disappears.

Verify that you have the personal certificate with its private key.

A public certificate is not sufficient for signing. AutoFirma also needs access to the associated private key. Having an FNMT root certificate installed does not mean you have your personal signing certificate.

If you've changed computers or imported a copy, check which file you used:

• .p12 or .pfx: These are formats used to transport a copy of the certificate with its private key.
• .cer or .crt: They usually contain the public certificate and do not retrieve the private key you need on their own.

Also check the certificate holder, validity dates, and status. If it's expired or revoked, importing it again won't restore its validity.

Keep the backup password protected. Do not share that file, its password, or your electronic ID card PIN to request assistance.

If the certificate is in Firefox, check the correct profile.

Firefox can store personal certificates in its own store. Therefore, just because you can see them in the browser doesn't mean they are also imported into the system's certificate store.

Exporting them is not mandatory if AutoFirma can access the appropriate storage. First, check the profile used and the storage selection. Do not delete secondary profiles as a first attempt at repair.

If you need to transfer the certificate, open Firefox. Settings > Privacy and security > Certificates > Manage certificates. In Your certificatesSelect the staff and press Make a copy.

Protect the export with a password and keep the file .p12If the copy fails, do not randomly delete root certificates: check that you have selected your personal certificate and that you can access its private key.

Import the copy into Windows or macOS

In Windows, use the user certificate import wizard that AutoFirma will run and verify that the personal certificate is installed correctly.

On macOS, open Access to Keychains, select the keychain of login and uses File > Import Items to incorporate the copy .p12 o .pfxEnter your password and check the category My certificates.

Close and reopen AutoFirma after the import, and repeat the local test.

If you use the electronic ID card (DNIe), check the reader and the certificates.

The electronic ID card requires the device to be able to communicate with the card and use its keys. Check that the reader is connected, that it recognizes the document, and that you have the software compatible with your system.

Enter your electronic ID card (DNIe) before repeating the selection and enter your PIN when prompted. If you don't remember it, use the official change or recovery procedure instead of repeatedly trying different combinations.

The validity of the physical ID card and its certificates must be checked separately. It cannot be concluded that the chip is faulty simply because the document was issued before a certain year.

The police allow you to renew your electronic ID card (DNIe) certificate at DNIe Update Points. As long as the document remains valid, you can renew it using the same card. If the reader doesn't recognize the chip, consult the corresponding diagnostic tool before requesting a duplicate.

Update or restore AutoFirma if it fails from your browser.

Download AutoFirma from the Official Electronic Signature Portal and select the installer that corresponds to your system and architecture. On macOS, distinguish between Intel and Apple Silicon systems and check the compatibility information in the download.

Don't always choose the 32-bit version because of an SAF_09 error. That recommendation appears in an FNMT help document for certain cases, but the code alone doesn't demonstrate an architectural problem.

If AutoFirma works directly but fails when invoked from the browser, try Tools > Restore installationThe manual describes this repair as necessary to recover communication resources, for example, after installing Firefox or creating another profile.

If your official procedure instructs you to configure Firefox to trust the system's root certificates, apply that option during the restore process. This trust for communication does not replace the installation of your personal certificate.

In a typical Windows and macOS installation, You don't need to manually replace the internal Java.If you suspect the installation is corrupted, use the official installer before modifying application folders or libraries.

Interpret the SAF code before applying changes

The code provides guidance on the operation that has failed, but it doesn't always identify a single cause. These are some meanings found in the project's official code:

Code	Affected operation	What to check first
SAF_08	Access to the certificate store.	Storage, profile and card access, if used.
SAF_09	Execution of the signature.	Full message, certificate, and local proof.
SAF_11	Sending the result.	Communication with the service and network configuration.
SAF_15	Data decryption.	Context of the procedure and instructions for its support.
SAF_16	Data recovery.	Access to the service and proxy, if available.
SAF_19	Absence of certificates in the warehouse.	Available certificates and selected warehouse.

If you need assistance, please provide the AutoFirma version, operating system, browser, complete code, and the local test result. Also indicate whether you are using a software certificate or your electronic ID card (DNIe).

With this information, you can decide whether to review the certificate, repair the installation, or check the connection to the headquarters, without deleting profiles or reducing the security of the equipment as a first measure.