Getting DMArchiver to work with phone verification and login codes

[Gorrrg]

Whenever I want to use DMA I have to disable phone verification, it's a minmal risk as I can turn it back on again right after. But I imagine if you'd use it more often than me, it becomes a hassle. And even worse some people might forget to turn it back on or leave it off on purpose because of that.

Now I tried using the login code sent to me on my phone as a password once, and it obviously didn't work. Also the 1 hour temporary app password doesn't work. Do you think you can add support for proper app authentication or look into why the temporaray password doesn't work? And then add a command line switch -pv (phone verification) or something?

[Mincka]

I will definitely look into it. It does not seem too hard to implement.

I tried to use the temporary password using a web browser but wasn't able to use it. It seems to be done only for third-party apps and devices. Maybe something related to the user-agent or some other context parameter used. I guess it's less important to have the temporary password working here.

I will allow to use a SMS or TOTP code directly in the arguments or interactively.

[mythofechelon]

I tried using my username and an app password too but those credentials were rejected with error "Your username or password was invalid" too.

[Mincka]

Like I said, the application password cannot be used for a web browsing session (what the tool simulates).

You have to disable multi-factor authentication temporarily or wait that I, or someone else, implements the support for phone verification code.