Project:Tool Access Control/ACNet: Difference between revisions
From London Hackspace Wiki
No edit summary |
No edit summary |
||
Line 4: | Line 4: | ||
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. | * [[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. | ||
* [[# | * [[#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. | ||
Revision as of 17:13, 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 )