Skip to content

Enhancing the Eventuate Java Client According GDPR #9

@dartartem

Description

@dartartem

The save() and update() operations need an optional encryption key parameter that they use to encrypt events.

The parameter is an object with the following fields: (encryptionKeyId, …)

The client is instantiated with an optional Encryption object that implements encrypt(encryptionKeyId, eventdata) and decrypt(encryptedEventData) operations.

The encrypted event is prefixed with the encryptionKeyId. This enables the find() and subscribe() operations to decrypt the events.

The Java client should probably use https://docs.spring.io/spring-security/site/docs/5.0.4.RELEASE/reference/htmlsingle/#crypto

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions