📱 qrtak

Generate configuration QR codes for rapid TAK client deployment

TAK Configuration

Configure TAK clients for rapid deployment

Configuring for Android devices (ATAK)

🔗 Connection

Enter the TAK server address for enrollment

🔐 Authentication

⚠️
Security Notice: QR codes do not encrypt credentials. Anyone who can scan one can read the username and token. Share credential-bearing codes only in controlled environments.

Generated QR Code

Scan this QR code with ATAK to automatically configure the connection

📱
Enter configuration details to generate QR code
⚠️
QR Enrollment Has Limitations

If enrollment fails, ATAK shows: "The TAK Server's identity could not be verified"

When it works: Certificates from trusted CAs (like Let's Encrypt) that are in Android's system trust store.

When it fails: Self-signed certificates or untrusted CAs not in Android's trust store.

Technical limitations: The ATAK enrollment QR uses ATAK's default stream connection, port 8089 with SSL. The certificate-enrollment HTTPS connector uses a separate server port.

For self-signed certificates: Use the Data Package Builder tab instead - it lets you include your server's certificate so ATAK will trust it.

URL Import Configuration

Import data packages or configuration files via URL

Enter the URL of a data package (.zip) or configuration file to import

Generated QR Code

Scan this QR code to import the specified data package

Enter URL above

Data Package Builder

Create TAK client package layouts with config.pref, certificates, a manifest, and optional files

Auto-Enrollment: Package contains server info and CA certificate. ATAK prompts for enrollment credentials after import; the package does not include the password.
Auto-generated from server and client details. Leave empty for smart naming or specify custom name.
Username for server authentication (required for auto-enrollment, optional for soft-cert)
Password for server authentication
Root CA certificate (.p12) and its password - required for server trust
Pre-generated client certificate (.p12) and its password - only needed for soft-cert deployment
Drag & drop files here, or click to select
No files selected

Bulk Onboard: TAK Users (.txt)

Upload your TAK Server tak_users.txt export, set the server host, then step through users and scan. Processing stays on this device.

Hostname only, no protocol. Example: tak.example.com
Expected JSON array: [{\"username\":\"demo1\",\"password\":\"...\"}, ...]. Typical filename tak_users.txt.

Preference URI Builder

Build a tak://com.atakmap.app/preference URI with one or more key/type/value entries

💡 Tip: Search and select a known preference above to auto-fill the key field, or manually add custom preferences below.

Generated QR Code

Scan in ATAK to apply preferences

No preferences added yet

Use the search above to find known preferences
or click "Add Preference" to manually add custom ones

Configuration Profiles

Save and manage configuration profiles for quick deployment

Saved Profiles

qrtak Help

Generate enrollment and import QR codes, build configuration packages, and create bulk user QR codes in your browser.

🚀 Quick Start

1

Select a Tab

Use: TAK Config (ATAK/iTAK), URL Import, Data Package Builder, Bulk Onboard, Preferences, or Profiles.

2

Fill Required Fields

Required inputs show red until valid, then green. Hostname/port are validated; optional fields remain neutral until filled.

3

Generate & Scan

QRs render automatically when valid. Scan with ATAK/iTAK or download/copy as needed.

4

Save Profiles

Store current configuration for reuse. Overwrites prompt for confirmation.

📱 Tabs Overview

TAK Config

Unified configuration with two modes:

  • ATAK: Enrollment QR with host, username, and password/token.
  • iTAK: Quick‑connect CSV in QR (description,host,port,protocol).
ATAK/iTAK Validation QR Code

URL Import

Create an ATAK import QR for a data package or configuration file at a URL. ATAK asks the user to confirm before importing.

Import Validation QR Code

Data Package Builder

Build configuration packages with config.pref, certificates, and a manifest. When client = iTAK, protocol tokens are ssl (HTTPS) and tcp (HTTP); QUIC is hidden.

Packages Client package layouts ZIP

Bulk Onboard

Onboard many users from tak_users.txt (JSON array of {username,password}). Enter server host once, then step through users with Prev/Next or ←/→. Show/Copy controls sit under the QR and reset per user. The list fills the sidebar for efficient navigation.

Bulk Keyboard Validation

💡 Best Practices

Security Considerations

  • ⚠️ Password Security: Avoid including passwords in QR codes when possible
  • 🔒 Data Packages: Use data packages for sensitive configurations
  • 👥 Access Control: Limit access to configuration tools

Mass Deployment

  • 📋 Profiles: Create standardized profiles for each team/role
  • 🖨️ Print Handouts: Generate printed QR codes for field deployment
  • 📱 Kiosk Mode: Use large displays for group onboarding

Configuration Management

  • 🔄 Version Control: Keep track of configuration changes
  • 🧪 Testing: Test configurations in safe environments first
  • 📝 Documentation: Document custom configurations and templates

🔧 Troubleshooting

QR Code Issues

  • QR Code Too Large: Try using data packages instead of direct configuration
  • Scanning Fails: Ensure good lighting and clean QR code display
  • Invalid Configuration: Check your input values and validation messages

Connection Problems

  • Server Unreachable: Verify hostname/IP and network connectivity
  • Authentication Failed: Check username and token/password
  • Port Issues: Ensure correct port number and firewall settings

📚 Additional Resources

Project Inspiration

Technical Documentation

Community Support

📞 Support & Contact

For technical support or feature requests: