SIVA-672 remove SOAP interface

OSS_USED.md

@@ -9,7 +9,7 @@ Libraries license information was obtained using the following command:
 ./mvnw license:aggregate-add-third-party
 ```
 
-Lists of 47 third-party dependencies.
+Lists of 44 third-party dependencies.
      (The Apache Software License, Version 2.0) co.elastic.logging:logback-ecs-encoder (co.elastic.logging:logback-ecs-encoder:1.6.0 - https://github.com/elastic/ecs-logging-java/logback-ecs-encoder)
      (Apache License, Version 2.0) Guava: Google Core Libraries for Java (com.google.guava:guava:33.1.0-jre - https://github.com/google/guava)
      (3-Clause BSD License) jcabi-manifests (com.jcabi:jcabi-manifests:2.1.0 - https://www.jcabi.com/jcabi-manifests)
@@ -26,9 +26,6 @@ Lists of 47 third-party dependencies.
      (European Union Public License 1.1) TimeStampToken Validation Service (ee.openid.siva:timestamptoken-validation-service:3.7.0 - https://github.com/open-eid/SiVa/validation-services-parent/timestamptoken-validation-service)
      (European Union Public License 1.1) tsl-loader (ee.openid.siva:tsl-loader:3.7.0 - https://github.com/open-eid/SiVa/validation-services-parent/tsl-loader)
      (European Union Public License 1.1) validation-commons (ee.openid.siva:validation-commons:3.7.0 - https://github.com/open-eid/SiVa/validation-services-parent/validation-commons)
-     (Eclipse Distribution License - v 1.0) Jakarta XML Web Services API (jakarta.xml.ws:jakarta.xml.ws-api:4.0.1 - https://github.com/jakartaee/jax-ws-api)
-     (Apache-2.0) Apache CXF Runtime JAX-WS Frontend (org.apache.cxf:cxf-rt-frontend-jaxws:4.0.4 - https://cxf.apache.org)
-     (Apache-2.0) Apache CXF Runtime HTTP Transport (org.apache.cxf:cxf-rt-transports-http:4.0.4 - https://cxf.apache.org)
      (Apache License, Version 2.0) Apache PDFBox (org.apache.pdfbox:pdfbox:2.0.31 - https://www.apache.org/pdfbox-parent/pdfbox/)
      (Bouncy Castle Licence) Bouncy Castle PKIX, CMS, EAC, TSP, PKCS, OCSP, CMP, and CRMF APIs (org.bouncycastle:bcpkix-jdk18on:1.76 - https://www.bouncycastle.org/java.html)
      (Bouncy Castle Licence) Bouncy Castle Provider (org.bouncycastle:bcprov-jdk18on:1.76 - https://www.bouncycastle.org/java.html)

README.md

@@ -5,7 +5,7 @@
 [![SiVa CI with Maven](https://github.com/open-eid/siva/actions/workflows/siva-verify.yml/badge.svg?branch=master)](https://github.com/open-eid/siva/actions/workflows/siva-verify.yml)
 [![GitHub license](https://img.shields.io/badge/license-EUPLv1.1-blue.svg)](https://raw.githubusercontent.com/open-eid/SiVa/develop/LICENSE.md)
 
-SiVa is digital signature validation web service that provides JSON and SOAP API to validate following file types:
+SiVa is digital signature validation web service that provides JSON API to validate following file types:
 
 * Estonian DDOC containers
 * Estonian BDOC containers with TimeMark and TimeStamp signatures
@@ -68,7 +68,7 @@ Logs for all running containers can be viewed at http://localhost:11080.
 SiVa project compiles **2 fat executable JAR** files that You can run after successfully building the
 project by issuing below command:
 
-**Starting the SiVa REST and SOAP webservice. NB! X.X.X denotes the version you are running.**
+**Starting the SiVa REST webservice. NB! X.X.X denotes the version you are running.**
 
 ```bash
 java -jar siva-parent/siva-webapp/target/siva-webapp-X.X.X-exec.jar

docs/index.md

@@ -4,7 +4,7 @@
     <img src="img/siva/eu_logo.svg" />
 </div>
 
-SiVa is digital signature validation web service that provides SOAP and JSON
+SiVa is digital signature validation web service that provides JSON
 API to validate following file types:
 
  * Estonian DDOC containers
@@ -28,7 +28,7 @@ SiVa architecture document will cover:
   main SiVa subsystems and base validation Java libraries
   used for different validation services
 * [**Interfaces**](siva3/interfaces) - Description of SiVa
-   SOAP and JSON API request and response
+  JSON API request and response
 * [**Deployment**](siva3/deployment) - gives general overview of
   servers required when deploying SiVa validation web service
   into production

docs/siva3/background.md

@@ -2,7 +2,7 @@
 
 ## What is SiVa?
 
