You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Aug 27, 2024. It is now read-only.
Currently MeMaS does not check if the claimed user is authorized to do X. Even though we trust their claim of who the user is, we still need to verify if they have the rights/permissions to perform the action they request.
This at its early stages involve:
CP APIs can only modify nodes below the user, such as user1 can have control over user1.A.B:C, but not over user2.X
DP API memorize can only write to corpuses directly below the user (? To be debated if this is necessary)
DP API recall can read only from corpuses that belong to the user, or belong to direct ancestors. Such as companyA.team1.user1 can read from the corpus companyA:C, but not companyA.team2:X.
Currently MeMaS does not check if the claimed user is authorized to do X. Even though we trust their claim of who the user is, we still need to verify if they have the rights/permissions to perform the action they request.
This at its early stages involve:
user1
can have control overuser1.A.B:C
, but not overuser2.X
memorize
can only write to corpuses directly below the user (? To be debated if this is necessary)recall
can read only from corpuses that belong to the user, or belong to direct ancestors. Such ascompanyA.team1.user1
can read from the corpuscompanyA:C
, but notcompanyA.team2:X
.TRACKS: #19, #25
The text was updated successfully, but these errors were encountered: