Who these recommendations are for
These recommendations are addressed to the IT and OT IT departments of a production plant that enables access to the safety system from phones: workers' own phones, company phones, and phones of guests or drivers. We assume the system runs in the browser and that a badge with a QR code opens an address with a token, with no app to install.
Each recommendation has a rationale that follows from how the system works, so that IT can assess the risk and decide for itself.
1. Provide HTTPS on an address reachable from the phone
The QR scanner in the browser requires a secure context, HTTPS. An installation shared over plain HTTP under an IP address will not start the camera, so the user will see a message about an insecure context instead of the scanner window.
Make sure the certificate is trusted by phone browsers, including those on the guest network, and use a domain name rather than a bare IP address. Test the address from a phone outside the internal network, because a guest's device does not know the certificates of the internal certificate authority.
Number of IT decisions before the first day
2. Set firewall rules and do not rely on external CDN resources
The camera of the training tablet uses the browser's native barcode detector and, when it is missing, a library loaded from the system's own server instead of an external CDN. The reason is practical: the plant firewall rejects such traffic without a message, so the scanner does not start and the user does not know why.
During deployment, check which domains and ports are open from the network the phones use, and propose a plant rule: everything the screen needs comes from one installation address.
3. Limit supported browsers to a list you test
Not every browser provides the same code detector, and older phones may support none of them. The system then shows a message about lack of support, but that message does not replace the plant's decision on which browsers it supports.
Prepare a short list of supported browsers and phone system versions, test the badge scan on it, and publish it at the gate and in the invitation. For everyone else, the plant defines a fallback, for example a scan on a tablet at the gate.
4. Plan camera permission and four error messages
The browser asks for permission to use the camera. The system distinguishes four situations and shows a separate message for each: no permission, no camera, insecure context and lack of support. Prepare a short instruction for gate officers and help desk staff: which message means what and who fixes it.
The most common case is permission denied on the first try. Decide whether the plant instructs people how to change permissions in the browser settings, or directs the person to the tablet at the gate.
- No permission: change the camera permission in the browser.
- No camera: the device has no camera or another application is using it.
- Insecure context: an address without HTTPS, fixed by IT.
- Lack of support: a browser without a detector, fallback variant.
5. Decide what to do about private phones and guest networks
Access without installation means no software stays on the phone, but the address with the token may remain in the browser history. Decide whether the plant allows workers' private phones or only company phones, and describe this in a policy that IT can verify.
For guests and drivers, establish which network they use: the plant's guest network or their own mobile data. Both options require that the system address be reachable and that the firewall does not block traffic from the guest network to the installation.
6. Test the whole path before the first day
The test should cover the full flow: scan, confirmation of the person, start of training and saving the result. Run it on phones from different systems and browsers, on the guest network and on the internal network, and record the results in a table with the date and browser version.
InnerWeb is a software producer and does not supply or replace the plant's equipment: phones and tablets are the client's responsibility, and we help define the requirements for the browser, the address and the firewall.
Video
Frequently asked questions
Why does the scanner not start the camera on an IP address?
The browser requires a secure HTTPS context. An installation over plain HTTP under an IP address will not start the camera, and the system shows a message about an insecure context.
Why do we not use an external CDN?
The plant firewall rejects such traffic without a message. The scanner library is therefore loaded from the installation's own server.
Does InnerWeb supply phones and tablets?
No. InnerWeb is a software producer. Devices with a browser are the client's responsibility.
Preparing the network and browsers for the safety system?
Book a talk with IT: we will go through HTTPS, the firewall and the list of browsers and prepare the requirements for your plant.
Let's talk