416-MemoryLane / issue-tracking

0 stars 0 forks source link

[SPIKE] Authentication and Authorization via a central server #7

Closed eysk-io closed 1 year ago

eysk-io commented 1 year ago

Both authentication and authorization are required for access to albums. This will be managed by Galactus, a centralised deployed service and server in a client-server architecture. This centralisation is required for our application, to ensure that the peer-to-peer network is enforced around album access authorization.

Galactus will keep a record of all albums and the users which have access to these albums. At the same time, for each user it will contain a list of the albums the user has access to. When we have a user that has been granted access to the album, Galactus will perform an atomic operation to a central database that will do the following two things:

A significant challenge for this module (and Wingman) will be accounting for the fact that the IP address of the connection during a session for a node will be likely different every time the node joins a network. As well, if the node is not gracefully shutdown with a process to indicate a stale IP address in the database, another node with access to the same album would try to connect to the stale IP address.

scott-m-king commented 1 year ago

SPIKE doc: https://docs.google.com/document/d/1Uxg_q5zpd2nTs63gjDt3Xs7Tj9jFVOY2QxnlpV-8hbA/edit?usp=sharing