feat(auth): add mobile client authentication support#407
Merged
IharKrasnik merged 3 commits intoak/boostfrom Mar 11, 2026
Merged
feat(auth): add mobile client authentication support#407IharKrasnik merged 3 commits intoak/boostfrom
IharKrasnik merged 3 commits intoak/boostfrom
Conversation
- Add ACCESS_MOBILE token type and client type detection utility - Update auth endpoints to return tokens in response body for mobile clients - Add google-mobile endpoint for mobile Google OAuth - Support automatic client type detection via headers (X-Client-Type or Authorization Bearer) Mobile clients receive tokens in response body, web clients continue using cookies. Co-authored-by: Cursor <cursoragent@cursor.com>
aleksays
requested review from
IharKrasnik,
cr1of0x and
fruneen
and removed request for
fruneen
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
3 participants
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.
Mobile clients receive tokens in response body, web clients continue using cookies.