InnerWeb
Skip to main content

Registration desk: access tokens and rollout order

Two secrets protect the registration desk, and both must be set in the right order, otherwise every scan will be rejected. The IT team should first deploy the device image, then the token on the intermediary server, then the access token in the address, and finish with boundary tests.

42
hexadecimal characters of the access token (168 bits)
Source: card
7
steps in the desk rollout order
Source: card
2
independent secrets protecting the desk
Source: card

Who this is for and why this order matters

These notes are for the IT department and integrators who launch the registration desk in a production plant. The desk is an unattended screen, so its security relies on secrets, not on an operator's login. A mistake in the order of setting them up means the screen works, but every scan returns an error or, worse, opens without protection.

The system is designed so that a missing token closes the desk instead of opening it. This is a safe default, but it requires that the rollout follows the set order and that the IT team knows what to expect after each step.

Two secrets, two roles

The desk is protected by two different secrets. The first is the desk token, added by the intermediary server. It never reaches the browser, so even a person with access to the screen cannot read it from developer tools. The second is the access token contained in the desk address. The administrator rotates it with one confirmed click in the system settings.

The access token is 42 hexadecimal characters, which is 168 bits, and it is not copied into browser storage. An empty or removed token closes the desk. This means that switching the desk off in case of an incident is done by removing or rotating the token, without going to the computer at the gate.

Security parameters of the desk

Security parameters of the deskChart: 168 bits of the access token, 42 characters, 2 secrets.050100150200valueAccess token bitsAccess token bits: 168 value168Access token charactersAccess token characters: 42 value42Number of secretsNumber of secrets: 2 value2
Source: Registration desk documentation

Rollout order step by step

The order below reduces the number of rejected scans during start-up.

  • Step 1: prepare the device image: a computer with a browser, a USB HID scanner, no keyboard, the screen in full-screen mode.
  • Step 2: set the desk token on the intermediary server and check that it does not appear in the code sent to the browser.
  • Step 3: generate the access token in the system settings and put it into the desk address.
  • Step 4: open the address on the desk and scan a test badge with a valid induction.
  • Step 5: scan a badge without a valid induction and check that the induction starts.
  • Step 6: verify that after removing the access token the desk closes, and after restoring it the desk opens.
  • Step 7: set the re-scan window in seconds and check it with a double scan.

Implementation traps

The first trap is pasting the access token into a messenger or notes, where it can leak. We recommend passing the address only through a channel agreed with the security department, and rotating the token after every change of people with access.

The second trap concerns infrastructure: the intermediary server must be reachable from the desk's network. A server error or timeout shows the operator a readable message, so that an unreachable backend does not look like an unrecognised badge. It is worth distinguishing these two cases during tests.

The third trap is restarting the server during peak traffic. Plan maintenance outside the peak of entries, and after every change run a test scan of a valid badge and a badge without a valid induction, to confirm that the desk works as it did before the change. It is also worth having a short written emergency procedure: who switches the desk off by rotating the token, and who restarts it.

Maintenance after go-live

After launch, set a schedule for rotating the access token and name the person responsible for passing the new address to the desk. Add a task to the review plan: check that the desk closes when the token is empty. A plant with several entrances should have a separate access token for each desk if the software allows it, and at least a separate address.

Video

Frequently asked questions

What happens when the access token is empty?

The desk closes instead of opening. An empty or removed token is treated as no access.

Is the desk token visible in the browser?

No. The desk token is added by the intermediary server and does not reach the browser.

How do I rotate the access token?

The administrator does it with one confirmed click in the system settings, then puts the new address on the desk.

When should test scans be run?

After the first rollout, after every token rotation and after every server restart. A scan with a valid induction and a scan without one confirm that both paths work.

Let us plan the desk rollout with your IT team

Book a conversation with our rollout team. We will go through the order of steps and the boundary tests for your network.

Let's talk