7.12 Testing services between authorities (group task)

Testing of services of another authority or X-Road subsystem requires that a subsystem has opened their service in the security server for use by another subsystem.

Testing party in the role of service provider:

Open the service of your subsystem in the security server for another subsystem wishing to test your service.

This operation is further described in the ‘Learning material for X-Road security server administrator’:

21.4. Changing the access rights of a service: https://moodle.ria.ee/mod/book/view.php?id=353&chapterid=312

Testing party in the role of user of the service:

Testing service of another subsystem with SoapUI: first, you should know the parameters of the service of the subsystem to be tested: <DEVTRAINING_XX_A>, <serviceCode>,<serviceVersion>

Test as described below, ensuring that names of another subsystem and service are used as values of service header fields (not those of your own subsystem, as tested in chapter 6).

 

Add a new SoapUI project with the test subsystem parameters

  • Activate SoapUI
  • Create a new SOAP project, select in the menu: File -> New SOAP project
  • Enter data:
    • Initial WSDL: – enter the WSDL address of the test service via the security server in the form:

http://<turvaserveri_IP>/wsdl?xRoadInstance=ee-dev&memberClass=COM&memberCode=<XRD_MEMBER>&subsystemCode=<DEVTRAINING_XX_A>&serviceCode=<serviceCode>&version=v1

  • Select ‘OK’

Testing dataservice of another subsystem with SoapUI tool via X-Road security server:

  1. Change the endpoint field in SoapUI request window by entering the value: http://<security_server_IP_address>
  2. Change the header fields of the request in the request input window:
    1. Service/xRoadInstance: ee-dev (we operate in X-Road development instance)
    2. Service/ memberClass: COM
    3. Service/ memberCode: <XRD_MEMBER>
    4. Service/ subsystemCode: <DEVTRAINING_XX_A>
    5. Service/ serviceCode: <name of dataservice of another subsystem>
    6. Service/ serviceVersion: <version no of dataservice of another subsystem>
    7. protocolVersion: 4.0
    8. client /xRoadInstance: ee-dev (we operate in an X-Road development instance)
    9. client / memberClass: COM
    10. client / memberCode: <XRD_MEMBER>
    11. client / subsystemCode: <DEVTRAINING_XX_B>
Here, <XRD_MEMBER> is X-Road member code used for training, which is prepared before training. <DEVTRAINING_XX_A> and <DEVTRAINING_XX_B> are the subsystems of the service provider and the user prepared for the training, where XX represents the number of the participant; each participant uses a separate subsystem marked with their code.

3. Activate request by clicking the green activation button in the upper left corner.

4. Check the request response.

Testing the service of another subsystem with MISP2

Refresh the list of services of another subsystem and generate forms as described in clause 7.3.


Viimati muudetud: teisipäev, 9. mai 2017, 14:23