Who is responsible for what
InnerWeb is a software manufacturer and does not produce or replace access control readers. It integrates with the client's existing access control system, and the integration specification is intended for the access control supplier. The plant and the access control supplier therefore prepare the sending of events, and InnerWeb prepares their receipt and their connection with qualifications, permits, attendance and time recording.
This division means that the integration project involves no exchange of readers and no change of card technology. What changes is that the access control system, besides handling passage in its own way, sends a copy of the event to the indicated address.
Card scan event: fields to agree
A card scan event includes, among other things, the time, the place, the first name, the last name, the company, the number of the active card, the telephone number, the e-mail address and the person's language. Before go-live, the plant and the access control supplier agree which of these fields the access control system can send and which the plant wants to pass on in line with the data minimization principle.
Sensitive fields, such as telephone and e-mail, are passed on only when they are needed for a task, for example a notification in the person's language. In other cases, the time, the place and the identifier of the person are enough.
Consistency of identifiers
The most common cause of empty connections is a mismatch of identifiers: the card number in the event must match the number of the active card in the register. That is why the card register and the accounts should be tidied up before go-live, without duplicate accounts.
Division of responsibility in the access control integration (tasks per party)
Webhook and token: channel security
InnerWeb receives the card scan event through a webhook authenticated with a token that has a limited validity of 12 hours. This means the access control system must be able to refresh the token, rather than use a permanent key stored once. The access control supplier confirms that its system supports such a mechanism, or names an intermediary component that will handle it.
On the plant's side there is also the network channel: firewall rules, an encrypted connection and monitoring of delivery errors. The IT team decides where events that have not been delivered go, and who analyses them.
Testing before production go-live
The test consists of three passes: a scan of an active card, a scan of a blocked card and a scan of a visitor card. For each of them we check whether the event arrived, whether the fields match the specification and whether it went to the right account. The result of the test is recorded in a protocol with the date and the people who carried it out.
A separate test concerns failure: what happens when InnerWeb is temporarily unavailable. The access control system must not block passage through the gate because an event failed to send, and undelivered events must be possible to resend.
What the plant gains after go-live
After go-live the card scan events are linked with qualifications, permits, attendance and time recording. InnerWeb works as an independent system supplementing the client's access control, HR and ERP, so at the gate you see not only that the card is valid, but also whether the person has the required training.
For the IT department the gain is that the integration does not touch the cryptographic layer of the cards or the keys. The keys and SAM modules stay in the plant's access control system, and InnerWeb receives only the events.
Checklist
Video
Frequently asked questions
Does the integration require replacing readers?
No. InnerWeb integrates with the client's existing access control system and does not replace readers. Only the sending of a copy of the scan event from the access control system changes.
Why does the token have a limited validity?
It limits the consequences of a leak: a stolen token loses its validity after 12 hours. The access control system must therefore be able to refresh it.
Do card keys reach InnerWeb?
No. The keys and SAM modules stay in the access control system. InnerWeb receives only the scan events.
Who writes the specification for the access control supplier?
InnerWeb prepares the integration specification for the access control supplier, and the plant agrees with the supplier the scope of fields and the schedule.
Let's prepare the specification for your access control supplier
We will describe the event fields, the token and the test scenarios, and your IT team and the access control supplier will receive a ready list of tasks.
Let's talk