InnerWeb
Skip to main content

Instance address in the QR code and the visitor's phone

The QR code holds the address of the system instance, so a visitor's phone must be able to open it from outside the plant network, often over an ordinary mobile connection. Below are notes for IT: what to check in DNS, the firewall and the certificate before the first invitations go out to visitors.

1
e-mail with the code per person for a given token
Source: karta

Where the network requirement comes from

The QR code on the badge encodes the address of the system instance with a token in the form of a /q/ path and a token. The same address appears in the invitation e-mail and on the printed security label. The visitor usually opens it on the way to the plant, in the waiting area or in the car park, that is outside the internal network. If the address resolves only through the plant's internal DNS, the phone cannot reach the server, and the visitor sees a browser error instead of the correct flow.

This is a question for IT that should be asked before the first badge is issued, not after the first complaint. The requirement concerns only the public address with the token. The security and administration panels may remain inside the network, if the organisation decides so.

List of network checks

The points below cover the layers from the domain name to the certificate. Each should be checked from a phone on a mobile network, not from a computer in the office.

Pay particular attention to the fact that a code with an internal address, once printed, stays in circulation. Changing the instance address after badges have been issued means printing them again, so the decision about the address should be closed before the start.

  • the instance domain name resolves in public DNS,
  • the HTTPS port is reachable from the internet for the address with the token,
  • the certificate is issued by a trusted authority and covers the name,
  • the firewall does not block traffic from mobile operator ranges,
  • the redirect after a scan works on phones with different browsers.

Layers checked by IT

Layers checked by ITChart: four layers of checks from DNS to the visitor's phone test.01234layer numberPublic DNSPublic DNS: 1 layer number1Firewall and HTTPS portFirewall and HTTPS port: 2 layer number2CertificateCertificate: 3 layer number3Test from a phoneTest from a phone: 4 layer number4
Source: InnerWeb study: order of network checks

The e-mail with the code and the availability of the address

Each person receives the e-mail with the QR code at most once, thanks to an atomic flag in the database, and a new badge after a code exchange triggers a new e-mail with a new code. The e-mail goes out only after the trainings required at the gate have been passed. If the address in the e-mail does not open from the visitor's phone, help desk tickets will start already after the first wave of invitations.

A person without an e-mail address and without a phone receives a printout from security. For such a person the internet address does not matter, because the code is scanned by the plant's equipment. This distinction helps IT set priorities: reachability from the internet is critical for the e-mail path, not for the printout.

Acceptance test from the visitor's phone

Run the test on two phones: one with Android and one with iOS, on an operator network, without a connection to the plant network and without a VPN. Scan the code on a test label and check whether the browser opens the address without a certificate warning. Then scan an invented string of the correct shape and compare the flow: it should be the same, because the public address does not check the token.

Record the result in the acceptance protocol. It is worth adding a screenshot from the phone and the time of the test. After later changes to the firewall or DNS, the same test is repeated as part of the change list.

Changes after go-live

The most common cause of failures after months of operation is not the system itself but a change in the infrastructure: a renewed certificate without the intermediate chain, a changed firewall rule, or a moved DNS record. It is worth adding the address from the QR code to the list of services covered by availability monitoring, and setting an alert from a phone outside the network.

Checklist

Video

Frequently asked questions

Does a visitor's phone need access to the plant network?

No. The address in the code must be reachable from the internet. Internal panels may remain inside the plant network.

What if the instance address changes?

The address is stored in the QR codes on printouts and in e-mails, so a change means printing the badges again. Close the decision about the address before the start.

Does a visitor without a phone also need internet access?

No. A person without an e-mail address and a phone receives a printout from security, and the code is scanned by the plant's equipment.

Let's check the network before the first invitation

We will go through the DNS, firewall and certificate checklist with your IT team. Book a conversation with the InnerWeb team.

Let's talk