diff --git a/doc/TEST_API.md b/doc/TEST_API.md index 3c03204..5b10a9e 100644 --- a/doc/TEST_API.md +++ b/doc/TEST_API.md @@ -75,7 +75,7 @@ curl --location -k 'https://localhost:8090/about/version' and expected response: ``` -1.14.3 +1.14.4 ``` ## Self Description API diff --git a/doc/TRUEConnector/component-overview.md b/doc/TRUEConnector/component-overview.md index fb44afd..ffd8ef6 100644 --- a/doc/TRUEConnector/component-overview.md +++ b/doc/TRUEConnector/component-overview.md @@ -4,8 +4,8 @@ TRUE Connector is build using Java11, and use following libraries: | Component | Version | | --------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------- | -| [Execution core container](https://github.com/Engineering-Research-and-Development/true-connector-execution_core_container/releases/tag/1.14.3) | 1.14.3 | -| [Basic data app](https://github.com/Engineering-Research-and-Development/true-connector-basic_data_app/releases/tag/0.3.2) | 0.3.2 | +| [Execution core container](https://github.com/Engineering-Research-and-Development/true-connector-execution_core_container/releases/tag/1.14.4) | 1.14.4 | +| [Basic data app](https://github.com/Engineering-Research-and-Development/true-connector-basic_data_app/releases/tag/0.3.3) | 0.3.3 | | [Usage control app](https://github.com/Engineering-Research-and-Development/true-connector-uc_data_app_platoon/releases/tag/1.7.5) | 1.7.5 | | [Pip](https://github.com/Engineering-Research-and-Development/true-connector-uc_data_app_platoon/tree/1.7.5/Docker_Tecnalia_DataUsage/pip) | 1.0.0 | | [Multipart Message Library](https://github.com/Engineering-Research-and-Development/true-connector-multipart_message_library/releases/tag/1.0.17) | 1.0.17 | diff --git a/doc/TRUEConnector/prerequisite.md b/doc/TRUEConnector/prerequisite.md index ef08f4e..d47df4c 100644 --- a/doc/TRUEConnector/prerequisite.md +++ b/doc/TRUEConnector/prerequisite.md @@ -29,7 +29,7 @@ DAPS certificate should be obtained from Certified Authority responsible for the ## Post configuration steps -Once TRUE Connector is successfully configured and is up and running, responsible user for setting up environment and configuring connector should generate new passwords for 2 type of users required for operating with connector. More information how to do this can be found [here](https://github.com/Engineering-Research-and-Development/true-connector-execution_core_container/blob/1.14.3/doc/SECURITY.md#change-default-password). +Once TRUE Connector is successfully configured and is up and running, responsible user for setting up environment and configuring connector should generate new passwords for 2 type of users required for operating with connector. More information how to do this can be found [here](https://github.com/Engineering-Research-and-Development/true-connector-execution_core_container/blob/1.14.4/doc/SECURITY.md#change-default-password). Make sure to update following properties to address your usecase: diff --git a/doc/TRUEConnector/start-stop.md b/doc/TRUEConnector/start-stop.md index 389c34e..9b83ffe 100644 --- a/doc/TRUEConnector/start-stop.md +++ b/doc/TRUEConnector/start-stop.md @@ -89,10 +89,10 @@ You can also check using _docker ps_ command to verify that containers are up an ``` CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES -bc693e1fdb90 rdlabengpa/ids_execution_core_container:1.14.3 "/bin/sh -c 'java -j…" 3 hours ago Up 3 hours (healthy) 0.0.0.0:8087->8086/tcp, :::8087->8086/tcp, 0.0.0.0:8091->8449/tcp, :::8091->8449/tcp, 0.0.0.0:8890->8889/tcp, :::8890->8889/tcp ecc-consumer -28dc87213f68 rdlabengpa/ids_be_data_app:0.3.2 "/bin/sh -c 'java -j…" 3 hours ago Up 3 hours (healthy) 0.0.0.0:8184->8183/tcp, :::8184->8183/tcp, 0.0.0.0:9001->9000/tcp, :::9001->9000/tcp be-dataapp-consumer -9eb157ceb37b rdlabengpa/ids_be_data_app:0.3.2 "/bin/sh -c 'java -j…" 3 hours ago Up 3 hours (healthy) 0.0.0.0:8183->8183/tcp, :::8183->8183/tcp, 0.0.0.0:9000->9000/tcp, :::9000->9000/tcp be-dataapp-provider -44bc21187460 rdlabengpa/ids_execution_core_container:1.14.3 "/bin/sh -c 'java -j…" 3 hours ago Up 3 hours (healthy) 0.0.0.0:8086->8086/tcp, :::8086->8086/tcp, 0.0.0.0:8889->8889/tcp, :::8889->8889/tcp, 0.0.0.0:8090->8449/tcp, :::8090->8449/tcp ecc-provider +bc693e1fdb90 rdlabengpa/ids_execution_core_container:1.14.4 "/bin/sh -c 'java -j…" 3 hours ago Up 3 hours (healthy) 0.0.0.0:8087->8086/tcp, :::8087->8086/tcp, 0.0.0.0:8091->8449/tcp, :::8091->8449/tcp, 0.0.0.0:8890->8889/tcp, :::8890->8889/tcp ecc-consumer +28dc87213f68 rdlabengpa/ids_be_data_app:0.3.3 "/bin/sh -c 'java -j…" 3 hours ago Up 3 hours (healthy) 0.0.0.0:8184->8183/tcp, :::8184->8183/tcp, 0.0.0.0:9001->9000/tcp, :::9001->9000/tcp be-dataapp-consumer +9eb157ceb37b rdlabengpa/ids_be_data_app:0.3.3 "/bin/sh -c 'java -j…" 3 hours ago Up 3 hours (healthy) 0.0.0.0:8183->8183/tcp, :::8183->8183/tcp, 0.0.0.0:9000->9000/tcp, :::9000->9000/tcp be-dataapp-provider +44bc21187460 rdlabengpa/ids_execution_core_container:1.14.4 "/bin/sh -c 'java -j…" 3 hours ago Up 3 hours (healthy) 0.0.0.0:8086->8086/tcp, :::8086->8086/tcp, 0.0.0.0:8889->8889/tcp, :::8889->8889/tcp, 0.0.0.0:8090->8449/tcp, :::8090->8449/tcp ecc-provider b3f4cdb77ed6 rdlabengpa/ids_uc_data_app_platoon:1.7.5 "/bin/sh -c 'java -j…" 3 hours ago Up 3 hours (healthy) 8080/tcp uc-dataapp-consumer a36748901ce1 rdlabengpa/ids_uc_data_app_platoon_pip:v1.0.0 "java -jar pip.jar" 3 hours ago Up 3 hours 0/tcp uc-dataapp-pip-provider d6f77ad9762d rdlabengpa/ids_uc_data_app_platoon:1.7.5 "/bin/sh -c 'java -j…" 3 hours ago Up 3 hours (healthy) 8080/tcp uc-dataapp-provider diff --git a/doc/advancedConfiguration/auditlogs.md b/doc/advancedConfiguration/auditlogs.md index 24127e2..0482718 100644 --- a/doc/advancedConfiguration/auditlogs.md +++ b/doc/advancedConfiguration/auditlogs.md @@ -1,6 +1,6 @@ ### Audit logs -Audit logging is turned **off** by default. If you wish to configure it or even turn off please follow this [document](https://github.com/Engineering-Research-and-Development/true-connector-execution\_core\_container/blob/1.14.3/doc/AUDIT.md) . +Audit logging is turned **off** by default. If you wish to configure it or even turn off please follow this [document](https://github.com/Engineering-Research-and-Development/true-connector-execution\_core\_container/blob/1.14.4/doc/AUDIT.md) . ## Accessing audit logs diff --git a/doc/advancedConfiguration/broker.md b/doc/advancedConfiguration/broker.md index 110855b..eaa7f24 100644 --- a/doc/advancedConfiguration/broker.md +++ b/doc/advancedConfiguration/broker.md @@ -13,4 +13,4 @@ TRUE Connector can register itself on startup, and also unregister when shutting application.selfdescription.registrateOnStartup=true ``` -Information on how TRUE Connector can interact with Broker, can be found on following [link](https://github.com/Engineering-Research-and-Development/true-connector-execution\_core\_container/blob/1.14.3/doc/BROKER.md) +Information on how TRUE Connector can interact with Broker, can be found on following [link](https://github.com/Engineering-Research-and-Development/true-connector-execution\_core\_container/blob/1.14.4/doc/BROKER.md) diff --git a/doc/advancedConfiguration/extendedjwt.md b/doc/advancedConfiguration/extendedjwt.md index 98c7256..0cdbb40 100644 --- a/doc/advancedConfiguration/extendedjwt.md +++ b/doc/advancedConfiguration/extendedjwt.md @@ -1,3 +1,3 @@ ### Extended jwt validation -TRUE Connector can check additional claims from jwToken. For more information please check the [following link](https://github.com/Engineering-Research-and-Development/true-connector-execution_core_container/blob/1.14.3/doc/TRANSPORTCERTSSHA256.md) +TRUE Connector can check additional claims from jwToken. For more information please check the [following link](https://github.com/Engineering-Research-and-Development/true-connector-execution_core_container/blob/1.14.4/doc/TRANSPORTCERTSSHA256.md) diff --git a/doc/contributingTC.md b/doc/contributingTC.md index d9adb87..94829d2 100644 --- a/doc/contributingTC.md +++ b/doc/contributingTC.md @@ -18,4 +18,4 @@ should at least include the following information: * Steps to reproduce (system specs included) * Relevant logs and/or media (optional): e.g. an image -For more details about branches, naming conventions and some suggestions, take a look at following [Developer instructions](https://github.com/Engineering-Research-and-Development/true-connector-execution_core_container/tree/1.14.3#developer-guide-section) \ No newline at end of file +For more details about branches, naming conventions and some suggestions, take a look at following [Developer instructions](https://github.com/Engineering-Research-and-Development/true-connector-execution_core_container/tree/1.14.4#developer-guide-section) \ No newline at end of file diff --git a/doc/cosign.md b/doc/cosign.md index 58ee676..10086ed 100644 --- a/doc/cosign.md +++ b/doc/cosign.md @@ -4,9 +4,9 @@ Docker images that are part of the TRUE Connector are signed using [cosign](http Signed images starts with following versions: -**rdlabengpa/ids\_execution\_core\_container:v1.14.3**\ +**rdlabengpa/ids\_execution\_core\_container:v1.14.4**\ -**rdlabengpa/ids\_be\_data\_app:v0.3.2**\ +**rdlabengpa/ids\_be\_data\_app:v0.3.3**\ **rdlabengpa/ids\_uc\_data\_app\_platoon:v1.7.5**\ @@ -16,9 +16,9 @@ Signed images starts with following versions: Once images are downloaded, you can verify the signature by executing following command, (trueconn.pub file can be found in the root of this repo) and response should be like following ``` -cosign verify --key trueconn.pub rdlabengpa/ids_execution_core_container:v1.14.3 +cosign verify --key trueconn.pub rdlabengpa/ids_execution_core_container:v1.14.4 -Verification for index.docker.io/rdlabengpa/ids_execution_core_container:v1.14.3 -- +Verification for index.docker.io/rdlabengpa/ids_execution_core_container:v1.14.4 -- The following checks were performed on each of these signatures: - The cosign claims were validated - The signatures were verified against the specified public key @@ -40,9 +40,9 @@ The following checks were performed on each of these signatures: ``` ``` -cosign verify --key trueconn.pub rdlabengpa/ids_be_data_app:v0.3.2 +cosign verify --key trueconn.pub rdlabengpa/ids_be_data_app:v0.3.3 -Verification for index.docker.io/rdlabengpa/ids_be_data_app:v0.3.2 -- +Verification for index.docker.io/rdlabengpa/ids_be_data_app:v0.3.3 -- The following checks were performed on each of these signatures: - The cosign claims were validated - The signatures were verified against the specified public key diff --git a/doc/exchange-data.md b/doc/exchange-data.md index cdf90a1..f924c6b 100644 --- a/doc/exchange-data.md +++ b/doc/exchange-data.md @@ -28,7 +28,7 @@ _NOTE_: even that this curl command is exported from Postman, it is noticed seve If this happens, please check body of the request in Postman, and if body is empty, simply copy everything enclosed between\ _--data-raw '_ and _'_ -For more details on request samples, please check following link [Backend DataApp Usage](https://github.com/Engineering-Research-and-Development/market4.0-data\_app\_test\_BE/blob/0.3.2/README.md) +For more details on request samples, please check following link [Backend DataApp Usage](https://github.com/Engineering-Research-and-Development/market4.0-data\_app\_test\_BE/blob/0.3.3/README.md) Be sure to use correct configuration/ports for sender and receiver Data App and Execution Core Container (check .env file). diff --git a/doc/rest-api.md b/doc/rest-api.md index 39a5807..75743ae 100644 --- a/doc/rest-api.md +++ b/doc/rest-api.md @@ -2,4 +2,4 @@ Detailed description of API endpoints provided by TRUE Connector can be found in [link](rest\_api/REST\_API.md) -Bare in mind that all endpoints of the TRUE Connector will require authorization. Please follow [this link](https://github.com/Engineering-Research-and-Development/true-connector-execution\_core\_container/blob/1.14.3/doc/SECURITY.md) to get more information about providing correct credentials for desired request/functionality. \ No newline at end of file +Bare in mind that all endpoints of the TRUE Connector will require authorization. Please follow [this link](https://github.com/Engineering-Research-and-Development/true-connector-execution\_core\_container/blob/1.14.4/doc/SECURITY.md) to get more information about providing correct credentials for desired request/functionality. \ No newline at end of file diff --git a/doc/rest_api/REST_API.md b/doc/rest_api/REST_API.md index 26bc99e..2ebdd52 100644 --- a/doc/rest_api/REST_API.md +++ b/doc/rest_api/REST_API.md @@ -3,7 +3,7 @@ The TRUE Connector will use two protocols (http and https) as described by the Docker Compose File. Overview of all available endpoints: -*NOTE* Endpoints are protected with credentials, for more details, please check [this link](https://github.com/Engineering-Research-and-Development/true-connector-execution_core_container/blob/1.14.3/doc/SECURITY.md) +*NOTE* Endpoints are protected with credentials, for more details, please check [this link](https://github.com/Engineering-Research-and-Development/true-connector-execution_core_container/blob/1.14.4/doc/SECURITY.md) | **Method** | **Endpoint** | **Usage** | **Returns** | | ---------- | ------------ | --------- | ----------- | @@ -38,5 +38,5 @@ Swagger UI for representation CRUD operations: ![Resource representation](Resource_Representation_Swagger.jpg "Resource representation swagger API") -On following [link](https://github.com/Engineering-Research-and-Development/true-connector-execution_core_container/blob/1.14.3/doc/SELF_DESCRIPTION.md), you can find more detailed explanation of endpoints, with example requests. +On following [link](https://github.com/Engineering-Research-and-Development/true-connector-execution_core_container/blob/1.14.4/doc/SELF_DESCRIPTION.md), you can find more detailed explanation of endpoints, with example requests. diff --git a/doc/security.md b/doc/security.md index c21af88..fc6e015 100644 --- a/doc/security.md +++ b/doc/security.md @@ -47,7 +47,7 @@ Once certificate is generated, following instruction from previous link, you can TRUE Connector has several ways to check the integrity: * [Docker cosing check](cosign.md) - * [Healthcheck](https://github.com/Engineering-Research-and-Development/true-connector-execution_core_container/blob/1.14.3/doc/HEALTHCHECK.md) + * [Healthcheck](https://github.com/Engineering-Research-and-Development/true-connector-execution_core_container/blob/1.14.4/doc/HEALTHCHECK.md) * Verification of the components itself, that will check if current version of subcomponent is verified or not; Each component (Execution Core Container, Basic DataApp and Platoon Usage Control) should on startup log somethign like following: diff --git a/doc/selfDescriptionAPI/self-description-API.md b/doc/selfDescriptionAPI/self-description-API.md index ec10cc3..90ad2fb 100644 --- a/doc/selfDescriptionAPI/self-description-API.md +++ b/doc/selfDescriptionAPI/self-description-API.md @@ -1,6 +1,6 @@ ## Self Description API -To manage your Self Description Document please check following [link](https://github.com/Engineering-Research-and-Development/true-connector-execution\_core\_container/blob/1.14.3/doc/SELF\_DESCRIPTION.md) +To manage your Self Description Document please check following [link](https://github.com/Engineering-Research-and-Development/true-connector-execution\_core\_container/blob/1.14.4/doc/SELF\_DESCRIPTION.md) You can copy existing valid self-description.json document to following location **/ecc\_resources\_consumer** or **/ecc\_resources\_provider** folders, for consumer or provider. diff --git a/doc/user_management.md b/doc/user_management.md index 4fba3f5..d8eb055 100644 --- a/doc/user_management.md +++ b/doc/user_management.md @@ -23,5 +23,5 @@ Both user credentials are not persisted anywhere beside properties files, and th ## Modifying password for a user -Once new password is generated, (described [here](https://github.com/Engineering-Research-and-Development/true-connector-execution_core_container/blob/1.14.3/doc/SECURITY.md#change-default-password)) user should send encoded password to the operations user, which should be the only one who can modify connector property file. That user will update property file and restart TRUE Connector, so that new password will be loaded by the connector. +Once new password is generated, (described [here](https://github.com/Engineering-Research-and-Development/true-connector-execution_core_container/blob/1.14.4/doc/SECURITY.md#change-default-password)) user should send encoded password to the operations user, which should be the only one who can modify connector property file. That user will update property file and restart TRUE Connector, so that new password will be loaded by the connector. diff --git a/docker-compose.yml b/docker-compose.yml index 09544d5..8e69a84 100644 --- a/docker-compose.yml +++ b/docker-compose.yml @@ -1,7 +1,7 @@ version: '3.1' services: ecc-provider: - image: rdlabengpa/ids_execution_core_container:v1.14.3 + image: rdlabengpa/ids_execution_core_container:v1.14.4 deploy: resources: limits: @@ -101,7 +101,7 @@ services: - ./uc-dataapp-pip_resources_provider:/etc be-dataapp-provider: - image: rdlabengpa/ids_be_data_app:v0.3.2 + image: rdlabengpa/ids_be_data_app:v0.3.3 deploy: resources: limits: @@ -137,7 +137,7 @@ services: - ./ecc_cert:/cert ecc-consumer: - image: rdlabengpa/ids_execution_core_container:v1.14.3 + image: rdlabengpa/ids_execution_core_container:v1.14.4 deploy: resources: limits: @@ -237,7 +237,7 @@ services: - ./uc-dataapp-pip_resources_consumer:/etc be-dataapp-consumer: - image: rdlabengpa/ids_be_data_app:v0.3.2 + image: rdlabengpa/ids_be_data_app:v0.3.3 deploy: resources: limits: