Feature Request: Disable new authentication flow #1
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: sim0n00ps/OF-DL#1
Loading…
x
Reference in New Issue
Block a user
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?
Users who can't use the new authentication flow are getting annoyed at it deleting the auth.json when it fails. We should have a config option to disable the new flow for these users and expose the fact that the auth.json is invalid.
I'm not sure the correct fix, but the current behavior is that I had a working install, but when I updated to the latest Docker image auth fails and my auth.json gets deleted. I am not sure how to solve that given I am running the container on a server and there is no "pop up" login window or anything similar.
You can still use the new browser based (interactive) auth method with docker. You just need to navigate to the server's IP address and the port you defined in the docker run command (the docs and tutorial use 8080) when prompted by OF-DL. The macOS tutorial video in the documentation channel of the discord server shows this being done.
And you can also still use the browser extension, too. The new versions after the switch from GitHub didn't change the authentication logic, your old auth.json must have been invalid (the most likely culprit being the browser user agent being updated on whatever browser you generated the old auth.json file from, and trying to use the wrong user agent caused OnlyFans to invalidate the entire session).
My Auth.json file got deleted, and of course the github documentation disappeared, so how to build my own auth.json?