WHy is the login page via chrome additionally needed to auth.json to authenticate against OF? #16
No Assignees
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: sim0n00ps/OF-DL#16
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?
I know there was an answer in the old github repo but I don*t get it!
BTW, thank you all for your wonderful work and necessary contribution to get what is our legal concern! That project here means countless hours of work, I really appreciate that. Especially when it comes to the unprecendented and unspeakable behaviour of "our" forum. They have been never been of help, regarding all concerns with all kinds of betrayals which is allowed on the forum and is not penalized by the admin and support team, only for example...
If anybody needs financial support, please let me and us know. I am very upset that our forum acts like an idiot here. I will support you with my small ressources.
As of 1.9.x, there are now two methods to authenticate. There's still the legacy auth.json method (either manual or using the browser extension), or you can use the new Chromium browser to log in and have Puppeteer extract your session credentials automatically. This was done to make things easier for new users, they can just start the app, log into the browser, and hit thr ground running.
If you can't use the new method (such as if you log in using Google), or don't want to use it, you can enable DisableBrowserAuth in config.conf to revert back exclusively to the auth.json method if authentication.
@melithine Thanks! No it is a very nice feature, I only faced problems with it. And had to start twice....WIth the old deleted repo I had the problem that the login page via chromium, na, it was logged in but automatically without giving it credentials, but authentication failed in the tool. So I thought, that the before used method, which I knew now well was ok for me. But now I give it a try. So I can close the chromium after logging in? And in will only be used again if my token goes invalid? Or do I have to do it every start again?
the new config.conf is more structured, why didn't you use json anymore? Just a question! Your tool works like a flaw, and I so happy to have it found and used....
In the end it worked!!! Not that I put you on the wrong track.
@melithine : Last additional question: Is it possible to sum up all downloads, statistics? How many files, kinds of files, Total sums?
We can then close the issue, thanks!!
OF-DL doesn't support that, but you could definitely create a program that does that using the sqlite databases in the Metadata folder of each creator.