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

Revision as of 02:03, 17 May 2015

Summary

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

ACNode - 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
Membership DB - Secured storage of membership data.

System diagram

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

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

       local_db [label="local db",shape=box];
       httpserver [label="HTTP server",shape=box];
       httpserver -> local_db;
       local_db -> 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 working implementation Project:Tool_Access_Control/ACNode-cl

AC Server

Current: PHP CI implementation developed by mentar and Oskar, more info ACServer (currently active)

Legacy: Python Flask implementation started by ms7821 can be located here further improved by asoko (shelved)

Membership DB

Running on Turing VM slice (hosted outside the space as it has personal data). Accessed in JSON format.

@@ Line 3: / Line 3: @@
 This page aims to scope out the different projects that work together as part of the Access Control Network.
 The main components are:
-* ACNode - The clients that sit on the tool that is being controlled and manage physical access by reading the rfid card.
+* [[#AC_Node|ACNode]] - 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
+* [[#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.
+* [[#Membership_DB|Membership DB]] - Secured storage of membership data.
 == System diagram ==
@@ Line 16: / Line 16: @@
     subgraph cluster_0 {
 	node [shape=box,style=filled,color=lightgrey];
 	label = "ACServer";
-         sqlite [label="SQLite",shape=box];
+         local_db [label="local db",shape=box];
          httpserver [label="HTTP server",shape=box];
-         httpserver -> sqlite;
+         httpserver -> local_db;
-         sqlite -> httpserver;
+         local_db -> httpserver;
     }
@@ Line 29: / Line 27: @@
     acnode3 [label="ACNode",shape=box];
-    turing [label="Turing VM",shape=box];
+    membershipdb [label="Membership DB",shape=box];
@@ Line 40: / Line 38: @@
     httpserver -> acnode3;
-    turing-> httpserver;
+    membershipdb-> httpserver;
 }
 </graphviz>
+=== AC Node ===
+Currently working implementation [[Project:Tool_Access_Control/ACNode-cl]]
+=== AC Server ===
+Current: PHP CI implementation developed by [[User:mentar|mentar]] and Oskar, more info [[Project:Tool_Access_Control/ACServer|ACServer]] (currently active)
+Legacy: Python Flask implementation started by [[User:ms7821|ms7821]] can be located [https://github.com/londonhackspace/ACNode here] further improved by [[User:asoko|asoko]] (shelved)
+=== Membership DB ===
+Running on Turing VM slice (hosted outside the space as it has personal data). Accessed in JSON format.