Difference between revisions of "Project:Tool Access Control/ACNet"

From London Hackspace Wiki
Jump to: navigation, search
Line 3: Line 3:
 
This page aims to scope out the different projects that work together as part of the Access Control Network.
 
This page aims to scope out the different projects that work together as part of the Access Control Network.
 
The main components are:
 
The main components are:
* [[Project:Tool_Access_Control/Solexious_Proposal|ACNode]] - The clients that sit on the tool that is being controlled and manage physical access by reading the rfid card.
+
* - The clients that sit on the tool that is being controlled and manage physical access by reading the rfid card.
 
* [[#AC_Server|ACServer]] - The server stores the authentication information and pulls membership information from Turing over JSON and stores is at a SQLite DB
 
* [[#AC_Server|ACServer]] - The server stores the authentication information and pulls membership information from Turing over JSON and stores is at a SQLite DB
 
* Turing - Secured storage of membership data.
 
* Turing - Secured storage of membership data.
Line 43: Line 43:
  
 
== AC Node ==
 
== AC Node ==
 +
Currently proposed  (and built) by Solexious [[Project:Tool_Access_Control/Solexious_Proposal|Link]]
 
== AC Server ==
 
== AC Server ==
 
== Membership DB ==
 
== Membership DB ==
 
Running on Turing VM slice (out )
 
Running on Turing VM slice (out )

Revision as of 17:16, 16 February 2013

Summary

This page aims to scope out the different projects that work together as part of the Access Control Network. The main components are:

  • - The clients that sit on the tool that is being controlled and manage physical access by reading the rfid card.
  • ACServer - The server stores the authentication information and pulls membership information from Turing over JSON and stores is at a SQLite DB
  • Turing - Secured storage of membership data.

System diagram

<graphviz border='frame' format='png' >

digraph rfboard{
  rankdir=TD;
  size="10,5!";
  
  subgraph cluster_0 {

node [shape=box,style=filled,color=lightgrey]; label = "ACServer";

       sqlite [label="SQLite",shape=box];
       httpserver [label="HTTP server",shape=box];
       httpserver -> sqlite;
       sqlite -> httpserver; 
  }
  acnode1 [label="ACNode",shape=box];
  acnode2 [label="ACNode",shape=box];
  acnode3 [label="ACNode",shape=box];
 
  membershipdb [label="Membership DB",shape=box];


  acnode1 -> httpserver;
  acnode2 -> httpserver;
  acnode3 -> httpserver;
  httpserver -> acnode1;
  httpserver -> acnode2;
  httpserver -> acnode3;
  membershipdb-> httpserver;

} </graphviz>

AC Node

Currently proposed (and built) by Solexious Link

AC Server

Membership DB

Running on Turing VM slice (out )