Never assume internet connectivity. Your wizard must detect network loss and instantly offer the offline/phone method. Do not hide it in a submenu.
Attackers often target the wizard by bypassing the server check. Common attack vectors include:
To truly master software activation, one must understand the underlying handshake between the client software and the licensing server. product activation wizard
| Phase | Action | User Expectation | |-------|--------|------------------| | 1. Launch | Wizard appears on first run or after trial expiry | Clear context (“Activation required to continue”) | | 2. Input | User enters a product key / license code | Simple field, paste support, character grouping | | 3. Validation (client-side) | Basic format check (e.g., length, checksum) | Instant feedback on obvious errors | | 4. Communication | Wizard contacts activation server (HTTPS) | Progress indicator, timeout handling | | 5. Server validation | Key validity, activation count, product version | <3-second response | | 6. Response handling | Success → unlock features; Failure → show actionable error | Specific error message (not “invalid key”) | | 7. Confirmation | “Activation complete” screen | Option to close wizard or view license details |
Pros:
Cons:
Modern wizards utilize Product Key Blacklisting. Even if a Keygen produces a mathematically valid key, the server maintains a database of keys known to be leaked or generated illegally and will reject them during the validation handshake. Never assume internet connectivity
This is the default mode for consumer software like Windows 10/11, Adobe Creative Cloud, and Microsoft Office.