| ✅ | Item | |----|------| | 1 | API contracts documented & approved by ForScan liaison | | 2 | UI mock‑ups reviewed by UX team | | 3 | Encryption helper reviewed by security team | | 4 | Unit & integration tests ≥ 80 % coverage | | 5 | Localization strings extracted | | 6 | Build pipeline includes secret‑scanning (no hard‑coded keys) | | 7 | Deployment scripts add required OS keychain permissions | | 8 | Release notes contain “New: ForScan license‑key management” | | 9 | Support team trained on troubleshooting validation failures | |10 | Post‑release monitoring: watch for > 0.5 % validation error spikes |
Allows reading, clearing DTCs (diagnostic trouble codes), and basic data viewing. Extended License (2-Month Free / Paid): forscan license key
+-------------------+ HTTPS +----------------------+ | UI (Desktop/ | <--------------------> | ForScan License API | | Web) | (POST /validate) | (validate, deactivate)| +---------+---------+ +----------+-----------+ | | | (1) Enter key | v | +---------+---------+ | | License Service | | | (client side) | | | - encrypt(key) | | | - store ciphertext| | +---------+---------+ | | | | (2) Validate request | v | +---------+---------+ | | Secure Storage | <--- encrypted blob ----------> | | (OS keychain) | | +-------------------+ | | ^ | | (3) Validation response (valid/exp) | +----------------------------------------+ | ✅ | Item | |----|------| | 1
| # | Requirement | Acceptance Criteria | |---|-------------|---------------------| | | License‑Key Input Dialog | • Modal dialog reachable via Settings → License . • Input field accepts up to 64 alphanumeric characters (including hyphens). • “Validate” button triggers immediate server check. • Success shows green check and enables full feature set. | | FR‑02 | Real‑Time Validation | • Call POST /api/v1/license/validate with JSON "key": "<key>" over TLS. • API returns "valid": true, "expires": "2027‑12‑31", "features": ["full"] . • Invalid response shows red error with friendly message. | | FR‑03 | Secure Storage | • Encrypt key using AES‑256‑GCM with a per‑device key derived from OS‑provided secure storage (Windows DPAPI, macOS Keychain, Linux libsecret). • Store only the ciphertext + IV + authentication tag. | | FR‑04 | Status Dashboard | • Shows Key , Status (Valid/Expired), Expiration Date , Days Remaining . • Auto‑refreshes every 24 h and on app launch. | | FR‑05 | Admin Overview Page | • Table view of all registered keys (one row per workstation). • Columns: Device ID, Key (masked, last 4 chars), Expiration, Owner, Last Validation. • Filters: “Expiring in < 30 days”, “Expired”, “Invalid”. | | FR‑06 | Renewal Reminder Engine | • Background job runs daily. • If daysRemaining ≤ reminderThreshold (configurable, default 30 days) send email & in‑app notification. | | FR‑07 | Auditing / Logging | • Log entry format: timestamp, userId, deviceId, action, keyHash, outcome . • Write to central logging service (ELK, Splunk, etc.) with appropriate masking. | | FR‑08 | Key Deactivation API | • Admin can POST "key": "<key>", "action": "deactivate" to ForScan’s deactivation endpoint. • Local UI marks the key as “Deactivated – contact ForScan”. | | FR‑09 | Backup / Export | • Generate QR‑code (UTF‑8 payload = plain key) and a plain‑text file (optionally password‑protected). • Export dialog warns about security. | | FR‑10 | Multi‑Platform Support | • Implementation works on Windows 10/11, macOS 12+, Linux (Ubuntu 20+), and on the web (React/Angular front‑end). | | FR‑11 | Localization | • All UI strings externalized; English + optional languages (German, French). | • “Validate” button triggers immediate server check
Contact the FORScan team via their official forum with your purchase details and Hardware ID. There is no automated "resend" system.