This pr is to add the middleware that verifies the communication between locker and the tenant is JWS signed and JWE encrypte.

-> I have tested it through postman

-> test case

curl --location 'http://localhost:8080/data/add' \
--header 'Content-Type: application/json' \
--header 'Cookie: JSESSIONID.130f0e8f=node01ix1y16yw8z3v1m3nwkr4qbiwb6.node0' \
--data 'eyJlbmMiOiJBMjU2R0NNIiwidHlwIjoiSldUIiwiYWxnIjoiUlNBLU9BRVAtMjU2In0.tIsj8UjaA5xAY_yytYrc94PZS4Ma3RWn5kZAG5lWZXbkwwmjvCoG-26m9DWnd5ZBMl97OiZNTi7-LVBCEyczRkqZ25vYhqvRhHr2WDuksGEIl1i9rui93tbMmf4UWeeVD3S_6lw5GQLc7jXyyWVzKS1J-hxZ2ZXBGiOlSoo0Ua8Njhh0DkzUq6tO5ttBbYqQf7vAhI-AaRu4W7dlC8LKNhZAmPNKn9diQ5Aae75M7606gvdVFlwXTTdWAERdA-7NyMMhJxpgt2bU7C4DZKGdEWEDKe89SqEzIC0dCJ2gLgOnqFHOuwKaCUVV6T10kuUdATqCH_r9CBuXdXgJadpGKQ.jjy9UvpqGuQ52pE1.xdIJWCVoSREhR1nA2bOnJXT3Pnm4P50Oe-WNOTwWDos0cS1b-45TdtFlnB9OZi-eNX7LixMh3cIV6bP2UJ3K5BDRUamcT55J95M5VQ5MBX9ywu47mE-e4VYRRB52VzRebND6tAGP4z8jWUIVYRr9375QFFJY4lt7jSn-7FWNeKVWyh9x8_vGMAjFIUIgbuvXO-OvPB-pNyRXESzBLkb_oODhxMRzJhr6uyzMOPG_sCGIvorPAWiFIsPMNgLacKD8J1McusaioGjP1a6IS3GW8QUiONgZC6JRUTypJTixehOpVZ5JFFgT-JDc_FEqSCLkDoiub2cD0rS3WeXYbpolKn4YbXV34NXSB3iSy04iaTi54IRXwzW7x7iEcF2BZsuI7GegbPktMIkTx5cZ7O6hASE9nQ2Finy0axzeeDVcySqe6M4Ox3s-u8Qo0XxZ_vXeWBotQ8EaN5rddGn_3q6PoBr6_71rO9dUzHLTWsxatAib2HU12lZNqJj2sRT0yd38qbr_M38kl5bV69X8G_zuxvB70PCB9t0Q925-ril8glG-IbFruo8DivrJqLVp_WAatlQV7SvHYy5E0tLofreU5g3SsyvKX5qQ4s_vev7i2cSEUKaBHjM42lnfMA-ZJJaoWXfmFKTKgCu00lo_kHaQX3i4BZhM4Et1-hVgKYgARS-CO5muWTkYGhHUvQ.NrNzu_vsH8s3DFo-4NPfGw'

This PR adds 2 workflows

• Release new version (Triggered manually): This workflow will create a new tag, generate changelog and release notes
• Build and push docker image (Triggered manually, on pushing tags): This workflow will build a docker image and push it to docker hub

Description

Introducing a new framework for handling error, this framework internally converts the error while maintaining the log trail, this reduces the need to manually perform change context while providing more details around how the error needs to be propograted

Description

Adding CLI tool to generate keys and any future external requirement of the locker.

Currently supports

• Generating master key
• Generating key custodian keys

Description

Implement the metrics framework for the locker including the appropriate metrics required to track the health, liveliness and the usage of the locker

Description

The encryption algorithm used for any database related encryption is GcmAes256 and the hashing algorithm used is sha512. That being said, in future if we decided to change the hashing algorithm and or the encryption algorithm it would be difficult to maintain backwards compatibility. This can be mitigated by having an identifier of the encryption/hashing algorithm used along side the encrypted/hashed data.

Description

Due to error-stack its easy to simply change the context and propagate errors without much effort, but this definitely reduces the quality of the error propagation as there is no strict standard that the errors need to adhere to. This issue addresses this discussing upon a more standardized way of handling error removing change_context from the code based promoting a more declarative way of error handling instead of the current imperative way.

Possible Approaches

• Wrap the current error into a custom defined struct, create a specific context for all the layers/APIs and then define TryFrom implementation for them, internally handling the change contexts

Description

Add support for exporting program level metrics outside the application. The preferred framework for adding metrics includes opentelemetry or exporting prometheus metrics.

Sub Issues

• [ ] #31
• [ ] #32

Description

This will require use to create a tenant table which will store the public key that will be used to communicate with the locker.

Requirements

• Create database schema with the appropriate fields
• Create Interface to provide API to communicate with the database