-SiVa (Signature Validation) web service provides JSON and SOAP based API web interface to validate digital signatures.
+SiVa (Signature Validation) web service provides JSON based API web interface to validate digital signatures.
 Please take a look in [Validation Policy](../appendix/validation_policy/) section for supported formats and applied constraints.
 
 SiVa uses following Java libraries and command line utilities:
@@ -34,7 +34,7 @@ SiVa will use the following functionality of DigiDoc4J:
 
 ## Main features of SiVa validation service:
 
-- SOAP and REST/JSON API to validate signatures.
-- SOAP and REST/JSON API to retrieve data files from DDOC containers.
-- SOAP API is compatible with X-Road v6.
-- Signing of validation report.
+- REST/JSON API to validate signatures.
+- REST/JSON API to retrieve data files from DDOC containers.
+- REST/JSON API is compatible with X-Road v6.
+- Signing of validation report.

docs/siva3/deployment.md

@@ -10,7 +10,7 @@ In the following section, a description of each network node element is describe
 |------|-------------|
 | **Load balancer server** | Load balancer distributes traffic between SiVa server nodes when there is more than one Siva server instance running. SiVa does not set any specific requirements for load balancer. As an example, the nginx reverse proxy is used.                                                                                                                                                                                                                                                                                                                                                                           |
 | **Siva server** | The **SiVa webapp** service is set up to run on SiVa server.<br/>SiVa web application is executable Spring Boot JAR file. This means all the dependencies and servlet containers are packaged inside single JAR file. The JAR file can be placed anywhere in server and the JAR must be marked executable if its not already.<br/><br/>There also should be separate user created to run executable JAR as Linux service.<br/><br/>Read more about running [Spring Boot applications as Linux system service](https://docs.spring.io/spring-boot/docs/current/reference/html/deployment-install.html#deployment-service) |
-| **X-road security server** | A standard X-road security server setup. The SiVa validation service wsdl has to be registered to provide service to other organisations using XRoad infrastructure. Setting up XRoad Security server is out of scope for SiVa documentation (see the [official installation instructions](https://www.x-tee.ee/docs/live/xroad/ig-ss_x-road_v6_security_server_installation_guide.html)).                                                                                                                                                                                                                     |
+| **X-road security server** | A standard X-road security server setup. SiVa validation service endpoints have to be registered to provide service to other organisations using XRoad infrastructure. Setting up XRoad Security server is out of scope for SiVa documentation (see the [official installation instructions](https://www.x-tee.ee/docs/live/xroad/ig-ss_x-road_v6_security_server_installation_guide.html)).|
 | **Demo server** | Demo server hosts the **Demo webapp** provided within SiVa project as a reference client implementation. <ul><li>Demo webapp - single Java web application that provides a simple form to upload and validate a signed file in Siva webapp. Demo webapp serves as a tool for evaluating and testing the validation service. </li></ul>                                                                                                                                                                                                                                                                         |
 
 ### Horizontal scaling

docs/siva3/deployment_guide.md

@@ -459,12 +459,6 @@ See the reference list of all common [application properties](http://docs.spring
     TSL is currently used only by Generic and BDOC validators
 
 
-* Configure SOAP services endpoint URL-s displayed in WSDL
-
-| Property | Description |
-| ------ | ----------- |
-| **siva.wsdl.endpoint-url** | SOAP services endpoint URL to what specific service name is added within the application. Must contain only scheme, host and/or port and optional path. Service name must not be added to the url.  |
-
 * TimeMark validation - customizing policies
 
 | Property | Description |
@@ -549,8 +543,6 @@ t-level-signature-filter.countries[1] = LT
 | -------- | ----------- |
 |**siva.service.serviceHost**| An HTTP URL link to the Siva webapp <ul><li>Default: **http://localhost:8080**</li></ul> |
 |**siva.service.jsonServicePath**| Service path in Siva webapp to access the REST/JSON API<ul><li>Default: **/validate**</li></ul> |
-|**siva.service.soapServicePath**| Service path in Siva webapp to access the SOAP API <ul><li>Default: **/soap/validationWebService/validateDocument**</li></ul> |
 |**siva.service.jsonDataFilesServicePath**| Data file service path in Siva webapp to access the REST/JSON API<ul><li>Default: **/getDataFiles**</li></ul> |
-|**siva.service.soapDataFilesServicePath**| Data file service path in Siva webapp to access the SOAP API <ul><li>Default: **/soap/dataFilesWebService/getDocumentDataFiles**</li></ul> |
 |**siva.service.trustStore**| Path to Siva webapp truststore on classpath <ul><li>Default: **siva_server_truststore.p12**</li></ul> |
 |**siva.service.trustStorePassword**| Siva webapp truststore password <ul><li>Default: **password**</li></ul> |