[RFC] Labelled Data, Indexing and Token Authorisation

ClientHandler code validates requests before sending them to nodes to perform those requests. (Ie, we check if the app has permission to do XYZ.
DataHandler has the data (teh client handler cannot see this), and checks final permission on the data itself for a given request, and returns it.

Authenticator is the user-space application which controls the account, provides application’s with credentials to work on the network (currently keys which are checked at CH, the proposal changes that to be bearer-token based)

5 Likes

I’ve updated the OP with the following:

Changelog

  • Added examples of label flow for token issuing / authorization of labels on data.
  • Add a second SharedToken idea, so not tied to data controlled by issuer per-se.
  • Improved Summary
  • Added some thoughts on async token re-issue

I’ll likely separate out a Token RFC from this, as that’s where we’re starting to focus. And that should make it clearer to understand token logic in general

2 Likes