Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device.
Atlassian uses cookies to improve your browsing experience, perform analytics and research, and conduct advertising. Accept all cookies to indicate that you agree to our use of cookies on your device. Atlassian cookies and tracking notice, (opens new window)
TSL-Editor: SMP workflow (for configurations management, powered by e-SENS)
Aug 01, 2016
1. Introduction
Under the "File" option in the menu bar, you can find the "SMP" option, which will open a new window where you can perform all tasks related to the new central services based on Service Metadata Publishing (SMP).
In this new window, you'll be able to:
Generate SMP files signed by the scheme operator from a previously created TSL file (green rectangle in the picture below);
Upload SMP files signed by a scheme operator to an SMP server (yellow rectangle in the picture below).
2. Generate SMP files signed by the scheme operator from a previously created TSL file
To generate signed SMP files from a TSL file you should:
Choose the previously created TSL file;
Choose the XML file of the International Search Mask of your country;
Choose the folder where SMP files will be stored;
Check the "Sign SMP files" checkbox;
Choose a keystore (JKS file) and provide its password;
Enter the alias and password of the private key that will be used to sign the files;
Click on the "Transform" button.
A confirmation dialog will pop-up, prompting the scheme operator to confirm that he wants to apply his signature (ideally, a QES) to the content of the different SMP files:
Note: Currently, only XML Digital Signatures are supported. Further discussion/development is needed before being able to apply a XaDES.
After confirmation, the files will be generated. As a result, a folder named CC (with "CC" being the uppercase two-letter country code of your country, e.g., LU for Luxembourg, MT for Malta, etc) can now be found under the chosen output folder, containing the SMP files for the services declared by the TSL file. Following is a list of possible files that may be found, depending on the TSL file configuration:
Identity_Provider_CC.xml
International_Search_Mask_CC.xml
Order_Service_CC.xml
Patient_Identification_Service_CC.xml
Patient_Service_CC.xml
VPN_Gateway_A_CC.xml
VPN_Gateway_B_CC.xml
Consent_Service_Put_CC.xml
Consent_Service_Discard_CC.xml
Dispensation_Service_Initialize_CC.xml
Dispensation_Service_Discard_CC.xml
The signature that is applied is the scheme operator's and it is stored under the Endpoint/Extension element of the file. So, even if those SMP files contain a Signature element, they are not SignedServiceMetadata but just ServiceMetadata (see following sample file). The SignedServiceMetadata will be created when the SMP server applies its signature to the uploaded file.
3. Upload SMP files signed by a scheme operator to an SMP server
Before trying to upload SMP files, you need to request the SMP administrator to register your country in the SMP server, providing the following identificator:
ehealth-actorid-qns::urn:ehealth:<cc>:ncpb-idp
<cc> should be replaced by the lowercase two-letter code for your country (e.g., for Malta it'd be like: ehealth-actorid-qns::urn:ehealth:mt:ncpb-idp). Upon request, you'll be provided with your username and password.
It's only possible to upload SMP files representing ServiceMetadata, not SignedServiceMetadata. The latter is created by the SMP server itself by applying its own signature to the file.
To upload the generated SMP files to an SMP server you should:
Choose the folder where the SMP files are stored;
Select the desired SMP files to upload;
Enter the SMP server URL in the form of "http://...";
Provide the username and password of an SMP user with upload privileges;
If the upload is successful, a dialog must be displayed showing the status of the operation as well as URLs pointing to the country's available resources in the SMP server. You'll be provided the following resources:
Service Group: resource that contains the list of service metadata for a country;
Signed Service Metadata: resources that describe each of the services published by a country.
This resources can be retrieved in a RESTful way by means of an HTTP GET operation (you can simply paste the URL in the browser).
The SMP files retrieved from the server MUST have 2 signatures:
1) The remote scheme operator signature (applied in the Endpoint/Extension element);
2) The SMP server signature, applied to the ServiceMetadata (making it a SignedServiceMetadata).