The matadata server will act as a point of synchronization for managing access to cryptpad's sessions.

Data stored:

• session key (encrypted by workspace key)
• workspace id
• file id

Api

• create_or_join_session(encrypted_session_key, workspace_id, file_id) -> encrypted_session_key:
  • if there is no active session for that file, the entry is created and the provided key is returned
  • if there is already a session the existing key is returned, the provided key can be discarded
• TODO: session expired for the moment we can re-use the session key