Add support for authentication and online feed #73
Conversation
syhlx
changed the title
syhlx
force-pushed
the
authentication
branch
from
f2741b3 to
8aa6d43
Compare
|
I'm fairly new to kodi, if i want to use your fork of the repo, I just download it as a zip and install it in from it ? |
Yes, just make to sure to select the "authentication" branch before downloading as a zip from Github. |
|
Great. Thank you |
|
I'll have a look at that if I can find a stable public instance that would loan me an account for testing purposes |
|
How can I reach out to you. You can use my instance if you want. |
|
lekma at duck dot com |
|
but i will only be able to look at that next month at the earliest... |
|
so I had a quick look is there really no better way to login directly through the api??!! can you use the token on another machine (even though you never logged in with that machine)? if yes what happens when you logout on the machine you got the token with? is it revoked? can it still be used? otherwise it shouldn't be too difficult, i'll try it this week as soon as i have some free time. last question when "logged in" do you want the remote feed to be merged with the local one or do you prefer them to be exclusive? |
|
omg when login on the website the form sends the credentials in clear text... is that configurable on the instance? |
|
also i get a 403 for '/api/v1/auth/tokens/unregister' and '/api/v1/auth/tokens/register' while '/api/v1/auth/tokens' is ok... |
ok... this seems to be the norm for web developers... which only leaves us with the option of storing passwords in clear, if we were to implement automatic login... (thinking out loud here)... so... no automatic login?? |
|
forget my previous message (i think i'm having a brain fart....) |
|
progress: iv-org/invidious#5040 |
This enables access to a personal feed as user registered user of an Invidious instance.
To enable the feature, go to https://invidious.example.com/authorize_token?scopes=:* to generate a token a paste the entire string into the addon's settings (eg.
{"session":"v1:XXXXXXXXXXXXXX","scopes":[":*"],"signature":"XXXXXXXXXXXXXXXXXXXXX"}).If a token is present in the settings, the feed will default to the user's online feed (from the Invidious instance), if not, it will show the locally selected subscriptions.
This partially solves #41.