This translation has been done automatically by means of the Automatic Translation Platform of the General Secretariat of Digital Administration (PLaTa) and may contain errors or inaccuracies in the interpretation of the content.

01:30:442025-09-29

Certificates

AEMPS HEADQUARTERS > Certificates
How to obtain a Digital Certificate?

To obtain a digital certificate go to the website of the CERES platform of the National Currency and Stamp Factory (http://www.cert.fnmt.es/) and choose one of the two options that appear at the top:

Logotipo de Ceres
Imagen de acceso a Certificado de Usuario con DNI
Imagen de acceso a Certificado de Usuario

The link on the left will only work if you have an electronic DNI (with built-in chip) and have the necessary software installed on your PC to be able to use it. Otherwise, click on the link on the right: “Get the user certificate”.

What is a Digital Certificate?

An electronic or digital certificate is an electronic document in which the identity of the holder is collected and which can be used by the holder both to sign other documents electronically and to identify himself in a computer system, such as a web page.

Digital certificates are issued and signed electronically by a certification service provider, who will be responsible for ensuring that the identity collected in the certificate corresponds to the real identity of its holder. There are numerous digital certificate providers on the market. The AEMPS recognizes the certificates issued by allcertification service providers recognised by the Ministry of Industry, Energy and Tourism. To obtain a certificate, you must contact one of these providers. The most widespread certificates, at least in the General Administration of the State, are those issued free of charge by theNational Currency and Stamp Factory (FNMT).

Both natural and legal persons may possess digital certificates. In the case of legal persons, the certificates will be issued in the name of their administrators, legal representatives or volunteers with sufficient power for this purpose.

There are basically two types of digital certificates:

  • Those that have a computer file as their support. To use these types of certificates, you must first install them in the computer application that is going to be used to sign or to identify the holder of the certificate. The standard certificates issued by the FNMT are of this type. To access AEMPS telematics applications using an FNMT certificate, the certificate must be installed in a web browser that supports 128-bit symmetric encryption, such as MS Internet Explorer and Mozilla Firefox.
  • Those who have a cryptographic card as their support, such as theElectronic ID. To use these certificates you need to have a card reader installed on your PC. An FNMT certificate can also be installed on a cryptographic card, although the card must be purchased separately.
Certificate Verification System

According to article 6.1 d) of Royal Decree 1671/2009, of 6 November 2009, partially implementing Law 11/2007, of 22 June, on electronic access for citizens to public services, every electronic office will have a verification system of the certificates of the office, which will be accessible directly and free of charge.

In order to verify the validity of the certificate of the electronic headquarters of the Spanish Agency for Medicines and Health Products (AEMPS), the Ministry of Finance and Public Administration offers, directly and free of charge, theVALIDe Platform.

Supported Electronic Signature Systems

The Spanish Agency for Medicines and Health Products (AEMPS), allows, in the different electronic services made available to citizens and in order to guarantee their secure identification, the use of the following electronic signature systems, according to the provisions of article 13.2 of Law 11/2007, of 22 June, on citizens’ electronic access to public services:

  • Electronic signature systems incorporated into the National Identity Document, for natural persons.
  • Advanced electronic signature systems, including those based on recognized electronic certificate, admitted by the Public Administrations.
  • Other electronic signature systems, such as the use of agreed keys in a previous registry as a user, the provision of information known to both parties or other non-cryptographic systems, in the terms and conditions that in each case are determined.
Related links
Problems with the Digital Signature
  • Guides of the Ministry of Industry Tourism and Commerce on how to configure a digital certificate of the FNMT in browsers:
Problems with the digital signature in 64-bit architectures
  • It is recommended to use a 32-bit browser in accessing AEMPS applications that require a digital signature when accessing from windows 7 with 64 bits.

    Currently, two signature clients are distributed in the AEMPS applications:

    • CAPICOM:This signature client is no longer supported in Windows 7. It can be manually installed and used in the 32-bit browser by following the steps indicated in:http://www.cert.fnmt.es/show.php?o=faq&id=194&mode=show(Following the same steps as in Windows Vista).
    • @signature:This client will replace CAPICOM in the AEMPS applications in the future, however there is a bug in the latest version of the JAVA virtual machine, specifically version v1.6.0_24, which causes an erroneous behavior in the execution of the MPTAP Signature Client, depending on the type of installation that has been performed. As of version 3.1 of the Signature Client (27-Oct-2010), there are two types of deployment:
      • Classic Deployment:To be able to execute it, it is necessary to have performed a previous installation that basically consists of copying the necessary resources locally so that in each execution it is not necessary to access the resources via HTTP and therefore it is possible to invoke them locally, since after all it is an application that is executed locally (applet). It has been verified that JAVA JRE update v1.6.0_24 includes security restrictions that cause a local applet error when invoked as the Signature Client does using the classic deployment. ORACLE SDN (SUN Developer Network) has included and recognized this bug, 7020285 (http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=7020285).
      • JNLP Deployment:Automatic deployment pre-configured. Given the bug detected in the classic deployment, @firm strongly recommends the use of this alternative. For earlier versions of JAVA or 64-bit architectures, deployment via this path is not possible, so the installer component will automatically perform the classic deployment automatically.

    If you would like to find more information related to this website,Please use the search box at the top of the page.