Repository navigation
Secure Puter session storage and verify login on app startup - #6
Draft
CodeByArnob wants to merge 7 commits into
Draft
CodeByArnob wants to merge 7 commits into
CodeByArnob wants to merge 7 commits into
Conversation
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This draft implements the safe credential-storage and startup-validation foundations for the external-browser authentication work.
Changes
flutter_secure_storage11.2.0, using Android Keystore-backed encrypted storage (RSA-OAEP + AES-GCM defaults)./whoamiendpoint before restoring the authenticated UI state.Not included / blocking requirement
This PR does not claim to implement Chrome-to-app session handoff. The documented Puter.js flow returns a browser-side popup result; no official native Android redirect/PKCE callback contract has been verified. A secure handoff still requires a supported Puter native callback or a reviewed one-time relay design. No bearer token is placed in a URL, no Chrome cookies/storage are scraped, and no unverified deep-link token is accepted.
Validation
CI must install the new dependency and run format, analyze, tests, and Android build. Physical-device validation is still required for KeyStore migration and startup verification.
Closes neither the external-browser handoff nor issue #1 until that final part is implemented and tested.