WiFiGate

WiFiGate automates captive portal / firewall Wi‑Fi login so you do not have to complete the same browser flow every time (for example Sophos-style httpclient portals on your local gateway). What you can do • Wi‑Fi policy — Maintain two lists: networks that require portal login (allowlist) and networks without a captive portal. On no‑portal Wi‑Fi, the app skips firewall auto‑login and server logout. The same network cannot be in both lists. • Direct HTTP login — Uses a browser-like request with cookies, then Sophos / Cyberoam-style login.xml when the portal matches, or a generic HTML form POST for other setups. • Clear errors — Timeouts, unreachable host, bad credentials, and unexpected responses are turned into readable messages. • Smooth manual vs auto login — Manual login can take priority; auto‑login waits instead of blocking you. • Secure credentials — After a successful login, your user ID and password are stored in encrypted secure storage (not ordinary app settings). • Auto Login Agent — When enabled, the app checks Wi‑Fi and portal session and signs you in automatically with saved credentials when policy allows. • Web Portal (WebView) — Full-screen web portal when the direct path is not enough; optional auto‑fill for common Sophos-style fields. • Logout — Calls the portal logout endpoint when supported and when you are not on a no‑portal network; clears the in‑app session. Saved credentials stay so auto‑login can work again after the next sign‑in. • Biometrics — Optional fingerprint sign‑in after you have completed a manual login once. • Session & Home — Sign in or continue on no‑portal Wi‑Fi, see Wi‑Fi status, open the web portal when needed, refresh and reconnect from the dashboard. • Settings — Edit the firewall / portal URL, manage Wi‑Fi lists, toggle the Auto Login Agent, mobile data warning, and biometrics; open About for version and support info. • Activity logs — Local activity log (info, warnings, errors, success) to help you see what happened. Compatibility • Sophos / Cyberoam-style portals (login.xml / logout.xml) are the primary supported path. • Other vendors may work via generic form login; otherwise use Web Portal or extend the app for your gateway. Important notes • Login runs on Wi‑Fi (not when you are cellular‑only). • SSID may be unavailable without the right permissions or on some devices; you can still use IP / gateway rules where configured. • The app cannot force all traffic only over Wi‑Fi when mobile data is also on; an optional warning is available. • Long‑running background “keep‑alive” is limited on typical Android/Expo setups; behavior follows foreground use and network changes. • Some HTTPS portals with custom certificates may need a custom build. Session screen footer in the app: Powered By CPB‑IT (see in‑app About for details and links).