Implement BRSKI Policy App using Claim Cascade System

[A9-dev]

Some explanation of how the previous iteration of the BRSKI Policy app (the registrar app) works is here.

Currently for the trustnetz BRSKI demonstrator we have:

• A server for signing and verifying VCs: github
• A server which receives VCs, verifies them and translates them into sqlite statements: github
• A web application which provides a UI to see the state of the device/manufacturer/device type entities and allows pressing UI buttons to generate, sign and submit VCs to the server set up to receive VCs on the registrar: github
• A rust library with functions to check the device connected to the router should be allowed to be connected to the router, this also contains a suite of tests which we should replicate for the claim cascade implementation: github

I've got this script which adds some dummy demo data to the sqlite database

We now want to replace these with:

• A server API which contains the functions of the authentication server (email authentication) and allows claims to be submitted to claim cascade, as well as providing a method to submit prolog queries to run against the prolog environment
• A web app which presents the same functionality as the previous web app:
  • view the current state of the device, it's manufacturer, and it's device type
  • trust/distrust manufacturer (add trust claim, retract trust claim - schema)
  • trust/distrust device (add allow_to_connect claim, retract allow_to_connect claim - schema)
  • set device type of device instance (add is_of_device_type claim schema)
  • set device type vulnerable (this is implemented as binding the device type to vulnerable MUD statement - schema)
  • set device type not vulnerable (this is implemented as binding the device type to not vulnerable MUD statement - schema)
• A rust script with functions to run prolog queries to check the device connected to the router should be allowed to be connected to the router, see github

The schemas for claims for this system are here, we'll need to populate claim cascade with some claims to bootstrap the device information, device types, users, manufactuters, MUD files, etc...