AuthForge supports per-app access control lists for HWIDs and IP addresses. Use them to block pirated copies, restrict beta access, or geo-limit your application.Documentation Index
Fetch the complete documentation index at: https://docs.authforge.cc/llms.txt
Use this file to discover all available pages before exploring further.
How it works
During license validation (/auth/validate), the server checks the requesting HWID and IP address against your app’s access control lists before validating the license itself.
Evaluation order
- IP blacklist: If the IP is blacklisted, reject immediately.
- IP whitelist: If a whitelist is configured and the IP is NOT on it, reject.
- HWID blacklist: If the HWID is blacklisted, reject.
- HWID whitelist: If a whitelist is configured and the HWID is NOT on it, reject.
HWID blacklist
Block specific hardware IDs from authenticating. The HWID is the SHA-256 hash the SDK collects from the user’s machine. Use cases:- Block a known pirated/cracked machine fingerprint
- Revoke access from a specific device without revoking the entire license
HWID whitelist
When set, only listed HWIDs can authenticate. This is allowlist mode; any HWID not on the list is rejected. Use cases:- Restrict a beta to specific testers’ machines
- Lock down access to known-good devices in an enterprise deployment
IP blacklist
Block specific IP addresses from authenticating. Use cases:- Block IPs associated with abuse
- Block known VPN/proxy ranges
IP whitelist
When set, only listed IPs can authenticate. Useful for enterprise environments where users connect from known office IPs.Configuration
Via the dashboard
Go to your app’s Settings → Security. You’ll see four sections for each list type. Add entries and click Save.Via the Developer API
Get current security config:Limits
| Limit | Value |
|---|---|
| Max entries per list | 1,000 |
| HWID value max length | 128 characters |
| IP value max length | 45 characters (supports IPv6) |
Error response
When a request is blocked by a blacklist or whitelist, the SDK receives:Next steps
- Security API Reference; Full endpoint documentation
- Security Best Practices; Hardening your AuthForge integration