DeviantArt Oauth: write token to conf

[chrsmlls333]

I'm finding it inconvenient using the Oauth:deviantart feature then having to copy the refresh-token to my .conf before I run the task. As I may be flipping between multiple .conf files for different run tasks, it means each .conf needs to be updated (or am I incorrect?)

It would be very useful for the authorization process to take the received token and write it to the .conf or cache which it pulled the id/secret from.

Thanks!

[mikf]

Writing to a conf file isn't possible, but writing the token to cache might work.
(Although maybe there are security considerations for multi user systems with a shared cache)

As I may be flipping between multiple .conf files for different run tasks, it means each .conf needs to be updated (or am I incorrect?)

You can use as many config files as needed, 2-3 through the default config paths and an arbitrary amount through -c/--config, and their settings will internally be merged into one big dict-tree, where your settings are read from. You could therefore have one config file that only specifies your deviantart refresh token and all your other settings somewhere else.

(It might be useful to support an include option that would allow to specify more config files inside the first one ...)

[chrsmlls333]

Oh interesting! I have used such "configuration stacking" in Jekyll yamls, but didn't know gallery-dl would allow this.

I think it would be wholly intuitive for gallery-dl to save the refresh-token on first oauth in the same way it renews and keeps in cache throughout a long download cycle. Definitely a feature request, but seems sensible. Do you have any concerns over this behaviour?

[mikf]

913b833 is the first attempt of implementing this. Most of it is hidden behind options (see commit message), and it only works for DeviantArt at the moment, but I'll probably enable this by default and implement it for everything using OAuth in the next "big" release.

[chrsmlls333]

@mikf Are there any usage changes since these commits? Do you still need refresh-token: 'cache'?

[mikf]

extractor.oauth.cache is now enabled by default, and most(*) OAuth tokens are now set to "cache" by default, but there aren't any usage changes for Deviantart since the initial commit here.

gallery-dl oauth:deviantart is still writing the token to your cache file, and "refresh-token": "cache" will still read it from there, but you can technically delete them from your config file and it'll still work.

(you might want to read #807 (comment) and #807 (comment))

(*) support for Mastodon instances is still missing

[chrsmlls333]

This is all fantastic, thank you @mikf !! Feel free to close this unless you want to wait until Mastodon is settled.