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 6: / Line 6: @@
 * [[#AC_Server|ACServer]] - The server stores the authentication information and pulls membership information from Turing over JSON and stores is at a SQLite DB
 * [[#Membership_DB|Membership DB]] - Secured storage of membership data.
-== TODO ==
-* Add a secondary acnode and test multiple acnode functionality (Sol)
-* Figure out a strategy of syncing the membership database to the local access database, as currently manual (mentar)
-** Optimise the sync so it takes less time and add it to the cron job to every few minutes
-* Move the acserver to a separate VM running on the server downstairs (tgreer + mentar)
-* Code a basic web ui for adding tools/maintainers/nodes (mentar)
 == System diagram ==
@@ Line 50: / Line 43: @@
 === AC Node ===
-Currently proposed  (and built) by Solexious [[Project:Tool_Access_Control/Solexious_Proposal|Link]]
+Currently working implementation [[Project:Tool_Access_Control/ACNode-cl]]
 === AC Server ===
-versions
-Python Flask implementation started by [[User:ms7821|ms7821]] can be located [https://github.com/londonhackspace/ACNode here] further improved by [[User:asoko|asoko]]
-PHP Code Igniter implementation developed by [[User:mentar|mentar]] and Oskar located [https://github.com/mentarus/ACServer here]
-Usage: curl http://[server]:[port]/[node_id]/card/[card_id]
+Current: PHP CI implementation developed by [[User:mentar|mentar]] and Oskar, more info [[Project:Tool_Access_Control/ACServer|ACServer]] (currently active)
-For testing it's installed on babbage port 1234
+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.