Connection direction and ports
Do we need to open an inbound port on the plant network? No. For every tap, the access control server sends an HTTPS POST message to InnerWeb, so the connection is outbound from the plant network. For the IT and OT team this means a firewall rule for outbound traffic to one address on port 443, with no need to expose the access control server to the internet.
Does the card migration change this setup? No, because the media and card number change, not the event channel. If readers and controllers are replaced together with the cards, it is enough to check that the access control server, after its update, can still send HTTPS POST messages.
Authentication and the JWT token
How does the access control system authenticate to InnerWeb? The integration uses a technical account and a JWT token with a limited validity period, which the integration renews automatically. On the access control vendor side, token renewal must therefore work, or the system must log in before each batch of messages.
Agree with the access control vendor how token expiry is handled overnight and at weekends. A good acceptance test is to pause the renewal and check that messages still arrive after a new login, with no lost events.
Tap integration specification requirements
Message content and card number
What should a message contain? The integration specification requires the reader timestamp, the reader ID, the person, the card number in the form facility_code-number, the direction (entry or exit) and the event ID. After migration the card numbers have new values, so before the wave goes live the team must deliver a card export (facility code and number) linked to the personnel number.
How are entries and exits handled? The access control system sends events in real time together with the direction, and InnerWeb receives them through an authenticated webhook. The rules for pairing entries and exits and for rejecting duplicates are set in the specification together with the access control vendor. If readers in the client's access control system do not distinguish direction, this is a technical fact on the access control side that must be covered in the specification. After replacing readers, update the reader dictionary, where separate readers are described as entry or exit.
Controller timestamp and idempotency
Why does the reader timestamp matter, and not the receipt time? The access control system sends events in real time, carrying the event time from the reader. As a result, an offline queue or a resend after a network outage does not shift taps: a delayed tap lands in its own hour, and the event ID allows duplicates to be rejected under the rules agreed in the specification.
In practice this gives the access control vendor one requirement: every event must have a stable ID that does not change on resend. After the controllers are migrated, it is worth checking this, because new firmware may generate IDs differently.
What stays in InnerWeb and what stays in the access control system
All processing, meaning recognising entries and exits, pairing them into work days, schedules, exceptions and reports, happens on the InnerWeb side, and the access control system logic stays unchanged. The IT and OT team therefore does not need to move the time-accounting rules to the access control system, or the other way round.
A tap from an unknown card goes to the queue of cards waiting for assignment, instead of creating an account from an unknown tap. As a result, the first wave of new cards that is not yet linked to people does not create accounts or disrupt the records.
Video
Frequently asked questions
Does the integration need to be redeployed after the card replacement?
No. The HTTPS POST channel and the authentication stay in place. What changes is the card number and the card export linked to the personnel number, which is loaded into InnerWeb by CSV import.
What if the access control vendor cannot send HTTPS POST?
This is the first question to settle before the integration: whether the access control server supports sending HTTPS POST. Together with it, the list of readers and the card export format are agreed.
Could events from an offline queue upset the work days?
No, as long as each message carries the reader timestamp and the event ID. The rules for rejecting duplicates are set in the specification with the access control vendor.
Does InnerWeb see the card number in plain form?
The card number has the form facility_code-number and is used to link the card to a person. The card number is not shown in the account search of the training module.
Sources
Let us check the tap integration before the migration
We will go through the list of agreements with your IT and OT team and the access control vendor: sending, token, readers and card export. As a result, the work days will have no gaps after the card replacement.
Let's talk