docs: LINE (OIDC compliant) & Snapchat (Custom auth token) authentication#1327
Merged
MichaelVerdon merged 11 commits intomainfrom Feb 24, 2026
Merged
docs: LINE (OIDC compliant) & Snapchat (Custom auth token) authentication#1327MichaelVerdon merged 11 commits intomainfrom
MichaelVerdon merged 11 commits intomainfrom
Conversation
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
MichaelVerdon
approved these changes
Feb 6, 2026
dackers86
reviewed
Feb 9, 2026
Member
|
The Line button in the description (recording) appears different from the example applications. Should the custom auth button for LINE be updated to match these examples? 
Screen.Recording.2026-02-12.at.11.21.22.mov |
dackers86
approved these changes
Feb 24, 2026
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.
CUSTOM_AUTHENTICATION.mdon authenticating with custom OIDC provider, and documentation on signing in with OAuth 2.0 + custom token created on a server using Firebase Admin.What it looks like in the React example app:
Screen.Recording.2026-02-05.at.16.32.43.mov
Screen.Recording.2026-02-24.at.14.04.47.mov