TanQR Settings is a compact but powerful configuration layer for QR-based authentication and device pairing workflows. This guide walks through how to optimize TanQR Settings for faster scans, stronger security, and smoother user experience.
Below is a quick reference that maps core TanQR Settings options to their impact on device onboarding, scan reliability, and backend integration paths.
| Setting Name | Default | Impact on Scan Flow | Recommended for Production |
|---|---|---|---|
| Payload Type | URL | Defines whether the decoder opens a link, launches an app, or triggers API auth | App Deep Link |
| Session TTL | 15 min | Controls how long a signed token remains valid after scan | 30 min |
| Require Device Confirmation | Off | Adds a step where the device must approve the pairing | On |
| Rate Limit Scans | 10/min | Prevents abuse by capping scan attempts per device/IP | 20/min |
| Encryption Mode | AES-128 | Determines data protection in transit and at rest | AES-256 |
Optimize Payload Configuration
TanQR Settings allow you to choose between URL, vCard, plain text, and app deep link payloads. Selecting the correct payload type reduces fallback handling on the client and improves first-time scan success. For mobile apps, prefer deep link payloads paired with registered URL schemes.
Adjust Session and Timeout Values
Shorter sessions improve security but may frustrate users on slow networks. With TanQR Settings, you can set Session TTL between 5 and 120 minutes. For kiosk or shared-device scenarios, keep TTL low and enforce reauthentication to prevent session hijacking.
Harden Security and Device Confirmation
Enabling Require Device Confirmation in TanQR Settings introduces a final approval step on the paired device. This blocks accidental grants and makes it harder for attackers to pair without physical access. Combine this with rate limiting and encrypted payloads for a robust onboarding chain.
Fine-Tune Rate Limits and Encryption
TanQR Settings expose controls for scan rate limits and encryption modes. Raising rate limits too high increases spam risk, while setting them too low can block legitimate bursts. Use AES-256 in production to protect credential data and align with compliance expectations.
Deployment and Maintenance Recommendations
- Align TanQR Settings with your SSO and certificate lifecycle policies
- Automate configuration validation in CI/CD for staging and production
- Monitor scan success rates and adjust Session TTL based on real usage
- Rotate encryption keys on a defined schedule and test rollback paths
- Document settings for each environment and restrict edit access to admins
FAQ
Reader questions
Can I change the payload type after initial pairing?
Yes, you can update the payload type in TanQR Settings, but existing signed tokens will continue using the original format until they expire or are reissued.
What happens if the Session TTL is set too low?
Users may be forced to scan again before completing multi-step workflows, leading to a poor experience and support queries about failed sessions.
Does Require Device Confirmation work offline?
It does. The confirmation step is handled locally on the device, so TanQR Settings can enforce this even without an active internet connection.
How should I configure Rate Limit Scans for high-traffic events?
Set Rate Limit Scans to a value that matches expected peak concurrency per device, and monitor logs to adjust the threshold before events scale.