Provide username (and password) for authentication request

[Phil0L]

Hello everybody,

I'm trying to create an application that can control multiple Spotify accounts.
For this I make multiple authentication requests via authentication code auth flow.
It works fine and I can get multiple access tokens.
The only problem I have is that the api seems to only remember the last used credentials.
What's currently happening:
The application requests access token 1 for user 1 -> I log in and grant all permissions.
The application requests access token 2 for user 2 -> I log in and grant all permissions.
Restart of the application.
The application requests access token 1 for user 2 ↯

What I'm trying to achieve:
Upon restarting the application, all access tokens should be received without user input again

I'm thinking of two possibilities, but I can't seem to find a way to achieve them.
Either save not only the last user, but several
Or provide the username (+ password) in the authentication request.

Anyone have any idea how to do something like this?
Thanks in advance

[dargmuesli]

How do you persist access tokens? Sounds like a code example might be of use here.

[dargmuesli]

It's not clear to me how

the api seems to only remember the last used credentials

works while

When I restart the application, they are lost

and you

Restart of the application

Why would

The application requests access token 1 for user 2 ↯

If

They are lost

[Phil0L]

If I just take a spotify account and start the authentication process, then spotify wants my access data and after entering it redirects me to the redirect url. now when i stop and restart the application, spotify redirects me to the redirect url without any prompt. this is the behavior i want. I want you to only have to log in once. so how does the api (or spotify or whoever) store those last used credentials? And do I get it somehow that 2 credentials are saved? Or that I send the credentials via api?

[dargmuesli]

This api wrapper does not store anything, the REST api itself should neither. It seems like it's up to you to set a breakpoint and step through your code to see why a url is opened.
You're correctly using 2 api instances as far as I can see.

[Phil0L]

So...
First of all, thank you very much for your help.
I was very stupid. I overlooked the one obvious thing. The REFRESH TOKEN...
I now persist the refresh token in a file, to recreate an access token at any time.
The refresh token does not expire right?

I will mark this discussion as answered.

[dargmuesli]

I'm not sure, actually. I think some but not all authorization flow implementations (in the www) do set a (very long) expiry for refresh tokens. Not sure about Spotify.