Update de.flapdoodle.embed.mongo to 4.13.0 in main #297

atala-dev · 2024-04-30T20:06:15Z

About this PR

📦 Updates de.flapdoodle.embed:de.flapdoodle.embed.mongo from 4.12.6 to 4.13.0

Usage

✅ Please merge!

I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.

If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.

Configure Scala Steward for your repository with a .scala-steward.conf file.

Have a fantastic day writing Scala!

⚙ Adjust future updates

Add this to your .scala-steward.conf file to ignore future updates of this dependency:

updates.ignore = [ { groupId = "de.flapdoodle.embed", artifactId = "de.flapdoodle.embed.mongo" } ]

Or, add this to slow down future updates of this dependency:

dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "de.flapdoodle.embed", artifactId = "de.flapdoodle.embed.mongo" }
}]

^{labels: test-library-update, early-semver-minor, semver-spec-minor, commit-count:1}

## [0.1.1](prism-mediator-v0.1.0...prism-mediator-v0.1.1) (2023-05-23) ### Bug Fixes * execute the ProtocolExecute's jobToRun zio ([#8](#8)) ([5034499](5034499)) * Hardcode the atala prism did identity ([#9](#9)) ([7984eea](7984eea))

…ple (#10)

…orrect content-type header (#3) Co-authored-by: Shailesh Patil <shailesh.patil@iohk.io>

#7)

Added Mongo db driver Added ReactiveMongo Zlayer Added Mongo repo and collection update and query Updated the docker-compose to create the collection and indexes required. Co-authored-by: Shailesh Patil <shailesh.patil@iohk.io>

* feat: mediator rename package and code cleanup

* feat: mediator added test for the mongo repo layer * caching updated the version

) fix: meadiator db bson implicits to store the orginal

…ured logging (#16) * Added more logging and formatted the logging for console, with msgHasH * Added console json formatter * code cleanup * structured login with logstash * updated the package in buildinfo * downgraded the version for logback * updated the version for logback * address pr comments

* add to alias is a set, and not duplicates fixed ussing mongo addtoset * Added tests and Updated the reposne to nochnage in case of the noupdate was done --------- Co-authored-by: Shailesh Patil <shailesh.patil@iohk.io>

Co-authored-by: Fabio Pinheiro <fabiomgpinheiro@gmail.com>

Mediator returns "routing_did" instead of "recipient_did" in keylist response body Fix for ATL-4845

New a Webapp to show the QR Code For ATL-4304 Create a pipeline to build the Mediator App Fix CI setup Disable the test in scalajs Updated the node setup version Co-authored-by: Shailesh Patil <shailesh.patil@iohk.io>

Fix trustPing callback not working For ATL-5077 Same fix as in commit 5034499

Stop documentation to be built (since it has a bug)

Reply to StatusRequest in the messagepickup protocol For ATL-4883

Process a Keylist Query and return a Keylist For ATL-4208

petevielhaber · 2024-05-01T12:19:36Z

Coordinate-Mediation-Protocol.md

+
+It coordinates the mediation configuration between a mediating agent and the recipient.
+
+This protocol follows the request-response message exchange pattern, and only requerires the simple state of waiting for a response or to produce a response.


Suggested change

This protocol follows the request-response message exchange pattern, and only requerires the simple state of waiting for a response or to produce a response.

This protocol follows the request-response message exchange pattern and only requires the simple state of waiting for or producing a response.

petevielhaber · 2024-05-01T12:22:05Z

Mediator-Error_Handling.md

+
+## Custom behavior table
+
+This table defines the expected behavior of the mediator in different scenarios not covered by the specifications.


Suggested change

This table defines the expected behavior of the mediator in different scenarios not covered by the specifications.

This table defines the expected behavior of the mediator in different scenarios that the specification does not cover:

petevielhaber · 2024-05-01T12:22:59Z

Mediator-Error_Handling.md

+* Log the error.
+* Dispatch a problem report as outlined in the table above.
+* Record the problem report and error information in the database.
+Every one of these steps should be traceable back to the initial call via an `XRequestID`, and by the MsgID (the SHA-251 hash of the encrypted message).


Suggested change

Every one of these steps should be traceable back to the initial call via an `XRequestID`, and by the MsgID (the SHA-251 hash of the encrypted message).

These steps should be traceable back to the initial call via an `XRequestID`, and by the MsgID (the SHA-251 hash of the encrypted message).

petevielhaber · 2024-05-01T12:24:12Z

README.md

+
+**#identus-mediator on Discord:**
+
+For the fastest answers, join the [#identus-mediator][Link-Discord] channel in the official Atala Discord and ask your questions, or chat with other Atala developers and pioneers!


This should link to the HL Discord

petevielhaber · 2024-05-01T12:25:00Z

README.md

+DID Comm v2 (Decentralized Identifiers Communication Version 2) is a protocol engineered for secure, private, and decentralized communications between various entities utilizing decentralized identifiers (DIDs). A DID Comm v2 Mediator functions as an intermediary in the communication process, streamlining the exchange of messages among the involved parties.
+
+
+- Establishing Logical Connections - The Mediator empowers entities, which could be individuals or organizations, to forge secure connections amongst themselves. Each entity possesses a unique DID that acts as its identifier within the decentralized network.


Suggested change

- Establishing Logical Connections - The Mediator empowers entities, which could be individuals or organizations, to forge secure connections amongst themselves. Each entity possesses a unique DID that acts as its identifier within the decentralized network.

- **Establishing Logical Connections**: The Mediator empowers entities, which could be individuals or organizations, to forge secure connections amongst themselves. Each entity possesses a unique DID that acts as its identifier within the decentralized network.

petevielhaber · 2024-05-01T12:25:43Z

README.md

+
+
+- Establishing Logical Connections - The Mediator empowers entities, which could be individuals or organizations, to forge secure connections amongst themselves. Each entity possesses a unique DID that acts as its identifier within the decentralized network.
+- DID resolution - When an entity seeks to communicate with another, it resolves the recipient's DID to procure the information necessary to establish a connection. This resolution procedure entails retrieving the recipient's public key and correlated metadata from a decentralized identity infrastructure, which could be a blockchain or distributed ledger.


Suggested change

- DID resolution - When an entity seeks to communicate with another, it resolves the recipient's DID to procure the information necessary to establish a connection. This resolution procedure entails retrieving the recipient's public key and correlated metadata from a decentralized identity infrastructure, which could be a blockchain or distributed ledger.

- **DID resolution**: When an entity seeks to communicate with another, it resolves the recipient's DID to procure the information necessary to establish a connection. This resolution entails retrieving the recipient's public key and correlated metadata from a decentralized identity infrastructure, a blockchain, or a distributed ledger.

petevielhaber · 2024-05-01T12:27:31Z

README.md

+
+- Establishing Logical Connections - The Mediator empowers entities, which could be individuals or organizations, to forge secure connections amongst themselves. Each entity possesses a unique DID that acts as its identifier within the decentralized network.
+- DID resolution - When an entity seeks to communicate with another, it resolves the recipient's DID to procure the information necessary to establish a connection. This resolution procedure entails retrieving the recipient's public key and correlated metadata from a decentralized identity infrastructure, which could be a blockchain or distributed ledger.
+- Message encryption - The sender employs a double encryption technique for the message: initially for the ultimate receiver, and subsequently encapsulates the encrypted message within another encryption layer for the Mediator. This is achieved using the public keys of both the Mediator and the recipient obtained through the DID resolution process. Dual encryption ensures that only the intended recipient has the capacity to decrypt and access the message.


Suggested change

- Message encryption - The sender employs a double encryption technique for the message: initially for the ultimate receiver, and subsequently encapsulates the encrypted message within another encryption layer for the Mediator. This is achieved using the public keys of both the Mediator and the recipient obtained through the DID resolution process. Dual encryption ensures that only the intended recipient has the capacity to decrypt and access the message.

- **Message encryption**: The sender employs a double encryption technique for the message, initially for the ultimate receiver, and subsequently encapsulates the encrypted message within another encryption layer for the Mediator. This procedure is possible using the public keys of both the Mediator and the recipient obtained through the DID resolution process. Dual encryption ensures that only the intended recipient can decrypt and access the message.

petevielhaber · 2024-05-01T12:28:15Z

README.md

+  end
+```
+
+- Message routing - The sender transmits an encrypted message to the Mediator, which serves as a routing agent. In this role, the Mediator receives messages from the sender, decrypts one layer, and forwards them to the appropriate recipient based on the recipient's DID.


Suggested change

- Message routing - The sender transmits an encrypted message to the Mediator, which serves as a routing agent. In this role, the Mediator receives messages from the sender, decrypts one layer, and forwards them to the appropriate recipient based on the recipient's DID.

- **Message routing**: The sender transmits an encrypted message to the Mediator, a routing agent. In this role, the Mediator receives messages from the sender, decrypts one layer, and forwards them to the appropriate recipient based on the recipient's DID.

petevielhaber · 2024-05-01T12:29:05Z

README.md

+```
+
+- Message routing - The sender transmits an encrypted message to the Mediator, which serves as a routing agent. In this role, the Mediator receives messages from the sender, decrypts one layer, and forwards them to the appropriate recipient based on the recipient's DID.
+- Mediation process- The Mediator verifies the authenticity and integrity of the incoming message by checking the digital signature attached to it. This signature ensures that the message was indeed sent by the claimed sender and that it hasn't been tampered with during transmission.


Suggested change

- Mediation process- The Mediator verifies the authenticity and integrity of the incoming message by checking the digital signature attached to it. This signature ensures that the message was indeed sent by the claimed sender and that it hasn't been tampered with during transmission.

- **Mediation process**: The Mediator verifies the authenticity and integrity of the incoming message by checking the digital signature attached to it. This signature ensures that the claimed sender sent the message and hasn't been tampered with during transmission.

petevielhaber · 2024-05-01T12:29:59Z

README.md

+- Message routing - The sender transmits an encrypted message to the Mediator, which serves as a routing agent. In this role, the Mediator receives messages from the sender, decrypts one layer, and forwards them to the appropriate recipient based on the recipient's DID.
+- Mediation process- The Mediator verifies the authenticity and integrity of the incoming message by checking the digital signature attached to it. This signature ensures that the message was indeed sent by the claimed sender and that it hasn't been tampered with during transmission.
+
+- Message decryption - After verifying the message's authenticity, the Mediator decrypted one layer of the message using the mediator's private key, which is securely held by the mediator. Once decrypted, the next message becomes readable (the final plaintext intended for the final user it's still encrypted).


Suggested change

- Message decryption - After verifying the message's authenticity, the Mediator decrypted one layer of the message using the mediator's private key, which is securely held by the mediator. Once decrypted, the next message becomes readable (the final plaintext intended for the final user it's still encrypted).

- **Message decryption**: After verifying the message's authenticity, the mediator decrypted one layer of the message using the mediator's private key, which the mediator securely holds. Once decrypted, the following message becomes readable (the final plaintext intended for the final user is still encrypted).

petevielhaber · 2024-05-01T12:30:56Z

README.md

+- Mediation process- The Mediator verifies the authenticity and integrity of the incoming message by checking the digital signature attached to it. This signature ensures that the message was indeed sent by the claimed sender and that it hasn't been tampered with during transmission.
+
+- Message decryption - After verifying the message's authenticity, the Mediator decrypted one layer of the message using the mediator's private key, which is securely held by the mediator. Once decrypted, the next message becomes readable (the final plaintext intended for the final user it's still encrypted).
+- Optional processing - The Mediator may perform additional processing on the message based on predefined rules or business logic. This could include applying filters, applying policies, or invoking external services.


Suggested change

- Optional processing - The Mediator may perform additional processing on the message based on predefined rules or business logic. This could include applying filters, applying policies, or invoking external services.

- **Optional processing**: The Mediator may perform additional processing on the message based on predefined rules or business logic, including applying filters, applying policies, or invoking external services.

petevielhaber · 2024-05-01T12:32:22Z

README.md

+
+- Message decryption - After verifying the message's authenticity, the Mediator decrypted one layer of the message using the mediator's private key, which is securely held by the mediator. Once decrypted, the next message becomes readable (the final plaintext intended for the final user it's still encrypted).
+- Optional processing - The Mediator may perform additional processing on the message based on predefined rules or business logic. This could include applying filters, applying policies, or invoking external services.
+- Message forwarding - If necessary, the Mediator can further forward the decrypted message to additional entities in the communication flow. This enables multi-party communication scenarios.


Suggested change

- Message forwarding - If necessary, the Mediator can further forward the decrypted message to additional entities in the communication flow. This enables multi-party communication scenarios.

- **Message forwarding**: The mediator can forward the decrypted message to additional entities in the communication flow, enabling multi-party communication scenarios.

petevielhaber · 2024-05-01T12:34:27Z

README.md

+- Optional processing - The Mediator may perform additional processing on the message based on predefined rules or business logic. This could include applying filters, applying policies, or invoking external services.
+- Message forwarding - If necessary, the Mediator can further forward the decrypted message to additional entities in the communication flow. This enables multi-party communication scenarios.
+
+By acting as an intermediary, the DID Comm v2 Mediator helps facilitate secure and private communication between entities while leveraging the decentralized nature of DIDs and cryptographic techniques to ensure the authenticity, integrity, and confidentiality of the messages exchanged.


Suggested change

By acting as an intermediary, the DID Comm v2 Mediator helps facilitate secure and private communication between entities while leveraging the decentralized nature of DIDs and cryptographic techniques to ensure the authenticity, integrity, and confidentiality of the messages exchanged.

By acting as an intermediary, the DID Comm v2 Mediator helps facilitate secure and private communication between entities while leveraging the decentralized nature of DIDs and cryptographic techniques to ensure the message's authenticity, integrity, and confidentiality.

petevielhaber · 2024-05-01T12:34:42Z

README.md

+
+By acting as an intermediary, the DID Comm v2 Mediator helps facilitate secure and private communication between entities while leveraging the decentralized nature of DIDs and cryptographic techniques to ensure the authenticity, integrity, and confidentiality of the messages exchanged.
+
+The mediator is especially useful when the edge entities are not always online, like the mobile paradigm. Usually, we can assume that the mediator is always online.


Suggested change

The mediator is especially useful when the edge entities are not always online, like the mobile paradigm. Usually, we can assume that the mediator is always online.

The mediator is particularly convenient for edge entities that are only sometimes online, such as in the mobile paradigm. It's a practical solution, as we can assume that the mediator is always online.

petevielhaber · 2024-05-01T12:36:17Z

docs/architecture/README.md

+## System Context Diagram
+
+The system context diagram illustrates the high-level interactions and dependencies of the Identus Mediator with
+external components, mainly cloud and edge agents.


Suggested change

external components, mainly cloud and edge agents.

external components, mainly Cloud and Edge Agents.

petevielhaber · 2024-05-01T12:37:03Z

docs/architecture/README.md

+
+## Container Diagram
+
+The container diagram depicts the internal containers/runnables and their relationships within the Identus Mediator.


Suggested change

The container diagram depicts the internal containers/runnables and their relationships within the Identus Mediator.

The container diagram depicts the internal containers and executables and their relationships within the Identus Mediator.

petevielhaber · 2024-05-01T12:38:02Z

docs/architecture/README.md

+  Pickup 3.0, and TrustPing 2.0. It communicates with external systems via HTTP.
+
+- **QR Code Web App**: This component is responsible for displaying a QR code containing an OOB invitation that can be
+  scanned by an edge agent mobile application to initiate a mediation request with the mediator.


Suggested change

scanned by an edge agent mobile application to initiate a mediation request with the mediator.

scannable by an Edge Agent mobile application to initiate a mediation request with the mediator.

petevielhaber · 2024-05-01T12:38:28Z

docs/architecture/README.md

+
+- **User Accounts**: for storing user account information of mediated agents.
+
+- **Message Items**: for storing messages sent by edge and cloud agents.


Suggested change

- **Message Items**: for storing messages sent by edge and cloud agents.

- **Message Items**: for storing messages sent by Edge and Cloud Agents.

petevielhaber · 2024-05-01T12:38:43Z

docs/architecture/README.md

+
+The Mediator Database stores data related to the Identus Mediator. It contains the following collection:
+
+- **User Accounts**: for storing user account information of mediated agents.


Suggested change

- **User Accounts**: for storing user account information of mediated agents.

- **User Accounts**: for storing user account information of Mediated Agents.

petevielhaber · 2024-05-01T12:39:18Z

logging.md

+# Logging
+
+We want traceability from HTTP calls.
+- Each HTTP call needs to generate a call ID (preferably on the proxy). The ID must be within the scope of the ZIO application. So, every log will mention this ID. This ID must return to the user as an HTTP header.


Suggested change

- Each HTTP call needs to generate a call ID (preferably on the proxy). The ID must be within the scope of the ZIO application. So, every log will mention this ID. This ID must return to the user as an HTTP header.

- Each HTTP call must generate a call ID (preferably on the proxy). The ID must be within the scope of the ZIO application. So, every log will mention this ID. This ID must return to the user as an HTTP header.

petevielhaber · 2024-05-01T12:40:03Z

logging.md

+- Each HTTP call needs to generate a call ID (preferably on the proxy). The ID must be within the scope of the ZIO application. So, every log will mention this ID. This ID must return to the user as an HTTP header.
+- In case of errors and problem reports, the user can use those IDs to get support.
+
+A user can receive Level 3 support during the logging retention policies. The user needs to provide the value in the header `X-Request-Id` to get this support.


Suggested change

A user can receive Level 3 support during the logging retention policies. The user needs to provide the value in the header `X-Request-Id` to get this support.

A user can receive Level 3 support during the logging retention policies. To get this support, the user needs to provide the value in the header `X-Request-Id`.

petevielhaber · 2024-05-01T12:40:42Z

logging.md

+
+## Code
+
+To have a concise code, we have created a middleware that modifies the annotations in the scope before each execution of that endpoint and includes the trace ID of the request.


Suggested change

To have a concise code, we have created a middleware that modifies the annotations in the scope before each execution of that endpoint and includes the trace ID of the request.

To have a concise codebase, we have created a middleware that modifies the annotations in the scope before each execution of that endpoint and includes the trace ID of the request.

petevielhaber · 2024-05-01T12:42:37Z

make-trust-ping-example-kotlin.md

+ sbt mediator/run  
+```
+Using  Docker 
+***if you have mac os comment the the line


Suggested change

***if you have mac os comment the the line

***if you have macOS comment the the line

petevielhaber

Minor suggestions throughout

atala-dev and others added 30 commits April 30, 2024 15:32

feat: Add config from application.conf and docker-compose and an exam…

2f661e7

…ple (#10)

Update sbt-native-packager to 1.9.16 in main (#7)

3818846

feat : mediator Trust ping kotlin example (#11)

e84d9a1

Updated the LICENSE

7b64cff

Update scalafmt-core to 3.7.4 in main (#2)

637feb6

docs: mediator Updated kotlin readme for example client to pass the c…

1864051

…orrect content-type header (#3) Co-authored-by: Shailesh Patil <shailesh.patil@iohk.io>

Update scala3-library, ... to 3.3.0 in main (#1)

b7c2baf

fix: make content-type header case insensitive & remove support for ws (

c44219e

#7)

feat: Add Storage (#8)

70e87db

Added Mongo db driver Added ReactiveMongo Zlayer Added Mongo repo and collection update and query Updated the docker-compose to create the collection and indexes required. Co-authored-by: Shailesh Patil <shailesh.patil@iohk.io>

feat: mediator rename package and organise the packages (#12)

09176a2

* feat: mediator rename package and code cleanup

feat: mediator added test for storage layer (#13)

f31e4c9

* feat: mediator added test for the mongo repo layer * caching updated the version

fix: mediator db not storing the orignal value for protected header (#15

d16424a

) fix: meadiator db bson implicits to store the orginal

Update zio-test, zio-test-magnolia, ... to 2.0.15 in main (#14)

714063b

Update sbt-scalafix to 0.11.0 in main (#5)

e21c230

Update sbt-scoverage to 2.0.8 in main (#6)

6bbb394

Update sbt-converter to 1.0.0-beta42 in main (#10)

e3ce6e6

Update sbt-scalajs, scalajs-library_2.13, ... to 1.13.2 in main (#18)

18e1daa

Update sbt to 1.9.1 in main (#20)

980f7f2

Update munit to 1.0.0-M8 in main (#11)

de13618

Co-authored-by: Fabio Pinheiro <fabiomgpinheiro@gmail.com>

fix: field name routing_did in keylist response body (#22)

bb35c99

Mediator returns "routing_did" instead of "recipient_did" in keylist response body Fix for ATL-4845

feat: new a Webapp to show the QR Code (#21)

546827f

New a Webapp to show the QR Code For ATL-4304 Create a pipeline to build the Mediator App Fix CI setup Disable the test in scalajs Updated the node setup version Co-authored-by: Shailesh Patil <shailesh.patil@iohk.io>

fix: trustPing call back not working (#23)

4ee2c4a

Fix trustPing callback not working For ATL-5077 Same fix as in commit 5034499

fix: disabled documentation generation (#24)

5a9d872

Stop documentation to be built (since it has a bug)

fix: mediator unique constraint issue (#25)

17a1851

tests: add integration tests for mediator (#9)

79ae407

feat: reply to StatusRequest (#26)

db3dc7b

Reply to StatusRequest in the messagepickup protocol For ATL-4883

feat: process KeylistQuery and return Keylist (#30)

f590125

Process a Keylist Query and return a Keylist For ATL-4208

mineme0110 force-pushed the main branch from 523a7ba to 38658ff Compare May 1, 2024 09:59

atala-dev requested a review from petevielhaber as a code owner May 1, 2024 09:59

petevielhaber reviewed May 1, 2024

View reviewed changes

petevielhaber requested changes May 1, 2024

View reviewed changes

mineme0110 force-pushed the main branch from 38658ff to 706185c Compare May 1, 2024 14:00

mineme0110 closed this May 1, 2024

mineme0110 force-pushed the main branch from 706185c to c15e3c2 Compare May 1, 2024 16:18

atala-dev deleted the update/main/de.flapdoodle.embed.mongo-4.13.0 branch May 1, 2024 20:07

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Update de.flapdoodle.embed.mongo to 4.13.0 in main #297

Update de.flapdoodle.embed.mongo to 4.13.0 in main #297

atala-dev commented Apr 30, 2024

petevielhaber May 1, 2024

petevielhaber May 1, 2024

petevielhaber May 1, 2024

petevielhaber May 1, 2024

petevielhaber May 1, 2024

petevielhaber May 1, 2024

petevielhaber May 1, 2024

petevielhaber May 1, 2024

petevielhaber May 1, 2024

petevielhaber May 1, 2024

petevielhaber May 1, 2024

petevielhaber May 1, 2024

petevielhaber May 1, 2024

petevielhaber May 1, 2024

petevielhaber May 1, 2024

petevielhaber May 1, 2024

petevielhaber May 1, 2024

petevielhaber May 1, 2024

petevielhaber May 1, 2024

petevielhaber May 1, 2024

petevielhaber May 1, 2024

petevielhaber May 1, 2024

petevielhaber May 1, 2024

petevielhaber left a comment


		It coordinates the mediation configuration between a mediating agent and the recipient.

		This protocol follows the request-response message exchange pattern, and only requerires the simple state of waiting for a response or to produce a response.


		## Custom behavior table

		This table defines the expected behavior of the mediator in different scenarios not covered by the specifications.

	Every one of these steps should be traceable back to the initial call via an `XRequestID`, and by the MsgID (the SHA-251 hash of the encrypted message).
	These steps should be traceable back to the initial call via an `XRequestID`, and by the MsgID (the SHA-251 hash of the encrypted message).


		#identus-mediator on Discord:

		For the fastest answers, join the [#identus-mediator][Link-Discord] channel in the official Atala Discord and ask your questions, or chat with other Atala developers and pioneers!

		DID Comm v2 (Decentralized Identifiers Communication Version 2) is a protocol engineered for secure, private, and decentralized communications between various entities utilizing decentralized identifiers (DIDs). A DID Comm v2 Mediator functions as an intermediary in the communication process, streamlining the exchange of messages among the involved parties.


		- Establishing Logical Connections - The Mediator empowers entities, which could be individuals or organizations, to forge secure connections amongst themselves. Each entity possesses a unique DID that acts as its identifier within the decentralized network.

	- Establishing Logical Connections - The Mediator empowers entities, which could be individuals or organizations, to forge secure connections amongst themselves. Each entity possesses a unique DID that acts as its identifier within the decentralized network.
	- Establishing Logical Connections: The Mediator empowers entities, which could be individuals or organizations, to forge secure connections amongst themselves. Each entity possesses a unique DID that acts as its identifier within the decentralized network.



		- Establishing Logical Connections - The Mediator empowers entities, which could be individuals or organizations, to forge secure connections amongst themselves. Each entity possesses a unique DID that acts as its identifier within the decentralized network.
		- DID resolution - When an entity seeks to communicate with another, it resolves the recipient's DID to procure the information necessary to establish a connection. This resolution procedure entails retrieving the recipient's public key and correlated metadata from a decentralized identity infrastructure, which could be a blockchain or distributed ledger.

	- DID resolution - When an entity seeks to communicate with another, it resolves the recipient's DID to procure the information necessary to establish a connection. This resolution procedure entails retrieving the recipient's public key and correlated metadata from a decentralized identity infrastructure, which could be a blockchain or distributed ledger.
	- DID resolution: When an entity seeks to communicate with another, it resolves the recipient's DID to procure the information necessary to establish a connection. This resolution entails retrieving the recipient's public key and correlated metadata from a decentralized identity infrastructure, a blockchain, or a distributed ledger.

	- Message routing - The sender transmits an encrypted message to the Mediator, which serves as a routing agent. In this role, the Mediator receives messages from the sender, decrypts one layer, and forwards them to the appropriate recipient based on the recipient's DID.
	- Message routing: The sender transmits an encrypted message to the Mediator, a routing agent. In this role, the Mediator receives messages from the sender, decrypts one layer, and forwards them to the appropriate recipient based on the recipient's DID.

	- Mediation process- The Mediator verifies the authenticity and integrity of the incoming message by checking the digital signature attached to it. This signature ensures that the message was indeed sent by the claimed sender and that it hasn't been tampered with during transmission.
	- Mediation process: The Mediator verifies the authenticity and integrity of the incoming message by checking the digital signature attached to it. This signature ensures that the claimed sender sent the message and hasn't been tampered with during transmission.

	- Message decryption - After verifying the message's authenticity, the Mediator decrypted one layer of the message using the mediator's private key, which is securely held by the mediator. Once decrypted, the next message becomes readable (the final plaintext intended for the final user it's still encrypted).
	- Message decryption: After verifying the message's authenticity, the mediator decrypted one layer of the message using the mediator's private key, which the mediator securely holds. Once decrypted, the following message becomes readable (the final plaintext intended for the final user is still encrypted).

	- Optional processing - The Mediator may perform additional processing on the message based on predefined rules or business logic. This could include applying filters, applying policies, or invoking external services.
	- Optional processing: The Mediator may perform additional processing on the message based on predefined rules or business logic, including applying filters, applying policies, or invoking external services.

	- Message forwarding - If necessary, the Mediator can further forward the decrypted message to additional entities in the communication flow. This enables multi-party communication scenarios.
	- Message forwarding: The mediator can forward the decrypted message to additional entities in the communication flow, enabling multi-party communication scenarios.

	By acting as an intermediary, the DID Comm v2 Mediator helps facilitate secure and private communication between entities while leveraging the decentralized nature of DIDs and cryptographic techniques to ensure the authenticity, integrity, and confidentiality of the messages exchanged.
	By acting as an intermediary, the DID Comm v2 Mediator helps facilitate secure and private communication between entities while leveraging the decentralized nature of DIDs and cryptographic techniques to ensure the message's authenticity, integrity, and confidentiality.


		By acting as an intermediary, the DID Comm v2 Mediator helps facilitate secure and private communication between entities while leveraging the decentralized nature of DIDs and cryptographic techniques to ensure the authenticity, integrity, and confidentiality of the messages exchanged.

		The mediator is especially useful when the edge entities are not always online, like the mobile paradigm. Usually, we can assume that the mediator is always online.

	The mediator is especially useful when the edge entities are not always online, like the mobile paradigm. Usually, we can assume that the mediator is always online.
	The mediator is particularly convenient for edge entities that are only sometimes online, such as in the mobile paradigm. It's a practical solution, as we can assume that the mediator is always online.

	external components, mainly cloud and edge agents.
	external components, mainly Cloud and Edge Agents.


		## Container Diagram

		The container diagram depicts the internal containers/runnables and their relationships within the Identus Mediator.

	scanned by an edge agent mobile application to initiate a mediation request with the mediator.
	scannable by an Edge Agent mobile application to initiate a mediation request with the mediator.


		- User Accounts: for storing user account information of mediated agents.

		- Message Items: for storing messages sent by edge and cloud agents.

Update de.flapdoodle.embed.mongo to 4.13.0 in main #297

Update de.flapdoodle.embed.mongo to 4.13.0 in main #297

Conversation

atala-dev commented Apr 30, 2024

About this PR

Usage

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

petevielhaber left a comment

Choose a reason for hiding this comment


		The Mediator Database stores data related to the Identus Mediator. It contains the following collection:

		- User Accounts: for storing user account information of mediated agents.

	- Each HTTP call needs to generate a call ID (preferably on the proxy). The ID must be within the scope of the ZIO application. So, every log will mention this ID. This ID must return to the user as an HTTP header.
	- Each HTTP call must generate a call ID (preferably on the proxy). The ID must be within the scope of the ZIO application. So, every log will mention this ID. This ID must return to the user as an HTTP header.

	A user can receive Level 3 support during the logging retention policies. The user needs to provide the value in the header `X-Request-Id` to get this support.
	A user can receive Level 3 support during the logging retention policies. To get this support, the user needs to provide the value in the header `X-Request-Id`.


		## Code

		To have a concise code, we have created a middleware that modifies the annotations in the scope before each execution of that endpoint and includes the trace ID of the request.

	To have a concise code, we have created a middleware that modifies the annotations in the scope before each execution of that endpoint and includes the trace ID of the request.
	To have a concise codebase, we have created a middleware that modifies the annotations in the scope before each execution of that endpoint and includes the trace ID of the request.

	***if you have mac os comment the the line
	***if you have macOS comment the the line