Technical Specification
Version: 1.17
Doc. ID: PR-MSERV
| Date | Version | Description | Author |
|---|---|---|---|
| 19.08.2015 | 0.1 | Initial version | Martin Lind |
| 28.08.2015 | 0.2 | Added comments and made editorial changes | Margus Freudenthal |
| 03.09.2015 | 0.3 | Re-structuring and accuracy improvements | Martin Lind |
| 13.09.2015 | 0.4 | Made editorial changes | Margus Freudenthal |
| 16.09.2015 | 0.5 | Correct example message for authentication certificate registration request | Martin Lind |
| 17.09.2015 | 0.6 | Improvements for example messages and referential improvements | Martin Lind |
| 17.09.2015 | 0.7 | Improvements for Schema fragments | Martin Lind |
| 18.09.2015 | 0.8 | Updating Schema in the WSDL | Martin Lind |
| 21.09.2015 | 1.0 | Editorial changes made | Imbi Nõgisto |
| 21.09.2015 | 1.1 | Document renamed | Imbi Nõgisto |
| 01.10.2015 | 1.2 | Field requestId added and redundant elements removed | Martin Lind |
| 05.10.2015 | 1.3 | Updated example messages | Martin Lind |
| 06.10.2015 | 1.4 | Correct header fields for WSDL | Martin Lind |
| 17.10.2015 | 1.6 | Editorial changes related to requestId field | Margus Freudenthal |
| 28.10.2015 | 1.7 | Complete X-Road identifiers schema added | Siim Annuk |
| 30.10.2015 | 1.8 | Header field userId removed from management services WSDL | Kristo Heero |
| 11.12.2015 | 1.9 | Corrected documentation about registering only subsystems | Siim Annuk |
| 07.06.2017 | 1.10 | Additional signature algorithms supported | Kristo Heero |
| 06.03.2018 | 1.11 | Added terms section, term doc reference and link, fixed references | Tatu Repo |
| 06.02.2019 | 1.12 | Update clientReg message description | Petteri Kivimäki |
| 03.06.2019 | 1.13 | Add ownerChange management service | Ilkka Seppälä |
| 29.06.2019 | 1.14 | Rename newOwner element to client in ownerChange management service | Petteri Kivimäki |
| 10.05.2023 | 1.15 | Security Categories removed. | Justas Samuolis |
| 20.11.2023 | 1.16 | Add addressChange management service | Justas Samuolis |
| 11.12.2023 | 1.17 | clientDisable and clientEnable services | Madis Loitmaa |
- License
- 1 Introduction
- 2 Format of the Messages
- 2.1 clientReg - Security Server Client Registration
- 2.2 clientDeletion - Security Server Client Deletion
- 2.3 authCertReg - Security Server Authentication Certificate Registration
- 2.4 authCertDeletion - Security Server Authentication Certificate Deletion
- 2.5 ownerChange - Security Server Owner Change
- 2.6 addressChange - Security Server address change
- 2.7 clientDisable - Disable Security Server Client Subsystem Temporarily
- 2.8 clientEnable - Enable Security Server Client Subsystem
- Annex A. Example messages
- Annex B WSDL File for Management Services
This work is licensed under the Creative Commons Attribution-ShareAlike 3.0 Unported License. To view a copy of this license, visit http://creativecommons.org/licenses/by-sa/3.0/.
Management services are services provided by the X-Road governing organization to manage Security Servers and Security Server clients. They are called by Security Servers to register in Central Server the configuration changes made by the Security Server administrator. The management services are the following:
-
clientReg – registering an X-Road subsystem as a client of the Security Server;
-
clientDeletion – removing a client from the Security Server;
-
authCertReg – adding an authentication certificate to the Security Server;
-
authCertDeletion – removing an authentication certificate from the Security Server.
-
ownerChange - changing the owner member of the Security Server.
-
addressChange - changing Security Server's address.
-
clientDisable - disabling Security Server's client subsystem temporarily.
-
clientEnable - enabling disabled Security Server's client subsystem.
The management services are implemented as standard X-Road services (see [PR-MESS] for detailed description of the protocol) that are offered by the X-Road governing authority. The exception is the authCertReg service that, for technical reasons, is implemented as HTTPS POST (see below for details).
This protocol builds on existing transport and message encoding mechanisms. Therefore, this specification does not cover the technical details and error conditions related to making HTTPS requests together with processing MIME-encoded messages. These concerns are discussed in detail in their respective standards.
Section 2 as well as Annex B, of this specification contain normative information. All the other sections are informative in nature. All the references are normative.
This specification does not include option for partially implementing the protocol – the conformant implementation must implement the entire specification.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document (in uppercase, as shown) are to be interpreted as described in [REQUIREMENT].
See X-Road terms and abbreviations documentation [TA-TERMS].
- [REQUIREMENT] Key words for use in RFCs to Indicate Requirement Levels. Request for Comments 2119, Internet Engineering Task Force, March 1997.
- [DM-CS] X-Road: Central Server Data Model. Document ID: DM-CS
- [PR-MESS] X-Road: Message Protocol v4.0. Document ID: PR-MESS
- [WSDL] Web Services Description Language (WSDL) 1.1. World Wide Web Consortium. 15 March 2001.
- [DER] DER encoding. ITU-T X.690. July 2002.
- [TA-TERMS] X-Road Terms and Abbreviations. Document ID: TA-TERMS.
This section describes the input and output parameters of the management services. The low-level technical details of the services are specified using the WSDL [WSDL] syntax. See Annex B for management services WSDL file.
The client registration service is invoked by the Security Server when a new client is added to the server.
The body of the client registration message (request or response) contains the following fields:
-
client – identifier of the subsystem to be added to the Security Server;
-
server – identifier of the Security Server where the client is added;
-
requestId – for responses only, unique identifier of the request that is stored in the Central Server database [DM-CS].
The XML Schema fragment of the client registration request body is shown below. For clarity, documentation in the schema fragment is omitted.
<xsd:complexType name="ClientRequestType">
<xsd:sequence>
<xsd:element name="server" type="id:XRoadSecurityServerIdentifierType"/>
<xsd:element name="client" type="id:XRoadClientIdentifierType"/>
<element name="requestId" type="tns:RequestIdType" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>The request is sent using HTTP POST method. The content type of the request MUST be multipart/related and the request must contain the following MIME parts.
-
X-Road SOAP request message. The message MUST contain the regular X-Road headers and the two data fields (server, client). The content type of this part MUST be text/xml.
-
Signature of the member that owns the subsystem to be registered as a Security Server client. The MIME part must contain signature of the SOAP request message, created with the private key corresponding to a signing certificate of the subsystem's owner. The content type of this part must be application/octet-stream. Additionally, the part MUST include header field signature-algorithm-ID that identifies the signature algorithm. Currently supported signature algorithms are SHA256withRSA, SHA384withRSA, SHA512withRSA, SHA256withRSAandMGF1, SHA384withRSAandMGF1, and SHA512withRSAandMGF1.
-
Signing certificate of the subsystem's owner that was used to create the second MIME part. The content type of this part MUST be application/octet-stream.
-
OCSP response certifying that the signing certificate was valid at the time of creation of the request. The content type of this part MUST be application/octet-stream.
The response echoes back the client and the server fields of the request and adds the field requestId.
An example of the client registration request and response is given in Annex A.1.
The clientDeletion service is invoked by the Security Server when a client is unregistered.
The body of the client deletion message (request or response) contains following fields:
-
client – identifier of the subsystem to be removed from the Security Server;
-
server – identifier of the Security Server where the client is removed;
-
requestId – for responses only, unique identifier of the request that is stored in the Central Server database [DM-CS].
The XML Schema fragment of the client deletion request body shown below.
<xsd:complexType name="ClientRequestType">
<xsd:sequence>
<xsd:element name="server" type="id:XRoadSecurityServerIdentifierType"/>
<xsd:element name="client" type="id:XRoadClientIdentifierType"/>
<element name="requestId" type="tns:RequestIdType" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>The response echoes back the client and the server fields of the request and adds the field requestId.
An example of the client deletion request and response is given in Annex A.2.
The authCertReg service is invoked by the Security Server when a new authentication certificate is added to the server.
The body of the authentication certificate registration message (request or response) contains the following fields:
-
server – identifier of the Security Server where the authentication certificate is added;
-
address – DNS address of the Security Server;
-
authCert – contents (in DER encoding [DER]) of the authentication certificate that will be added to the Security Server;
-
requestId – for responses only, unique identifier of the request that is stored in the Central Server database [DM-CS].
The XML Schema fragment of the authentication certificate registration request body is shown below. For clarity, documentation in the schema fragment is omitted.
<xsd:complexType name="AuthCertRegRequestType">
<xsd:sequence>
<xsd:element name="server" type="id:XRoadSecurityServerIdentifierType"/>
<xsd:element name="address" type="string" minOccurs="0"/>
<xsd:element name="authCert" type="base64Binary"/>
<element name="requestId" type="tns:RequestIdType" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>Unlike the other requests, the authentication certificate registration request cannot be sent as a regular X-Road request. This is caused by a bootstrapping problem – sending an X‑Road message requires that the authentication certificate of the Security Server is registered at the Central Server. However, the certificate is registered only as a result of invoking this service. Therefore, another mechanism is needed.
The authentication certificate registration request is sent to the Central Server directly via HTTPS. When making the HTTPS connection the client MUST verify that the server uses the TLS certificate that is given in the global configuration.
If the Central Server encounters an error, it responds with a SOAP fault message.
The request is sent using HTTP POST method. The content type of the request MUST be multipart/related and the request must contain the following MIME parts.
-
X-Road SOAP request message. The message MUST contain the regular X-Road headers and the three data fields (server, address, authCert). The content type of this part MUST be text/xml.
-
Proof of possession of the authentication key. The MIME part must contain signature of the SOAP request message (the body of the first MIME part). The signature MUST be given using the private key corresponding to the authentication certificate that is being registered (authCert field of the SOAP message). The content type of this part must be application/octet-stream. Additionally, the part MUST include header field signature-algorithm-ID that identifies the signature algorithm. Currently supported signature algorithms are SHA256withRSA, SHA384withRSA, and SHA512withRSA.
-
Signature of the Security Server's owner. The MIME part must contain signature of the SOAP request message, created with the private key corresponding to a signing certificate of the Security Server's owner. The content type of this part must be application/octet-stream. Additionally, the part MUST include header field signature-algorithm-ID that identifies the signature algorithm. Currently supported signature algorithms are SHA256withRSA, SHA384withRSA, SHA512withRSA, SHA256withRSAandMGF1, SHA384withRSAandMGF1, and SHA512withRSAandMGF1.
-
Authentication certificate that is being registered (authCert field of the SOAP message). The content type of this part MUST be application/octet-stream.
-
Signing certificate of the Security Server's owner that was used to create the third MIME part. The content type of this part MUST be application/octet-stream.
-
OCSP response certifying that the signing certificate was valid at the time of creation of the request. The content type of this part MUST be application/octet-stream.
The Central Server sends responds with X-Road response message (content type MUST be text/xml). The response echoes back the three fields of the SOAP request and adds the field requestId.
An example of the authentication certificate registration request and response is given in Annex A.3.
The authCertDeletion service is invoked by the Security Server when an authentication certificate is deleted from the server. The body of the authentication certificate deletion message (request or response) contains the following fields:
-
server – identifier of the Security Server where the authentication certificate is removed;
-
authCert – contents (in DER encoding) of the authentication certificate that is removed from the Security Server;
-
requestId – for responses only, unique identifier of the request that is stored in the Central Server database [DM-CS].
The XML Schema fragment of the authentication certificate deletion request body is shown below.
<xsd:complexType name="AuthCertDeletionRequestType">
<xsd:sequence>
<xsd:element name="server" type="id:XRoadSecurityServerIdentifierType"/>
<xsd:element name="authCert" type="base64Binary"/>
<element name="requestId" type="tns:RequestIdType" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>The response echoes back the client and the server fields of the request and adds the field requestId.
An example of the authentication certificate deletion request and response is given in Annex A.4.
The owner change service is invoked by the Security Server when the owner member of the Security Server is changed.
The body of the owner change message (request or response) contains the following fields:
-
server – identifier of the Security Server where the owner is changed;
-
client – identifier of the new owner member of the Security Server;
-
requestId – for responses only, unique identifier of the request that is stored in the Central Server database [DM-CS].
The XML Schema fragment of the client registration request body is shown below. For clarity, documentation in the schema fragment is omitted.
<xsd:complexType name="ClientRequestType">
<xsd:sequence>
<xsd:element name="server" type="id:XRoadSecurityServerIdentifierType"/>
<xsd:element name="client" type="id:XRoadClientIdentifierType"/>
<element name="requestId" type="tns:RequestIdType" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>The request is sent using HTTP POST method. The content type of the request MUST be multipart/related and the request must contain the following MIME parts.
-
X-Road SOAP request message. The message MUST contain the regular X-Road headers and the two data fields (server, client). The content type of this part MUST be text/xml.
-
Signature of the new owner member of the Security Server. The MIME part must contain signature of the SOAP request message, created with the private key corresponding to a signing certificate of the new owner member. The content type of this part must be application/octet-stream. Additionally, the part MUST include header field signature-algorithm-ID that identifies the signature algorithm. Currently supported signature algorithms are SHA256withRSA, SHA384withRSA, SHA512withRSA, SHA256withRSAandMGF1, SHA384withRSAandMGF1, and SHA512withRSAandMGF1.
-
Signing certificate of the new owner member that was used to create the second MIME part. The content type of this part MUST be application/octet-stream.
-
OCSP response certifying that the new owner member's signing certificate was valid at the time of creation of the request. The content type of this part MUST be application/octet-stream.
The response echoes back the server and the client fields of the request and adds the field requestId.
An example of the owner change request and response is given in Annex A.5.
The service is used to change the Security Server address from Security Server.
The body of the address change message (request or response) contains the following fields:
- server – identifier of the Security Server where the owner is changed;
- address – new Security Server DNS address;
- requestId – for responses only, unique identifier of the request that is stored in the Central Server database [DM-CS].
The XML Schema fragment of the address cahnge request body is shown below. For clarity, documentation in the schema fragment is omitted.
<xsd:complexType name="AddressChangeRequestType">
<xsd:sequence>
<xsd:element name="server" type="id:XRoadSecurityServerIdentifierType" />
<xsd:element name="address" type="string" />
<xsd:element name="requestId" type="tns:RequestIdType" minOccurs="0" />
</xsd:sequence>
</xsd:complexType>The request is sent using HTTP POST method. The content type of the request MUST be multipart/related and the request must contain the following MIME parts.
-
X-Road SOAP request message. The message MUST contain the regular X-Road headers and the two data fields (server, client). The content type of this part MUST be text/xml.
-
Signature of owner member of the Security Server. The MIME part must contain signature of the SOAP request message, created with the private key corresponding to a signing certificate of the owner member. The content type of this part must be application/octet-stream. Additionally, the part MUST include header field signature-algorithm-ID that identifies the signature algorithm. Currently supported signature algorithms are SHA256withRSA, SHA384withRSA, SHA512withRSA, SHA256withRSAandMGF1, SHA384withRSAandMGF1, and SHA512withRSAandMGF1.
-
Signing certificate of the owner member that was used to create the second MIME part. The content type of this part MUST be application/octet-stream.
-
OCSP response certifying that the owner member's signing certificate was valid at the time of creation of the request. The content type of this part MUST be application/octet-stream.
The response echoes back the server and the client fields of the request and adds the field requestId.
An example of the address change request and response is given in Annex A.6).
The clientDisable service is used to disable Security Server client subsystem temporarily.
The body of the client disabling message (request or response) contains following fields:
- client – identifier of the subsystem to be disabled;
- server – identifier of the Security Server where the client is disabled;
- requestId – for responses only, unique identifier of the request that is stored in the Central Server database [DM-CS].
The XML Schema fragment of the client deletion request body shown below.
<xsd:complexType name="ClientRequestType">
<xsd:sequence>
<xsd:element name="server" type="id:XRoadSecurityServerIdentifierType"/>
<xsd:element name="client" type="id:XRoadClientIdentifierType"/>
<element name="requestId" type="tns:RequestIdType" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>The request is sent using HTTP POST method. The content type of the request MUST be multipart/related and the request must contain the following MIME parts.
-
X-Road SOAP request message. The message MUST contain the regular X-Road headers and the two data fields (server, client). The content type of this part MUST be text/xml.
-
Signature of owner member of the Security Server. The MIME part must contain signature of the SOAP request message, created with the private key corresponding to a signing certificate of the owner member. The content type of this part must be application/octet-stream. Additionally, the part MUST include header field signature-algorithm-ID that identifies the signature algorithm. Currently supported signature algorithms are SHA256withRSA, SHA384withRSA, SHA512withRSA, SHA256withRSAandMGF1, SHA384withRSAandMGF1, and SHA512withRSAandMGF1.
-
Signing certificate of the owner member that was used to create the second MIME part. The content type of this part MUST be application/octet-stream.
-
OCSP response certifying that the owner member's signing certificate was valid at the time of creation of the request. The content type of this part MUST be application/octet-stream.
The response echoes back the client and the server fields of the request and adds the field requestId.
An example of the client disabling request and response is given in Annex A.7.
The clientEnable service is used to enable disabled Security Server client subsystem.
The body of the client enabling message (request or response) contains following fields:
- client – identifier of the subsystem to be enabled;
- server – identifier of the Security Server where the client is enabled;
- requestId – for responses only, unique identifier of the request that is stored in the Central Server database [DM-CS].
The XML Schema fragment of the client deletion request body shown below.
<xsd:complexType name="ClientRequestType">
<xsd:sequence>
<xsd:element name="server" type="id:XRoadSecurityServerIdentifierType"/>
<xsd:element name="client" type="id:XRoadClientIdentifierType"/>
<element name="requestId" type="tns:RequestIdType" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>The request is sent using HTTP POST method. The content type of the request MUST be multipart/related and the request must contain the following MIME parts.
-
X-Road SOAP request message. The message MUST contain the regular X-Road headers and the two data fields (server, client). The content type of this part MUST be text/xml.
-
Signature of owner member of the Security Server. The MIME part must contain signature of the SOAP request message, created with the private key corresponding to a signing certificate of the owner member. The content type of this part must be application/octet-stream. Additionally, the part MUST include header field signature-algorithm-ID that identifies the signature algorithm. Currently supported signature algorithms are SHA256withRSA, SHA384withRSA, SHA512withRSA, SHA256withRSAandMGF1, SHA384withRSAandMGF1, and SHA512withRSAandMGF1.
-
Signing certificate of the owner member that was used to create the second MIME part. The content type of this part MUST be application/octet-stream.
-
OCSP response certifying that the owner member's signing certificate was valid at the time of creation of the request. The content type of this part MUST be application/octet-stream.
The response echoes back the client and the server fields of the request and adds the field requestId.
An example of the client enabling request and response is given in Annex A.8.
Request message
--jetty113950090iemuz6a3
Content-Type: text/xml; charset=UTF-8
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:id="http://x-road.eu/xsd/identifiers"
xmlns:xroad="http://x-road.eu/xsd/xroad.xsd">
<SOAP-ENV:Header>
<xroad:client id:objectType="MEMBER">
<id:xRoadInstance>EE</id:xRoadInstance>
<id:memberClass>GOV</id:memberClass>
<id:memberCode>TS1OWNER</id:memberCode>
</xroad:client>
<xroad:service id:objectType="SERVICE">
<id:xRoadInstance>EE</id:xRoadInstance>
<id:memberClass>GOV</id:memberClass>
<id:memberCode>TS1OWNER</id:memberCode>
<id:serviceCode>clientReg</id:serviceCode>
</xroad:service>
<xroad:id>8770348d-c5f1-4f23-989e-7dd91fb59eff</xroad:id>
<xroad:protocolVersion>4.0</xroad:protocolVersion>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<xroad:clientReg>
<xroad:server id:objectType="SERVER">
<id:xRoadInstance>EE</id:xRoadInstance>
<id:memberClass>GOV</id:memberClass>
<id:memberCode>TS1OWNER</id:memberCode>
<id:serverCode>TS1</id:serverCode>
</xroad:server>
<xroad:client id:objectType="SUBSYSTEM">
<id:xRoadInstance>EE</id:xRoadInstance>
<id:memberClass>COM</id:memberClass>
<id:memberCode>client</id:memberCode>
<id:subsystemCode>subsystem</id:subsystemCode>
</xroad:client>
</xroad:clientReg>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
--jetty113950090iemuz6a3
Content-Type: application/octet-stream
signature-algorithm-id: SHA512withRSA
[SUBSYSTEM OWNER SIGNATURE BYTES]
--jetty113950090iemuz6a3
Content-Type: application/octet-stream
[SUBSYSTEM OWNER CERTIFICATE BYTES]
--jetty113950090iemuz6a3
Content-Type: application/octet-stream
[SUBSYSTEM OWNER CERTIFICATE OCSP RESPONSE BYTES]
--jetty113950090iemuz6a3--Response message
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:id="http://x-road.eu/xsd/identifiers"
xmlns:xroad="http://x-road.eu/xsd/xroad.xsd">
<SOAP-ENV:Header>
<xroad:client id:objectType="MEMBER">
<id:xRoadInstance>EE</id:xRoadInstance>
<id:memberClass>GOV</id:memberClass>
<id:memberCode>TS1OWNER</id:memberCode>
</xroad:client>
<xroad:service id:objectType="SERVICE">
<id:xRoadInstance>EE</id:xRoadInstance>
<id:memberClass>GOV</id:memberClass>
<id:memberCode>TS1OWNER</id:memberCode>
<id:serviceCode>clientReg</id:serviceCode>
</xroad:service>
<xroad:id>8770348d-c5f1-4f23-989e-7dd91fb59eff</xroad:id>
<xroad:protocolVersion>4.0</xroad:protocolVersion>
<xroad:requestHash
algorithmId="http://www.w3.org/2001/04/xmlenc#sha512">
LGxmFNQhkhehCsbrrBgX4w64N0Z+knazghehKDYwJzSmVwf8tyVCYHyD8Vp5eSNNMtm0
XDBzMOkqQ3uSDfNrLw==
</xroad:requestHash>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<xroad:clientRegResponse>
<xroad:server id:objectType="SERVER">
<id:xRoadInstance>EE</id:xRoadInstance>
<id:memberClass>GOV</id:memberClass>
<id:memberCode>TS1OWNER</id:memberCode>
<id:serverCode>TS1</id:serverCode>
</xroad:server>
<xroad:client id:objectType="SUBSYSTEM">
<id:xRoadInstance>EE</id:xRoadInstance>
<id:memberClass>COM</id:memberClass>
<id:memberCode>client</id:memberCode>
<id:subsystemCode>subsystem</id:subsystemCode>
</xroad:client>
<xroad:requestId>394</xroad:requestId>
</xroad:clientRegResponse>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>Request message
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:id="http://x-road.eu/xsd/identifiers"
xmlns:xroad="http://x-road.eu/xsd/xroad.xsd">
<SOAP-ENV:Header>
<xroad:client id:objectType="MEMBER">
<id:xRoadInstance>EE</id:xRoadInstance>
<id:memberClass>GOV</id:memberClass>
<id:memberCode>TS1OWNER</id:memberCode>
</xroad:client>
<xroad:service id:objectType="SERVICE">
<id:xRoadInstance>EE</id:xRoadInstance>
<id:memberClass>GOV</id:memberClass>
<id:memberCode>TS1OWNER</id:memberCode>
<id:serviceCode>clientDeletion</id:serviceCode>
</xroad:service>
<xroad:id>0e0d804a-b4e2-4f56-b5a0-2c32e4288f7d</xroad:id>
<xroad:protocolVersion>4.0</xroad:protocolVersion>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<xroad:clientDeletion>
<xroad:server id:objectType="SERVER">
<id:xRoadInstance>EE</id:xRoadInstance>
<id:memberClass>GOV</id:memberClass>
<id:memberCode>TS1OWNER</id:memberCode>
<id:serverCode>TS1</id:serverCode>
</xroad:server>
<xroad:client id:objectType="SUBSYSTEM">
<id:xRoadInstance>EE</id:xRoadInstance>
<id:memberClass>COM</id:memberClass>
<id:memberCode>client</id:memberCode>
<id:subsystemCode>subsystem</id:subsystemCode>
</xroad:client>
</xroad:clientDeletion>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>Response message
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:id="http://x-road.eu/xsd/identifiers"
xmlns:xroad="http://x-road.eu/xsd/xroad.xsd">
<SOAP-ENV:Header>
<xroad:client id:objectType="MEMBER">
<id:xRoadInstance>EE</id:xRoadInstance>
<id:memberClass>GOV</id:memberClass>
<id:memberCode>TS1OWNER</id:memberCode>
</xroad:client>
<xroad:service id:objectType="SERVICE">
<id:xRoadInstance>EE</id:xRoadInstance>
<id:memberClass>GOV</id:memberClass>
<id:memberCode>TS1OWNER</id:memberCode>
<id:serviceCode>clientDeletion</id:serviceCode>
</xroad:service>
<xroad:id>0e0d804a-b4e2-4f56-b5a0-2c32e4288f7d</xroad:id>
<xroad:protocolVersion>4.0</xroad:protocolVersion>
<xroad:requestHash algorithmId="http://www.w3.org/2001/04/xmlenc#sha512">
KHe7PMAcYgNzcS7/4KImaYZxpLry0l+1zkFgzKXVkmzkYXg9IjBgX7CP6wDXwYT0qVON
6NiF74LvlSwpPupO5A==
</xroad:requestHash>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<xroad:clientDeletionResponse>
<xroad:server id:objectType="SERVER">
<id:xRoadInstance>EE</id:xRoadInstance>
<id:memberClass>GOV</id:memberClass>
<id:memberCode>TS1OWNER</id:memberCode>
<id:serverCode>TS1</id:serverCode>
</xroad:server>
<xroad:client id:objectType="SUBSYSTEM">
<id:xRoadInstance>EE</id:xRoadInstance>
<id:memberClass>COM</id:memberClass>
<id:memberCode>client</id:memberCode>
<id:subsystemCode>subsystem</id:subsystemCode>
</xroad:client>
<xroad:requestId>395</xroad:requestId>
</xroad:clientDeletionResponse>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>Request message
--jetty113950090iemuz6a3
Content-Type: text/xml; charset=UTF-8
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:id="http://x-road.eu/xsd/identifiers"
xmlns:xroad="http://x-road.eu/xsd/xroad.xsd">
<SOAP-ENV:Header>
<xroad:client id:objectType="MEMBER">
<id:xRoadInstance>EE</id:xRoadInstance>
<id:memberClass>GOV</id:memberClass>
<id:memberCode>TS1OWNER</id:memberCode>
</xroad:client>
<xroad:service id:objectType="SERVICE">
<id:xRoadInstance>EE</id:xRoadInstance>
<id:memberClass>GOV</id:memberClass>
<id:memberCode>TS1OWNER</id:memberCode>
<id:serviceCode>authCertReg</id:serviceCode>
</xroad:service>
<xroad:id>9a82c2d1-27d6-4053-85a7-f37327c6dba7</xroad:id>
<xroad:protocolVersion>4.0</xroad:protocolVersion>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<xroad:authCertReg>
<xroad:server id:objectType="SERVER">
<id:xRoadInstance>EE</id:xRoadInstance>
<id:memberClass>GOV</id:memberClass>
<id:memberCode>TS1OWNER</id:memberCode>
<id:serverCode>TS1</id:serverCode>
</xroad:server>
<xroad:address>192.168.74.202</xroad:address>
<xroad:authCert>
MIIDtzCCAp+gAwIBAgIIaAPFaI/REfAwDQYJKoZIhvcNAQEFBQAwNzERMA8GA1UE
AwwIQWRtaW5DQTExFTATBgNVBAoMDEVKQkNBIFNhbXBsZTELMAkGA1UEBhMCU0Uw
HhcNMTUxMDA1MTEyNzQzWhcNMTcxMDA0MTEyNzQzWjAuMQswCQYDVQQGEwJFRTEM
MAoGA1UECgwDR09WMREwDwYDVQQDDAhUUzFPV05FUjCCASIwDQYJKoZIhvcNAQEB
BQADggEPADCCAQoCggEBAIkX6/b/yUNSIvZatpFDqUDJ4l+igH+z8/kyLlu92VL6
H7hkCL6ggn7qsHOTGaxOupXQBKx/EDMOt+cpbhQlQCSoU2LmXYklv9FEGXTUBt5U
VlT1mZXQkfPVT2ozWQeGEOe7RLApaldgfFgg6AklsuOTe0FgJTfqXrnjVy84MRht
56nw0V6SnujGMVxQJR1IJC13I5wRbVbkyOxX52vqJ7Kh/2GWtNj2AgY9VbZA6/8S
3fMVHWQUbVtFV/2LyjQ0OrwPm0VXsrqRnlh0tln3AtgNOiPgmg72aWNPwlPx7+rE
02t+0O+KieC3IZppY2044tC699ui5/nOZPrlIqC1XcCAwEAAaOBzzCBzDBNBggrB
gEFBQcBAQRBMD8wPQYIKwYBBQUHMAGGMWh0dHA6Ly9sb2NhbGhvc3Q6ODA4MC9la
mJjYS9wdWJsaWN3ZWIvc3RhdHVzL29jc3AwHQYDVR0OBBYEFCB7AE2wTs7iLMMxG
tilpSg8bShnMAwGA1UdEwEB/wQCMAAwHwYDVR0jBBgwFoAUdy2JLgO2/fjSZTkxN
SLQRhro0gkwDgYDVR0PAQH/BAQDAgO4MB0GA1UdJQQWMBQGCCsGAQUFBwMBBggrB
gEFBQcDAjANBgkqhkiG9w0BAQUFAAOCAQEATCbKukYbOV5R4I/ivhEXIJAA8azeJ
NONWg0+74v9hdInDSDuXreJkkpJNz0pZaaDnbsWFF+LGcB8UDTc6jOGOaH1b2iSh
qzq/jL+Le9iSi8V26aWmKJipt5fsU5E/OJAA0KMnNjhtq5FDdP7gCD7+pPVq2FwE
Wf9nsNtAq8uETc5f9PNGxE6PrDl2Gy2K3m4T/0kvQIiMFsk1z054/9rW/w+dQSSs
xHhYHOPzwbSEsoeSw3UEqeKdaYUspFs+eGD4b3dexwEe5M0oZAwL/+/56eTcOhne
nP9A+8jF1vlXnP/m+tThaftcMZa/NTvpceLx36TDUIwB222ddkyN2Offw==
</xroad:authCert>
</xroad:authCertReg>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
--jetty113950090iemuz6a3
Content-Type: application/octet-stream
signature-algorithm-id: SHA512withRSA
[AUTHENTICATION CERTIFICATE SIGNATURE BYTES]
--jetty113950090iemuz6a3
Content-Type: application/octet-stream
signature-algorithm-id: SHA512withRSA
[SECURITY SERVER OWNER SIGNATURE BYTES]
--jetty113950090iemuz6a3
Content-Type: application/octet-stream
[AUTHENTICATION CERTIFICATE BYTES]
--jetty113950090iemuz6a3
Content-Type: application/octet-stream
[SECURITY SERVER OWNER CERTIFICATE BYTES]
--jetty113950090iemuz6a3
Content-Type: application/octet-stream
[SECURITY SERVER OWNER CERTIFICATE OCSP RESPONSE BYTES]
--jetty113950090iemuz6a3--Response message
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:id="http://x-road.eu/xsd/identifiers"
xmlns:xroad="http://x-road.eu/xsd/xroad.xsd">
<SOAP-ENV:Header>
<xroad:client id:objectType="MEMBER">
<id:xRoadInstance>EE</id:xRoadInstance>
<id:memberClass>GOV</id:memberClass>
<id:memberCode>TS1OWNER</id:memberCode>
</xroad:client>
<xroad:service id:objectType="SERVICE">
<id:xRoadInstance>EE</id:xRoadInstance>
<id:memberClass>GOV</id:memberClass>
<id:memberCode>TS1OWNER</id:memberCode>
<id:serviceCode>authCertReg</id:serviceCode>
</xroad:service>
<xroad:id>9a82c2d1-27d6-4053-85a7-f37327c6dba7</xroad:id>
<xroad:protocolVersion>4.0</xroad:protocolVersion>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<xroad:authCertRegResponse>
<xroad:server id:objectType="SERVER">
<id:xRoadInstance>EE</id:xRoadInstance>
<id:memberClass>GOV</id:memberClass>
<id:memberCode>TS1OWNER</id:memberCode>
<id:serverCode>TS1</id:serverCode>
</xroad:server>
<xroad:address>192.168.74.202</xroad:address>
<xroad:authCert>
MIIDtzCCAp+gAwIBAgIIaAPFaI/REfAwDQYJKoZIhvcNAQEFBQAwNzERMA8GA1UE
AwwIQWRtaW5DQTExFTATBgNVBAoMDEVKQkNBIFNhbXBsZTELMAkGA1UEBhMCU0Uw
HhcNMTUxMDA1MTEyNzQzWhcNMTcxMDA0MTEyNzQzWjAuMQswCQYDVQQGEwJFRTEM
MAoGA1UECgwDR09WMREwDwYDVQQDDAhUUzFPV05FUjCCASIwDQYJKoZIhvcNAQEB
BQADggEPADCCAQoCggEBAIkX6/b/yUNSIvZatpFDqUDJ4l+igH+z8/kyLlu92VL6
H7hkCL6ggn7qsHOTGaxOupXQBKx/EDMOtcpbhQlQCSoU2LmXYklv9FEGXTUBt5UV
lT1mZXQkfPVT2ozWQeGEOe7RLApaldgfFgg6AklsuOTe0FgJTfqXrnjVy84MRht5
6nw0V6SnujGMVxQJR1IJC13I5wRbVbkyOxX52vqJ7Kh/2GWtNj2AgY9VbZA6/8ES
3fMVHWQUbVtFV/2LyjQ0OrwPm0VXsrqRnlh0tln3AtgNOiPgmg72aWNPwlPx7+rE
02t+0O+KieC3IZppY2044tC699ui5nOZPrlIqC1XcCAwEAAaOBzzCBzDBNBggrBg
EFBQcBAQRBMD8wPQYIKwYBBQUHMAGGMWh0dHA6Ly9sb2NhbGhvc3Q6ODA4MC9lam
JjYS9wdWJsaWN3ZWIvc3RhdHVzL29jc3AwHQYDVR0OBBYEFCB7AE2wTs7iLMMxGt
ilpSg8bShnMAwGA1UdEwEB/wQCMAAwHwYDVR0jBBgwFoAUdy2JLgO2/fjSZTkxNS
LQRhro0gkwDgYDVR0PAQH/BAQDAgO4MB0GA1UdJQQWMBQGCCsGAQUFBwMBBggrBg
EFBQcDAjANBgkqhkiG9w0BAQUFAAOCAQEATCbKukYbOV5R4I/ivhEXIJAA8azeJN
ONWg0+74v9hdInDSDuXreJkkpJNz0pZaaDnbsWFF+LGcB8UDTc6jOGOaH1b2iShq
zq/jL+Le9iSi8V26aWmKJipt5fsU5E/OJAA0KMnNjhtq5FDdP7gCD7+pPVq2FwEW
f9nsNtAq8uETc5f9PNGxE6PrDl2Gy2K3m4T/0kvQIiMFsk1z054/9rW/w+dQSSsx
HhYHOPzwbSEsoeSw3UEqeKdaYUspFs+eGD4b3dexwEe5M0oZAwL/+/56eTcOhnen
P9A+8jF1vlXnP/m+tThaftcMZa/NTvpceLx36TDUIwB222ddkyN2Offw==
</xroad:authCert>
<xroad:requestId>392</xroad:requestId>
</xroad:authCertRegResponse>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>Request message
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:id="http://x-road.eu/xsd/identifiers"
xmlns:xroad="http://x-road.eu/xsd/xroad.xsd">
<SOAP-ENV:Header>
<xroad:client id:objectType="MEMBER">
<id:xRoadInstance>EE</id:xRoadInstance>
<id:memberClass>GOV</id:memberClass>
<id:memberCode>TS1OWNER</id:memberCode>
</xroad:client>
<xroad:service id:objectType="SERVICE">
<id:xRoadInstance>EE</id:xRoadInstance>
<id:memberClass>GOV</id:memberClass>
<id:memberCode>TS1OWNER</id:memberCode>
<id:serviceCode>authCertDeletion</id:serviceCode>
</xroad:service>
<xroad:id>2c3094ae-3e19-46f7-b26d-e7ecb35dfc63</xroad:id>
<xroad:protocolVersion>4.0</xroad:protocolVersion>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<xroad:authCertDeletion>
<xroad:server id:objectType="SERVER">
<id:xRoadInstance>EE</id:xRoadInstance>
<id:memberClass>GOV</id:memberClass>
<id:memberCode>TS1OWNER</id:memberCode>
<id:serverCode>TS1</id:serverCode>
</xroad:server>
<xroad:authCert>
MIIDtzCCAp+gAwIBAgIIaAPFaI/REfAwDQYJKoZIhvcNAQEFBQAwNzERMA8GA1UE
AwwIQWRtaW5DQTExFTATBgNVBAoMDEVKQkNBIFNhbXBsZTELMAkGA1UEBhMCU0Uw
HhcNMTUxMDA1MTEyNzQzWhcNMTcxMDA0MTEyNzQzWjAuMQswCQYDVQQGEwJFRTEM
MAoGA1UECgwDR09WMREwDwYDVQQDDAhUUzFPV05FUjCCASIwDQYJKoZIhvcNAQEB
BQADggEPADCCAQoCggEBAIkX6/b/yUNSIvZatpFDqUDJ4l+igH+z8/kyLlu92VL6
H7hkCL6ggn7qsHOTGaxOupXQBKx/EDMOt+cpbhQlQCSoU2LmXYklv9FEGXTUBt5U
VlT1mZXQkfPVT2ozWQeGEOe7RLApaldgfFgg6AklsuOTe0FgJTfqXrnjVy84MRht
56nw0V6SnujGMVxQJR1IJC13I5wRbVbkyOxX52vqJ7Kh/2GWtNj2AgY9VbZA6/8E
S3fMVHWQUbVtFV/2LyjQ0OrwPm0VXsrqRnlh0tln3AtgNOiPgmg72aWNPwlPx7+r
E02t+0O+KieC3IZppY2044tC699ui5/nOZPrlIqC1XcCAwEAAaOBzzCBzDBNBggr
BgEFBQcBAQRBMD8wPQYIKwYBBQUHMAGGMWh0dHA6Ly9sb2NhbGhvc3Q6ODA4MC9l
amJjYS9wdWJsaWN3ZWIvc3RhdHVzL29jc3AwHQYDVR0OBBYEFCB7AE2wTs7iLMMx
GtilpSg8bShnMAwGA1UdEwEB/wQCMAAwHwYDVR0jBBgwFoAUdy2JLgO2/fjSZTkx
NSLQRhro0gkwDgYDVR0PAQH/BAQDAgO4MB0GA1UdJQQWMBQGCCsGAQUFBwMBBggr
BgEFBQcDAjANBgkqhkiG9w0BAQUFAAOCAQEATCbKukYbOV5R4I/ivhEXIJAA8aze
JNONWg0+74v9hdInDSDuXreJkkpJNz0pZaaDnbsWFF+LGcB8UDTc6jOGOaH1b2iS
hqzq/jL+Le9iSi8V26aWmKJipt5fsU5E/OJAA0KMnNjhtq5FDdP7gCD7+pPVq2Fw
EWf9nsNtAq8uETc5f9PNGxE6PrDl2Gy2K3m4T/0kvQIiMFsk1z054/9rW/w+dQSS
sxHhYHOPzwbSEsoeSw3UEqeKdaYUspFs+eGD4b3dexwEe5M0oZAwL/+/56eTcOhn
enP9A+8jF1vlXnP/m+tThaftcMZa/NTvpceLx36TDUIwB222ddkyN2Offw==
</xroad:authCert>
</xroad:authCertDeletion>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>Response message
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:id="http://x-road.eu/xsd/identifiers"
xmlns:xroad="http://x-road.eu/xsd/xroad.xsd">
<SOAP-ENV:Header>
<xroad:client id:objectType="MEMBER">
<id:xRoadInstance>EE</id:xRoadInstance>
<id:memberClass>GOV</id:memberClass>
<id:memberCode>TS1OWNER</id:memberCode>
</xroad:client>
<xroad:service id:objectType="SERVICE">
<id:xRoadInstance>EE</id:xRoadInstance>
<id:memberClass>GOV</id:memberClass>
<id:memberCode>TS1OWNER</id:memberCode>
<id:serviceCode>authCertDeletion</id:serviceCode>
</xroad:service>
<xroad:id>2c3094ae-3e19-46f7-b26d-e7ecb35dfc63</xroad:id>
<xroad:protocolVersion>4.0</xroad:protocolVersion>
<xroad:requestHash
algorithmId="http://www.w3.org/2001/04/xmlenc#sha512">
Zvs1uF2GW3zdma1r9K9keOGhNPOjCr3TEZNpxfpRCtsqqy3ljiLorMZ3e5iNZtX6Ek60
xtV12Gue8Mme1ryZmQ==
</xroad:requestHash>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<xroad:authCertDeletionResponse>
<xroad:server id:objectType="SERVER">
<id:xRoadInstance>EE</id:xRoadInstance>
<id:memberClass>GOV</id:memberClass>
<id:memberCode>TS1OWNER</id:memberCode>
<id:serverCode>TS1</id:serverCode>
</xroad:server>
<xroad:authCert>
MIIDtzCCAp+gAwIBAgIIaAPFaI/REfAwDQYJKoZIhvcNAQEFBQAwNzERMA8GA1UE
AwwIQWRtaW5DQTExFTATBgNVBAoMDEVKQkNBIFNhbXBsZTELMAkGA1UEBhMCU0Uw
HhcNMTUxMDA1MTEyNzQzWhcNMTcxMDA0MTEyNzQzWjAuMQswCQYDVQQGEwJFRTEM
MAoGA1UECgwDR09WMREwDwYDVQQDDAhUUzFPV05FUjCCASIwDQYJKoZIhvcNAQEB
BQADggEPADCCAQoCggEBAIkX6/b/yUNSIvZatpFDqUDJ4l+igH+z8/kyLlu92VL6
H7hkCL6ggn7qsHOTGaxOupXQBKx/EDMOt+cpbhQlQCSoU2LmXYklv9FEGXTUBt5U
VlT1mZXQkfPVT2ozWQeGEOe7RLApaldgfFgg6AklsuOTe0FgJTfqXrnjVy84MRht
56nw0V6SnujGMVxQJR1IJC13I5wRbVbkyOxX52vqJ7Kh/2GWtNj2AgY9VbZA6/8E
S3fMVHWQUbVtFV/2LyjQ0OrwPm0VXsrqRnlh0tln3AtgNOiPgmg72aWNPwlPx7+r
E02t+0O+KieC3IZppY2044tC699ui5/nOZPrlIqC1XcCAwEAAaOBzzCBzDBNBggr
BgEFBQcBAQRBMD8wPQYIKwYBBQUHMAGGMWh0dHA6Ly9sb2NhbGhvc3Q6ODA4MC9l
amJjYS9wdWJsaWN3ZWIvc3RhdHVzL29jc3AwHQYDVR0OBBYEFCB7AE2wTs7iLMMx
GtilpSg8bShnMAwGA1UdEwEB/wQCMAAwHwYDVR0jBBgwFoAUdy2JLgO2/fjSZTkx
NSLQRhro0gkwDgYDVR0PAQH/BAQDAgO4MB0GA1UdJQQWMBQGCCsGAQUFBwMBBggr
BgEFBQcDAjANBgkqhkiG9w0BAQUFAAOCAQEATCbKukYbOV5R4I/ivhEXIJAA8aze
JNONWg0+74v9hdInDSDuXreJkkpJNz0pZaaDnbsWFF+LGcB8UDTc6jOGOaH1b2iS
hqzq/jL+Le9iSi8V26aWmKJipt5fsU5E/OJAA0KMnNjhtq5FDdP7gCD7+pPVq2Fw
EWf9nsNtAq8uETc5f9PNGxE6PrDl2Gy2K3m4T/0kvQIiMFsk1z054/9rW/w+dQSS
sxHhYHOPzwbSEsoeSw3UEqeKdaYUspFs+eGD4b3dexwEe5M0oZAwL/+/56eTcOhn
enP9A+8jF1vlXnP/m+tThaftcMZa/NTvpceLx36TDUIwB222ddkyN2Offw==
</xroad:authCert>
<xroad:requestId>392</xroad:requestId>
</xroad:authCertDeletionResponse>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>Request message
--jetty113950090iemuz6a3
Content-Type: text/xml; charset=UTF-8
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:id="http://x-road.eu/xsd/identifiers"
xmlns:xroad="http://x-road.eu/xsd/xroad.xsd">
<SOAP-ENV:Header>
<xroad:client id:objectType="MEMBER">
<id:xRoadInstance>EE</id:xRoadInstance>
<id:memberClass>GOV</id:memberClass>
<id:memberCode>TS1OWNER</id:memberCode>
</xroad:client>
<xroad:service id:objectType="SERVICE">
<id:xRoadInstance>EE</id:xRoadInstance>
<id:memberClass>GOV</id:memberClass>
<id:memberCode>TS1OWNER</id:memberCode>
<id:serviceCode>ownerChange</id:serviceCode>
</xroad:service>
<xroad:id>40c1a424-729d-4d52-bd77-ac6f70d1dac0</xroad:id>
<xroad:protocolVersion>4.0</xroad:protocolVersion>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<xroad:ownerChange>
<xroad:server id:objectType="SERVER">
<id:xRoadInstance>EE</id:xRoadInstance>
<id:memberClass>GOV</id:memberClass>
<id:memberCode>TS1OWNER</id:memberCode>
<id:serverCode>TS1</id:serverCode>
</xroad:server>
<xroad:client id:objectType="MEMBER">
<id:xRoadInstance>EE</id:xRoadInstance>
<id:memberClass>COM</id:memberClass>
<id:memberCode>MACK</id:memberCode>
</xroad:client>
</xroad:ownerChange>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
--jetty113950090iemuz6a3
Content-Type: application/octet-stream
signature-algorithm-id: SHA512withRSA
[NEW OWNER SIGNATURE BYTES]
--jetty113950090iemuz6a3
Content-Type: application/octet-stream
[NEW OWNER CERTIFICATE BYTES]
--jetty113950090iemuz6a3
Content-Type: application/octet-stream
[NEW OWNER CERTIFICATE OCSP RESPONSE BYTES]
--jetty113950090iemuz6a3--Response message
<?xml version="1.0" encoding="UTF-8"?>
<SOAP-ENV:Envelope
xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:id="http://x-road.eu/xsd/identifiers"
xmlns:xroad="http://x-road.eu/xsd/xroad.xsd">
<SOAP-ENV:Header>
<xroad:client id:objectType="MEMBER">
<id:xRoadInstance>EE</id:xRoadInstance>
<id:memberClass>GOV</id:memberClass>
<id:memberCode>TS1OWNER</id:memberCode>
</xroad:client>
<xroad:service id:objectType="SERVICE">
<id:xRoadInstance>EE</id:xRoadInstance>
<id:memberClass>GOV</id:memberClass>
<id:memberCode>TS1OWNER</id:memberCode>
<id:serviceCode>ownerChange</id:serviceCode>
</xroad:service>
<xroad:id>40c1a424-729d-4d52-bd77-ac6f70d1dac0</xroad:id>
<xroad:protocolVersion>4.0</xroad:protocolVersion>
<xroad:requestHash
algorithmId="http://www.w3.org/2001/04/xmlenc#sha512">
LGxmFNQhkhehCsbrrBgX4w64N0Z+knazghehKDYwJzSmVwf8tyVCYHyD8Vp5eSNNMtm0
XDBzMOkqQ3uSDfNrLw==
</xroad:requestHash>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<xroad:ownerChangeResponse>
<xroad:server id:objectType="SERVER">
<id:xRoadInstance>EE</id:xRoadInstance>
<id:memberClass>GOV</id:memberClass>
<id:memberCode>TS1OWNER</id:memberCode>
<id:serverCode>TS1</id:serverCode>
</xroad:server>
<xroad:client id:objectType="MEMBER">
<id:xRoadInstance>EE</id:xRoadInstance>
<id:memberClass>COM</id:memberClass>
<id:memberCode>MACK</id:memberCode>
</xroad:client>
<xroad:requestId>691</xroad:requestId>
</xroad:ownerChangeResponse>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>Request message
--jetty832974847lp2nei0x
Content-Type: text/xml; charset=UTF-8
<?xml version="1.0" encoding="utf-8" ?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:id="http://x-road.eu/xsd/identifiers" xmlns:xroad="http://x-road.eu/xsd/xroad.xsd">
<SOAP-ENV:Header xmlns:ns4="http://x-road.eu/xsd/representation.xsd">
<xroad:client id:objectType="MEMBER">
<id:xRoadInstance>EE</id:xRoadInstance>
<id:memberClass>GOV</id:memberClass>
<id:memberCode>TS1OWNER</id:memberCode>
</xroad:client>
<xroad:service id:objectType="SERVICE">
<id:xRoadInstance>EE</id:xRoadInstance>
<id:memberClass>GOV</id:memberClass>
<id:memberCode>TS1OWNER</id:memberCode>
<id:serviceCode>addressChange</id:serviceCode>
</xroad:service>
<xroad:id>7f47514b-a6eb-40ce-afea-34e81d7b38a3</xroad:id>
<xroad:protocolVersion>4.0</xroad:protocolVersion>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<xroad:addressChange>
<xroad:server id:objectType="SERVER">
<id:xRoadInstance>EE</id:xRoadInstance>
<id:memberClass>GOV</id:memberClass>
<id:memberCode>TS1OWNER</id:memberCode>
<id:serverCode>TS1</id:serverCode>
</xroad:server>
<xroad:address>security-server.address</xroad:address>
</xroad:addressChange>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
--jetty832974847lp2nei0x
Content-Type: application/octet-stream
signature-algorithm-id: SHA512withRSA
[OWNER SIGNATURE BYTES]
--jetty832974847lp2nei0x
Content-Type: application/octet-stream
[OWNER CERTIFICATE BYTES]
--jetty832974847lp2nei0x
Content-Type: application/octet-stream
[OWNER CERTIFICATE OCSP RESPONSE BYTES]
--jetty832974847lp2nei0x--Response message
<?xml version="1.0" encoding="utf-8" ?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:id="http://x-road.eu/xsd/identifiers" xmlns:xroad="http://x-road.eu/xsd/xroad.xsd">
<SOAP-ENV:Header xmlns:ns4="http://x-road.eu/xsd/representation.xsd">
<xroad:client id:objectType="MEMBER">
<id:xRoadInstance>EE</id:xRoadInstance>
<id:memberClass>GOV</id:memberClass>
<id:memberCode>TS1OWNER</id:memberCode>
</xroad:client>
<xroad:service id:objectType="SERVICE">
<id:xRoadInstance>EE</id:xRoadInstance>
<id:memberClass>GOV</id:memberClass>
<id:memberCode>TS1OWNER</id:memberCode>
<id:serviceCode>addressChange</id:serviceCode>
</xroad:service>
<xroad:id>7f47514b-a6eb-40ce-afea-34e81d7b38a3</xroad:id>
<xroad:protocolVersion>4.0</xroad:protocolVersion>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<xroad:addressChangeResponse>
<xroad:server id:objectType="SERVER">
<id:xRoadInstance>EE</id:xRoadInstance>
<id:memberClass>GOV</id:memberClass>
<id:memberCode>TS1OWNER</id:memberCode>
<id:serverCode>TS1</id:serverCode>
</xroad:server>
<xroad:address>security-server.address</xroad:address>
<xroad:requestId>1133</xroad:requestId>
</xroad:addressChangeResponse>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>Request message
--jetty1580127502lpv3owhr
Content-Type: text/xml; charset=UTF-8
<?xml version="1.0" encoding="utf-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:id="http://x-road.eu/xsd/identifiers" xmlns:xroad="http://x-road.eu/xsd/xroad.xsd">
<SOAP-ENV:Header xmlns:ns4="http://x-road.eu/xsd/representation.xsd">
<xroad:client id:objectType="MEMBER">
<id:xRoadInstance>EE</id:xRoadInstance>
<id:memberClass>CLASS</id:memberClass>
<id:memberCode>MEMBER</id:memberCode>
</xroad:client>
<xroad:service id:objectType="SERVICE">
<id:xRoadInstance>EE</id:xRoadInstance>
<id:memberClass>BUSINESS</id:memberClass>
<id:memberCode>servicemember2</id:memberCode>
<id:serviceCode>clientDisable</id:serviceCode>
</xroad:service>
<xroad:id>4df02e1f-fc9b-4ae4-b61b-0dc1f7d28d1c</xroad:id>
<xroad:protocolVersion>4.0</xroad:protocolVersion>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<xroad:clientDisable>
<xroad:server id:objectType="SERVER">
<id:xRoadInstance>EE</id:xRoadInstance>
<id:memberClass>CLASS</id:memberClass>
<id:memberCode>MEMBER</id:memberCode>
<id:serverCode>SS1</id:serverCode>
</xroad:server>
<xroad:client id:objectType="SUBSYSTEM">
<id:xRoadInstance>EE</id:xRoadInstance>
<id:memberClass>CLASS</id:memberClass>
<id:memberCode>MEMBER</id:memberCode>
<id:subsystemCode>SUBSYSTEM</id:subsystemCode>
</xroad:client>
</xroad:clientDisable>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
--jetty1580127502lpv3owhr
Content-Type: application/octet-stream
signature-algorithm-id: SHA512withRSA
[OWNER SIGNATURE BYTES]
--jetty1580127502lpv3owhr
Content-Type: application/octet-stream
[OWNER CERTIFICATE BYTES]
--jetty1580127502lpv3owhr
Content-Type: application/octet-stream
[OWNER CERTIFICATE OCSP RESPONSE BYTES]
--jetty1580127502lpv3owhr--Response message
<?xml version="1.0" encoding="utf-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:id="http://x-road.eu/xsd/identifiers" xmlns:xroad="http://x-road.eu/xsd/xroad.xsd">
<SOAP-ENV:Header xmlns:ns4="http://x-road.eu/xsd/representation.xsd">
<xroad:client id:objectType="MEMBER">
<id:xRoadInstance>EE</id:xRoadInstance>
<id:memberClass>CLASS</id:memberClass>
<id:memberCode>MEMBER</id:memberCode>
</xroad:client>
<xroad:service id:objectType="SERVICE">
<id:xRoadInstance>EE</id:xRoadInstance>
<id:memberClass>BUSINESS</id:memberClass>
<id:memberCode>servicemember2</id:memberCode>
<id:serviceCode>clientDisable</id:serviceCode>
</xroad:service>
<xroad:id>4df02e1f-fc9b-4ae4-b61b-0dc1f7d28d1c</xroad:id>
<xroad:protocolVersion>4.0</xroad:protocolVersion>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<xroad:clientDisableResponse>
<xroad:server id:objectType="SERVER">
<id:xRoadInstance>EE</id:xRoadInstance>
<id:memberClass>CLASS</id:memberClass>
<id:memberCode>MEMBER</id:memberCode>
<id:serverCode>SS1</id:serverCode>
</xroad:server>
<xroad:client id:objectType="MEMBER">
<id:xRoadInstance>EE</id:xRoadInstance>
<id:memberClass>CLASS</id:memberClass>
<id:memberCode>MEMBER</id:memberCode>
</xroad:client>
<xroad:requestId>1122</xroad:requestId>
</xroad:clientDisableResponse>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>Request message
--jetty2041213627lpv3ox3x
Content-Type: text/xml; charset=UTF-8
<?xml version="1.0" encoding="utf-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:id="http://x-road.eu/xsd/identifiers" xmlns:xroad="http://x-road.eu/xsd/xroad.xsd">
<SOAP-ENV:Header xmlns:ns4="http://x-road.eu/xsd/representation.xsd">
<xroad:client id:objectType="MEMBER">
<id:xRoadInstance>EE</id:xRoadInstance>
<id:memberClass>CLASS</id:memberClass>
<id:memberCode>MEMBER</id:memberCode>
</xroad:client>
<xroad:service id:objectType="SERVICE">
<id:xRoadInstance>EE</id:xRoadInstance>
<id:memberClass>BUSINESS</id:memberClass>
<id:memberCode>servicemember2</id:memberCode>
<id:serviceCode>clientEnable</id:serviceCode>
</xroad:service>
<xroad:id>0655793f-9adb-4e57-a0ec-6ea5bf69ce8a</xroad:id>
<xroad:protocolVersion>4.0</xroad:protocolVersion>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<xroad:clientEnable>
<xroad:server id:objectType="SERVER">
<id:xRoadInstance>EE</id:xRoadInstance>
<id:memberClass>CLASS</id:memberClass>
<id:memberCode>MEMBER</id:memberCode>
<id:serverCode>SS1</id:serverCode>
</xroad:server>
<xroad:client id:objectType="SUBSYSTEM">
<id:xRoadInstance>EE</id:xRoadInstance>
<id:memberClass>CLASS</id:memberClass>
<id:memberCode>MEMBER</id:memberCode>
<id:subsystemCode>SUBSYSTEM</id:subsystemCode>
</xroad:client>
</xroad:clientEnable>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope>
--jetty2041213627lpv3ox3x
Content-Type: application/octet-stream
signature-algorithm-id: SHA512withRSA
[OWNER SIGNATURE BYTES]
--jetty2041213627lpv3ox3x
Content-Type: application/octet-stream
[OWNER CERTIFICATE BYTES]
--jetty2041213627lpv3ox3x
Content-Type: application/octet-stream
[OWNER CERTIFICATE OCSP RESPONSE BYTES]
--jetty2041213627lpv3ox3x--
Response message
<?xml version="1.0" encoding="utf-8"?>
<SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
xmlns:id="http://x-road.eu/xsd/identifiers" xmlns:xroad="http://x-road.eu/xsd/xroad.xsd">
<SOAP-ENV:Header xmlns:ns4="http://x-road.eu/xsd/representation.xsd">
<xroad:client id:objectType="MEMBER">
<id:xRoadInstance>EE</id:xRoadInstance>
<id:memberClass>CLASS</id:memberClass>
<id:memberCode>MEMBER</id:memberCode>
</xroad:client>
<xroad:service id:objectType="SERVICE">
<id:xRoadInstance>EE</id:xRoadInstance>
<id:memberClass>BUSINESS</id:memberClass>
<id:memberCode>servicemember2</id:memberCode>
<id:serviceCode>clientEnable</id:serviceCode>
</xroad:service>
<xroad:id>0655793f-9adb-4e57-a0ec-6ea5bf69ce8a</xroad:id>
<xroad:protocolVersion>4.0</xroad:protocolVersion>
</SOAP-ENV:Header>
<SOAP-ENV:Body>
<xroad:clientEnableResponse>
<xroad:server id:objectType="SERVER">
<id:xRoadInstance>EE</id:xRoadInstance>
<id:memberClass>CLASS</id:memberClass>
<id:memberCode>MEMBER</id:memberCode>
<id:serverCode>SS1</id:serverCode>
</xroad:server>
<xroad:client id:objectType="MEMBER">
<id:xRoadInstance>EE</id:xRoadInstance>
<id:memberClass>CLASS</id:memberClass>
<id:memberCode>MEMBER</id:memberCode>
</xroad:client>
<xroad:requestId>1122</xroad:requestId>
</xroad:clientEnableResponse>
</SOAP-ENV:Body>
</SOAP-ENV:Envelope><?xml version="1.0" encoding="UTF-8" standalone="no"?>
<wsdl:definitions xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" xmlns:tns="http://x-road.eu/centralservice/" xmlns:wsdl="http://schemas.xmlsoap.org/wsdl/" xmlns:xroad="http://x-road.eu/xsd/xroad.xsd" xmlns:xsd="http://www.w3.org/2001/XMLSchema" name="centralservice" targetNamespace="http://x-road.eu/centralservice/">
<wsdl:types>
<!-- Schema for identifiers (reduced) -->
<xsd:schema xmlns="http://x-road.eu/xsd/identifiers" elementFormDefault="qualified" targetNamespace="http://x-road.eu/xsd/identifiers">
<xsd:complexType name="XRoadIdentifierType">
<xsd:annotation>
<xsd:documentation>Globally unique identifier in the
X-Road system. Identifier consists of object type
specifier and list of hierarchical codes
(starting with code that identifiers the X-Road
instance).
</xsd:documentation>
</xsd:annotation>
<xsd:sequence>
<xsd:element minOccurs="0" ref="xRoadInstance"/>
<xsd:element minOccurs="0" ref="memberClass"/>
<xsd:element minOccurs="0" ref="memberCode"/>
<xsd:element minOccurs="0" ref="subsystemCode"/>
<xsd:element minOccurs="0" ref="serverCode"/>
<xsd:element minOccurs="0" ref="serviceCode"/>
<xsd:element minOccurs="0" ref="serviceVersion"/>
</xsd:sequence>
<xsd:attribute ref="objectType" use="required"/>
</xsd:complexType>
<xsd:simpleType name="XRoadObjectType">
<xsd:annotation>
<xsd:documentation>Enumeration for X-Road identifier
types that can be used in requests.
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="xsd:string">
<xsd:enumeration value="MEMBER"/>
<xsd:enumeration value="SUBSYSTEM"/>
<xsd:enumeration value="SERVER"/>
<xsd:enumeration value="SERVICE"/>
</xsd:restriction>
</xsd:simpleType>
<xsd:element name="xRoadInstance" type="xsd:string">
<xsd:annotation>
<xsd:documentation>Identifies the X-Road instance.
This field is applicable to all identifier
types.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="memberClass" type="xsd:string">
<xsd:annotation>
<xsd:documentation>Type of the member (company,
government institution, private person, etc.)
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="memberCode" type="xsd:string">
<xsd:annotation>
<xsd:documentation>Code that uniquely identifies a
member of given member type.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="subsystemCode" type="xsd:string">
<xsd:annotation>
<xsd:documentation>Code that uniquely identifies a
subsystem of given X-Road member.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="serviceCode" type="xsd:string">
<xsd:annotation>
<xsd:documentation>Code that uniquely identifies a
service offered by given X-Road member or
subsystem.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="serviceVersion" type="xsd:string">
<xsd:annotation>
<xsd:documentation>Version of the service.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="serverCode" type="xsd:string">
<xsd:annotation>
<xsd:documentation>Code that uniquely identifies
Security Server offered by a given X-Road member
or subsystem.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:attribute name="objectType" type="XRoadObjectType"/>
<xsd:complexType name="XRoadClientIdentifierType">
<xsd:complexContent>
<xsd:restriction base="XRoadIdentifierType">
<xsd:sequence>
<xsd:element ref="xRoadInstance"/>
<xsd:element ref="memberClass"/>
<xsd:element ref="memberCode"/>
<xsd:element minOccurs="0" ref="subsystemCode"/>
</xsd:sequence>
</xsd:restriction>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="XRoadServiceIdentifierType">
<xsd:complexContent>
<xsd:restriction base="XRoadIdentifierType">
<xsd:sequence>
<xsd:element ref="xRoadInstance"/>
<xsd:element ref="memberClass"/>
<xsd:element ref="memberCode"/>
<xsd:element minOccurs="0" ref="subsystemCode"/>
<xsd:element ref="serviceCode"/>
<xsd:element minOccurs="0" ref="serviceVersion"/>
</xsd:sequence>
</xsd:restriction>
</xsd:complexContent>
</xsd:complexType>
<xsd:complexType name="XRoadSecurityServerIdentifierType">
<xsd:complexContent>
<xsd:restriction base="XRoadIdentifierType">
<xsd:sequence>
<xsd:element ref="xRoadInstance"/>
<xsd:element ref="memberClass"/>
<xsd:element ref="memberCode"/>
<xsd:element ref="serverCode"/>
</xsd:sequence>
</xsd:restriction>
</xsd:complexContent>
</xsd:complexType>
</xsd:schema>
<!-- Schema for requests (reduced) -->
<xsd:schema xmlns="http://www.w3.org/2001/XMLSchema" xmlns:tns="http://x-road.eu/xsd/xroad.xsd" xmlns:id="http://x-road.eu/xsd/identifiers" targetNamespace="http://x-road.eu/xsd/xroad.xsd" elementFormDefault="qualified">
<xsd:import namespace="http://x-road.eu/xsd/identifiers" id="id"/>
<xsd:element name="clientReg" type="tns:ClientRequestType"/>
<xsd:element name="clientRegResponse" type="tns:ClientRequestType"/>
<xsd:element name="clientDeletion" type="tns:ClientRequestType"/>
<xsd:element name="clientDeletionResponse" type="tns:ClientRequestType"/>
<xsd:element name="authCertReg" type="tns:AuthCertRegRequestType"/>
<xsd:element name="authCertRegResponse" type="tns:AuthCertRegRequestType"/>
<xsd:element name="authCertDeletion" type="tns:AuthCertDeletionRequestType"/>
<xsd:element name="authCertDeletionResponse" type="tns:AuthCertDeletionRequestType"/>
<xsd:element name="ownerChange" type="tns:ClientRequestType"/>
<xsd:element name="ownerChangeResponse" type="tns:ClientRequestType"/>
<xsd:element name="addressChange" type="tns:AddressChangeRequestType"/>
<xsd:element name="addressChangeResponse" type="tns:AddressChangeRequestType"/>
<!-- Header fields -->
<xsd:element name="client" type="id:XRoadClientIdentifierType"/>
<xsd:element name="service" type="id:XRoadServiceIdentifierType"/>
<xsd:element name="id" type="xsd:string"/>
<xsd:element name="protocolVersion" type="xsd:string"/>
<xsd:element name="requestHash" type="xsd:string"/>
<xsd:complexType name="AuthCertRegRequestType">
<xsd:sequence>
<xsd:element name="server" type="id:XRoadSecurityServerIdentifierType">
<xsd:annotation>
<xsd:documentation>Identity of the Security Server the
authentication certificate will be associated with.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="address" type="string" minOccurs="0">
<xsd:annotation>
<xsd:documentation>Address of the Security Server the
authentication certificate will be associated with.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="authCert" type="base64Binary">
<xsd:annotation>
<xsd:documentation>
Contents (in DER encoding) of
the authentication certificate that will
be added to the list of certificates
authenticating the Security Server.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="requestId" type="tns:RequestIdType" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="AuthCertDeletionRequestType">
<xsd:sequence>
<xsd:element name="server" type="id:XRoadSecurityServerIdentifierType">
<xsd:annotation>
<xsd:documentation>Identity of the Security Server the
authentication certificate will be deleted from.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="authCert" type="base64Binary">
<xsd:annotation>
<xsd:documentation>Contents (in DER encoding) of
the authentication certificate that will
be deleted from the list of certificates
authenticating the Security Server.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="requestId" type="tns:RequestIdType" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="ClientRequestType">
<xsd:sequence>
<xsd:element name="server" type="id:XRoadSecurityServerIdentifierType">
<xsd:annotation>
<xsd:documentation>Identifier of the security
server where the client is added to or removed
from (depending on the request type).
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="client" type="id:XRoadClientIdentifierType">
<xsd:annotation>
<xsd:documentation>Identifier of the client
associated with the Security Server. When the
request is for registering client, the client is
added to the Security Server. When the request
is for deleting client, the client is removed
from the clients' list of the Security Server.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="requestId" type="tns:RequestIdType" minOccurs="0"/>
</xsd:sequence>
</xsd:complexType>
<xsd:complexType name="AddressChangeRequestType">
<xsd:sequence>
<xsd:element name="server" type="id:XRoadSecurityServerIdentifierType">
<xsd:annotation>
<xsd:documentation>Identifier of the Security Server the
authentication certificate will be associated with.
</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="address" type="string">
<xsd:annotation>
<xsd:documentation>New address of the Security Server</xsd:documentation>
</xsd:annotation>
</xsd:element>
<xsd:element name="requestId" type="tns:RequestIdType" minOccurs="0" />
</xsd:sequence>
</xsd:complexType>
<xsd:simpleType name="RequestIdType">
<xsd:annotation>
<xsd:documentation>For responses only, unique identifier
of the request that is stored in the Central Server database.
</xsd:documentation>
</xsd:annotation>
<xsd:restriction base="integer"/>
</xsd:simpleType>
</xsd:schema>
</wsdl:types>
<wsdl:message name="requestheader">
<wsdl:part name="client" element="xroad:client"/>
<wsdl:part name="service" element="xroad:service"/>
<wsdl:part name="id" element="xroad:id"/>
<wsdl:part name="protocolVersion" element="xroad:protocolVersion"/>
<wsdl:part name="requestHash" element="xroad:requestHash"/>
</wsdl:message>
<wsdl:message name="clientReg">
<wsdl:part element="xroad:clientReg" name="parameters"/>
</wsdl:message>
<wsdl:message name="clientRegResponse">
<wsdl:part element="xroad:clientRegResponse" name="parameters"/>
</wsdl:message>
<wsdl:message name="clientDeletion">
<wsdl:part element="xroad:clientDeletion" name="parameters"/>
</wsdl:message>
<wsdl:message name="clientDeletionResponse">
<wsdl:part element="xroad:clientDeletionResponse" name="parameters"/>
</wsdl:message>
<wsdl:message name="authCertReg">
<wsdl:part element="xroad:authCertReg" name="parameters"/>
</wsdl:message>
<wsdl:message name="authCertRegResponse">
<wsdl:part element="xroad:authCertRegResponse" name="parameters"/>
</wsdl:message>
<wsdl:message name="authCertDeletion">
<wsdl:part element="xroad:authCertDeletion" name="parameters"/>
</wsdl:message>
<wsdl:message name="authCertDeletionResponse">
<wsdl:part element="xroad:authCertDeletionResponse" name="parameters"/>
</wsdl:message>
<wsdl:message name="ownerChange">
<wsdl:part element="xroad:ownerChange" name="parameters"/>
</wsdl:message>
<wsdl:message name="ownerChangeResponse">
<wsdl:part element="xroad:ownerChangeResponse" name="parameters"/>
</wsdl:message>
<wsdl:message name="addressChange">
<wsdl:part element="xroad:addressChange" name="parameters"/>
</wsdl:message>
<wsdl:message name="addressChangeResponse">
<wsdl:part element="xroad:addressChangeResponse" name="parameters"/>
</wsdl:message>
<wsdl:portType name="centralservice">
<wsdl:operation name="clientReg">
<wsdl:input message="tns:clientReg"/>
<wsdl:output message="tns:clientRegResponse"/>
</wsdl:operation>
<wsdl:operation name="clientDeletion">
<wsdl:input message="tns:clientDeletion"/>
<wsdl:output message="tns:clientDeletionResponse"/>
</wsdl:operation>
<wsdl:operation name="authCertDeletion">
<wsdl:input message="tns:authCertDeletion"/>
<wsdl:output message="tns:authCertDeletionResponse"/>
</wsdl:operation>
<wsdl:operation name="ownerChange">
<wsdl:input message="tns:ownerChange"/>
<wsdl:output message="tns:ownerChangeResponse"/>
</wsdl:operation>
<wsdl:operation name="addressChange">
<wsdl:input message="tns:addressChange"/>
<wsdl:output message="tns:addressChangeResponse"/>
</wsdl:operation>
</wsdl:portType>
<wsdl:binding name="centralserviceSOAP" type="tns:centralservice">
<soap:binding style="document" transport="http://schemas.xmlsoap.org/soap/http"/>
<wsdl:operation name="clientReg">
<soap:operation soapAction=""/>
<wsdl:input>
<soap:body use="literal"/>
<soap:header message="tns:requestheader" part="client" use="literal"/>
<soap:header message="tns:requestheader" part="service" use="literal"/>
<soap:header message="tns:requestheader" part="id" use="literal"/>
<soap:header message="tns:requestheader" part="protocolVersion" use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal"/>
<soap:header message="tns:requestheader" part="client" use="literal"/>
<soap:header message="tns:requestheader" part="service" use="literal"/>
<soap:header message="tns:requestheader" part="id" use="literal"/>
<soap:header message="tns:requestheader" part="protocolVersion" use="literal"/>
<soap:header message="tns:requestheader" part="requestHash" use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="clientDeletion">
<soap:operation soapAction=""/>
<wsdl:input>
<soap:body use="literal"/>
<soap:header message="tns:requestheader" part="client" use="literal"/>
<soap:header message="tns:requestheader" part="service" use="literal"/>
<soap:header message="tns:requestheader" part="id" use="literal"/>
<soap:header message="tns:requestheader" part="protocolVersion" use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal"/>
<soap:header message="tns:requestheader" part="client" use="literal"/>
<soap:header message="tns:requestheader" part="service" use="literal"/>
<soap:header message="tns:requestheader" part="id" use="literal"/>
<soap:header message="tns:requestheader" part="protocolVersion" use="literal"/>
<soap:header message="tns:requestheader" part="requestHash" use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="authCertDeletion">
<soap:operation soapAction=""/>
<wsdl:input>
<soap:body use="literal"/>
<soap:header message="tns:requestheader" part="client" use="literal"/>
<soap:header message="tns:requestheader" part="service" use="literal"/>
<soap:header message="tns:requestheader" part="id" use="literal"/>
<soap:header message="tns:requestheader" part="protocolVersion" use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal"/>
<soap:header message="tns:requestheader" part="client" use="literal"/>
<soap:header message="tns:requestheader" part="service" use="literal"/>
<soap:header message="tns:requestheader" part="id" use="literal"/>
<soap:header message="tns:requestheader" part="protocolVersion" use="literal"/>
<soap:header message="tns:requestheader" part="requestHash" use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="ownerChange">
<soap:operation soapAction=""/>
<wsdl:input>
<soap:body use="literal"/>
<soap:header message="tns:requestheader" part="client" use="literal"/>
<soap:header message="tns:requestheader" part="service" use="literal"/>
<soap:header message="tns:requestheader" part="id" use="literal"/>
<soap:header message="tns:requestheader" part="protocolVersion" use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal"/>
<soap:header message="tns:requestheader" part="client" use="literal"/>
<soap:header message="tns:requestheader" part="service" use="literal"/>
<soap:header message="tns:requestheader" part="id" use="literal"/>
<soap:header message="tns:requestheader" part="protocolVersion" use="literal"/>
<soap:header message="tns:requestheader" part="requestHash" use="literal"/>
</wsdl:output>
</wsdl:operation>
<wsdl:operation name="addressChange">
<soap:operation soapAction=""/>
<wsdl:input>
<soap:body use="literal"/>
<soap:header message="tns:requestheader" part="client" use="literal"/>
<soap:header message="tns:requestheader" part="service" use="literal"/>
<soap:header message="tns:requestheader" part="id" use="literal"/>
<soap:header message="tns:requestheader" part="protocolVersion" use="literal"/>
</wsdl:input>
<wsdl:output>
<soap:body use="literal"/>
<soap:header message="tns:requestheader" part="client" use="literal"/>
<soap:header message="tns:requestheader" part="service" use="literal"/>
<soap:header message="tns:requestheader" part="id" use="literal"/>
<soap:header message="tns:requestheader" part="protocolVersion" use="literal"/>
<soap:header message="tns:requestheader" part="requestHash" use="literal"/>
</wsdl:output>
</wsdl:operation>
</wsdl:binding>
<wsdl:service name="centralservice">
<wsdl:port binding="tns:centralserviceSOAP" name="centralserviceSOAP">
<soap:address location="http://INSERT_MANAGEMENT_SERVICE_ADDRESS_HERE"/>
</wsdl:port>
</wsdl:service>
</wsdl:definitions>