didcomm 2.3.1

didcomm: ^2.3.1 copied to clipboard

• FIX: update ServiceType handling for SSI v3 compatibility (#80).

  • fix: update ServiceType handling for SSI v3 compatibility

  ---

• FEAT: deleteOn flags consolidated to deleteOnReceive (#79).

• FEAT: reverting deleteOnMediator to allow keeping msg during live mode (#78).

  • feat: reverting deleteOnMediator to allow ws flexibility

  • feat: example updated, more on delete options added

  • fix: formatting

  • fix: linting

  • fix: doc

  • fix: doc/naming

• FEAT: reconnect callbacks.

• FIX: close connections at the end of each test.
• FIX: allow sequential connections.

• FIX: code generation.
• FIX: use compatible syncronized package.
• FIX: add lock to prevent steam closing when messages are still processing.
• FIX: use acl for tests and examples.

• FIX: changelog after breaking changes.

Note: This release has breaking changes.

1. MediatorClient Refactoring

• Introduced a new MediatorClient.init factory for easier and safer instantiation, handling key agreement and signer resolution internally.
• All authentication and access token logic is now handled via a new AuthorizationProvider abstraction.
• Methods like sendMessage, fetchMessages, listInboxMessageIds, etc., no longer require explicit access tokens; tokens are managed automatically.
• WebSocket connection management is now handled via a new Connection class and a singleton ConnectionPool for concurrent connections.

2. AuthorizationProvider Abstraction

• Added AuthorizationProvider and AffinidiAuthorizationProvider for pluggable, extensible token management.
• Token refresh and challenge-response authentication are now encapsulated and reusable.
• All mediator flows (REST and WebSocket) now support authenticated mediators out of the box.

3. Connection & ConnectionPool

• New Connection class manages a single WebSocket connection and message stream.
• New ConnectionPool singleton manages multiple concurrent connections, subscriptions, and lifecycle.
• Important: All mediator clients must be registered with the pool before calling ConnectionPool.startConnections(). Clients added after startConnections() will not be managed.

4. API and Example Updates

• All examples and tests updated to use the new MediatorClient.init and AffinidiAuthorizationProvider.init flows.
• Removed legacy extension-based authentication methods.
• Simplified message sending, receiving, and inbox management APIs.

Migration Notes

• Replace direct MediatorClient constructors with MediatorClient.init.
• Use AffinidiAuthorizationProvider for Affinidi mediator authentication.
• Use ConnectionPool for managing multiple concurrent WebSocket connections.
• Remove any manual access token handling in your code.

• FIX: fetch by date and time.

• FEAT: pass close code and reason to channel onDone method.

• FIX: qeuery message.

• FIX: running tests on windows.

• FIX: release version.

• FIX: prevent from header to be non null for anoncrypt.
• FEAT: add packIntoAnoncryptAndAuthcryptMessages. check skid and apu to be null for anoncrypt.

• FEAT: delete messages on websockets.

• FEAT: add oob on mediator.
• FEAT: fetch and delete messages.

• FEAT: add ping interval option to listenForIncomingMessages method (#59).

  • feat: add ping interval option to listenForIncomingMessages method

  • refactor: move ping interval to web socket options

  • refactor: use web socket options in toWebSocketChannel

  • refactor: remove nullable from pingIntervalInSeconds

  • docs: parameter description webSocketOptions

• FEAT: organize exports.

• FEAT: organzie package exports.

• FIX: update to latest dart ssi.

• FIX: analyzer issues.

• FIX: formatted.
• FIX: doc added.
• FIX: reverted #2.
• FIX: reverted #1.
• FIX: moved acl mgmt to extensions.
• FIX: logs removed.
• FEAT: test/examples constants updated.
• FEAT: config file renamed.
• FEAT: config file renamed.
• FEAT: test evns vars updated.
• FEAT: TEST_MEDIATOR_WITH_ACL_DID added.
• FEAT: acl example added.
• FEAT: forward message abstracted in mediator client.

• FIX: package publish.

• FIX: a256gcp should be used only for ecdh-es.
• FEAT: add disclose message.
• FEAT: add query message.

• FIX: use a256gcm only for anoncrypt.

• FEAT: support p384 and p521.

• FEAT: add problem report message.

• FEAT: initial release