This new option will allow copies to incorporate this URL by default, as well as an identifier code for the còpia, which allows its download, from the item available to users of the Portal of Transparència of the AOC.
Copy signing mechanisms: available options
As a mechanism for signing copies, the service Còpia It allows you to configure different scenarios according to the needs of the user entity, either through a qualified official or through automated administrative action:
Electronic signature using secure verification codes (hereinafter CSV)
Electronic signature using a digital certificate installed in the local certificate store of the entity user's computer
Electronic signature using an electronic seal certificate assigned to the AOC Consortium (option available to entities that are eligible to use the AOC Consortium Digital Certification Service and that have requested a transferred electronic seal certificate).
In the case of using the first option (add to the còpia a secure verification code (CSV) of the original), until now, the service Còpia allowed to add a URL document verification service, specific to each user entity, if available and an identifier of the còpia authentic, which could either generate its own Còpia so that the entity could then configure it in its CSV service, or the user could add it manually at the time of making the còpia authentic. This identifier is used to download the original document from the indicated url. From now on, therefore, there will be the possibility of adding to the authentic copies made, the address of the service of Document verification using Secure Verification Code (CSV) that incorporates the Portal Transparència of the AOC Consortium.
Other technical improvements
Likewise, in this version change of the service, it is also taken advantage of to add some technical modifications, related to the adaptation of the applications hosted on theEACAT current, for the future change towards theEACAT 3.0. It should be noted that these modifications imply that, temporarily, service permissions Còpia, can only be managed from the configuration section of the current EACAT and not from the user management of the new EACAT.
From the screen below, you can add and remove service permissions (Service Administration and Copy Management) whose names have also been standardized, adapting them to the rest of AOC services and inclusive language.
