Complete OAuth Documentation Update with Phase 5 and Implementation Alignment #162
Conversation
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
lisad
approved these changes
Aug 10, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 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.
This PR completes our OAuth 2.0 documentation suite by adding the missing Phase 5: Protected Resource Access, which covers how clients use access tokens to retrieve ActivityPub data from our API endpoints.
The new Phase 5 documentation explains our dual-mode authentication system where the same endpoints serve both standard ActivityPub federation and enhanced LOLA portability data based on whether the request includes a valid OAuth token with the right scope.
I also reviewed and updated the existing phase documents to ensure they accurately reflect our current implementation. All code examples are verified against the actual codebase.
Close #141