Project:Tool Access Control/ACNet: Difference between revisions
From London Hackspace Wiki
No edit summary |
|||
Line 16: | Line 16: | ||
subgraph cluster_0 { | subgraph cluster_0 { | ||
node [shape=box,style=filled,color=lightgrey]; | node [shape=box,style=filled,color=lightgrey]; | ||
label = "ACServer"; | label = "ACServer"; | ||
sqlite [label="SQLite",shape=box]; | sqlite [label="SQLite",shape=box]; | ||
Line 29: | Line 27: | ||
acnode3 [label="ACNode",shape=box]; | acnode3 [label="ACNode",shape=box]; | ||
membershipdb [label="Membership DB",shape=box]; | |||
Line 40: | Line 38: | ||
httpserver -> acnode3; | httpserver -> acnode3; | ||
membershipdb-> httpserver; | |||
} | } | ||
</graphviz> | </graphviz> | ||
== AC Node == | |||
== AC Server == | |||
== Membership DB == | |||
Running on Turing VM slice (out ) |
Revision as of 17:02, 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:
- 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
- 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
AC Server
Membership DB
Running on Turing VM slice (out )