Pub Sub with fully server side authentification

[BarryCarlyon]

@Sylvanus

BUT, I must also whenever I use it, use the refresh function, which is completely backend. And the newly generated token access must replace the old access_token in my configuration to be used.

Correct, whenever the user access token dies, you can auto fetch a new access token using the refresh token

@Sylvanus

In reality if we follow your logic, I have to store the two keys permanently and have them changed, my program must, on each startup, refresh the access_token so my configuration changes constantly?

Correct!

@Sylvanus

Do you understand that we mix frontend operation and backend operation in the same process?

Yup, that is pretty standard when it comes to oAuth.

• Get permission from the end user once.
• Then you run using the token till it dies
• Refresh that token using the refresh token
• store the new access token (and new refresh token if one is provided)
• And use the new token

@Sylvanus

So I have to write this acces_token in a hard copy (and if necessary also store the refresh token) so that my application can use it as part of its connection to the Pub / Sub service.

I store mine in a database generally, and I fetch/save as needed rather than hard coding it