Repository navigation
docs: react native sdk, mobile passkeys and bearer transport - #43
Merged
Merged
Conversation
Two new Build pages: the React Native SDK (bearer transport, the ports, the hooks, the sign-in flows on a phone, calling your own API, the keychain after a reinstall) and Mobile Passkeys (the associated domain, both association files, the auth server's origins, the app declaration, how to check it, and carrier NAT against the flow rate limits). The server SDK page gains the bearer contract and requireAuth's authServerUrl and audience; secure routes gains the native variant of calling a protected route; the React SDK page names the shared client package and the ports and transport options; the ecosystem, system config and CLI pages pick up the new package and the mobile template.
13 tasks
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.
Documents the mobile work landing across the ecosystem: fells-code/seamless-auth-server#162 and #164 (bearer guards and transport), fells-code/seamless-auth-js#149, #150 and #151 (
@seamless-auth/client, ports,@seamless-auth/react-native), fells-code/seamless-templates#90 and fells-code/seamless-cli#205 (the Expo template and--mobile), and theflow_rate_limitskey from fells-code/seamless-auth-api#310. Best merged once those have shipped, so nothing here describes a package that is not yet on npm.New pages
AuthProviderand the three ports, reading state,useAuthorizedFetch, the sign-in flows on a phone (passkey, codes, magic link polling and universal links, OAuth through an in-app browser session), passkeys anddescribeDevice, the keychain-after-reinstall caveat, and the boundary.apple-app-site-associationandassetlinks.jsonwith the traps (Team ID is the certificate OU, one fingerprint per signing key), the auth server'soriginsadditions with the web origin first, the Expo declaration, how to check each piece (otoolfor simulator entitlements,pm get-app-links), and carrier NAT againstflow_rate_limits.Updated pages
requireAuthwithauthServerUrlandaudience, a "Bearer Transport For Native Clients" section, coverage mentions React Native and Fastify.@seamless-auth/client, adds "Platform Ports And Transport" withuseAuthorizedFetch.--mobile=expo.Verified
npm run build(35 pages),npm run lintandastro checkpass (the pre-commit hook runs all three).