oauth2 fixes #177
No reviewers
Labels
No labels
approved, awaiting change
broken setup
bug
cannot reproduce
configuration
documentation
duplicate
enhancement
extremely low priority
feature request
Fix it yourself
help wanted
invalid
mastodon_api
needs change/feedback
needs docs
needs tests
not a bug
not our bug
planned
pleroma_api
privacy
question
static_fe
triage
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
AkkomaGang/akkoma!177
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "oauth2-fixes"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
a lot of the oauth2 weirdness in pleroma was caused by it using the cookie-based session to pull out tokens - this meant that if you were to change frontends (and hence your token), your cookie would change as well, making the backend think you were a new user and skipping any checks for existing authorization
this change more or less removes session store for oauth2 (and honestly we should remove a lot more session stuff, oauth2 doesn't need state as well...)