Installation Key Management

[jazzz]

Problem

Currently Installation keys are generated when a Context is initialized. This is sufficient for testing, however does not allow a single identity to be used across multiple application sessions.

Desired Outcome

• Developers can chose to generate a new InstallationKey or reuse an existing key
• Keys are stored securely

Tasks

• Persist InstallationKeys
• Update API to allow developers to select existing keys.
• Determine approach to encryption at rest.
• Update Nim-Bindings/FFi

[jazzz]

@osmaczko do you have any preferences/knowledge here from previous experience?

I'd like to contain the keys to LibChat if possible so minimal secret material is being sent over FFI.

[jazzz]

A full implemented solution is not needed at this time, however there is currently a mismatch between Libchat and Nim-chat-poc, they both think they are owners of the InstallationKeys.

That needs to be reconciled (P1).

Having a loose plan of what the API looks like across the project boundaries would be helpful even if calls are stubs for now.