Audit all visible form control gaps and document QR authorization limits

2026-10-02 23:40:50 +08:00
parent ee2858e556
commit 0c18cabc92
2 changed files with 25 additions and 1 deletions
@@ -113,3 +113,26 @@ official account session by these RPC methods. This confirms the distinction
 for the currently observed endpoints; it does not prove all future widget APIs
 will require a WeChat-specific session. An official account login session may
 also be supported, but has not been verified here.
+
+## QR authorization feasibility review (2026-10-02)
+
+Rechecked the official 1.6.5 client artifact. Its observed WeChat login flow
+obtains a code through the WeChat provider and submits `app.wxlogin` with `code`.
+The account/password flow calls `app.login` with `username` and `password`.
+No QR-login creation, confirmation polling or authorization callback contract
+has been identified in that artifact or the public KoKonna documentation.
+Absence in this client does not establish that no server-side QR API exists.
+
+A QR code opening the official mini-program does not transfer its session to
+Frame Flow. A functional connect-by-scan integration requires an official
+third-party authorization handoff (challenge, user confirmation, callback/polling
+and an authorized credential exchange). Generating a decorative QR or registering
+Frame Flow's own WeChat login is not evidence of access to KoKonna account data.
+Do not advertise scan-to-connect until that complete contract has been verified.
+
+An official-account login connection is a possible alternative, pending a
+legitimate account and verification that it accesses the user's existing
+mini-program device. Frame Flow credentials are unrelated; do not ask users to
+enter their Frame Flow password as an official credential. The current integration
+only accepts an explicitly provisioned official session secret. No login attempts,
+new proxy changes or credential persistence were performed during this review.