Overview

Device authorisation allows tablets to securely access Central-Ops without requiring users to sign in each time. When a tablet is authorised using a 6-character code, it remains authenticated for extended periods, making it ideal for shared devices in vehicles.

This article explains how device authorisation works and how to troubleshoot devices that require frequent re-authorisation.

How device authorisation works

When you authorise a device using the 6-character code, Central-Ops sets an authentication cookie with the following behaviour:

• 100-day expiration - The cookie remains valid for 100 days from the last use
• Sliding expiration - Each time the device is used, the expiration extends automatically
• Persistent across sessions - The device stays authorised even after closing the browser

In practice, a device used at least once every couple of months should never need to re-authorise. This design accommodates scenarios such as school buses remaining idle over Christmas holidays without requiring re-authentication on the first day back.

In This Topic

Related Topics

Authorised Devices

Troubleshooting frequent re-authorisation on iPads

If devices are requiring authorisation more often than expected, the issue is typically caused by the iPad clearing the authentication cookie. The most common causes are:

Safari Intelligent Tracking Prevention (ITP)

Safari includes privacy features that can cap cookie lifetimes to as little as 7 days. This is especially common when:

• The app is accessed via a Home Screen shortcut
• The app runs through a managed browser or MDM portal
• "Prevent Cross-Site Tracking" is enabled

MDM policies

Mobile Device Management software may enforce policies that periodically clear website data or restrict cookie storage.

Storage pressure

When iPad storage runs low, iOS may automatically clear website data for sites that haven't been used recently.

Diagnostic checklist

If devices are losing authorisation unexpectedly, check the following:

1. How is the app accessed? Home Screen shortcut, Safari directly, or MDM portal/managed browser?
2. What iPadOS version is installed? Navigate to Settings → General → About
3. Is "Prevent Cross-Site Tracking" enabled? Check Settings → Safari → Prevent Cross-Site Tracking
4. What MDM software is in use? Check for policies that clear website data or enforce Safari settings
5. How often does re-authorisation occur? If roughly every 7 days, Safari ITP is the likely cause
6. How much free storage is available? Low storage can trigger iOS to clear website data