OAuth token non-retentive #77
Labels
No labels
bug
can't reproduce
confirmed
discussion
duplicate
enhancement
glitch-soc
help needed
suggestion
upstream
won’t fix
No milestone
No project
No assignees
2 participants
Due date
No due date set.
Dependencies
No dependencies set.
Reference
pleroma/mastofe#77
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Hi! I noticed whenever I use the MastoFE that the OAuth tokens aren't saved anywhere other than for a session, unlike the PleromaFE the MastoFE will ask for a new OAuth token each session. Is there by chance a possibility that by hosting both MastoFE and PleromaFE on the same domain it interferes with the login tokens?
Is there any way of making sessions last in MastoFE like they do in the PleromaFE?
Has nothing to do with pleroma-fe, more likely to do with the significant lack of testing&reporting. (I personally only have ephemeral sessions in my browser)
Not really sure what's going on, will try to debug, I thought it was a bug in chromium in one of my tests.
Ah! Alright, I thought it was possibly the way how the MastoFE handled the OAuth token.
And thanks! I will be trying to inspect the code a bit too how it handles the token since I was doing that anyway, I will report my results if I got any.