From my understanding, the image below overviews Steams OpenID implementation, when you start the session and satisfy one of the guards, steam sends an access token and a refresh token, part of the OAuth 2.0 authorization framework? These tokens can be used to obtain web session cookies, would this be the cookie headers located on a steam page- steamLoginSecure, sessionid, browserid, etc? Or a different kind of session cookies altogether? Would the goal of the refresh token sent by steam be for maintaining a session without needing re-satisification of a guard, or re-login? (perhaps "extending" was the wrong word here). If so, node-steam-user/others could use the same refresh token for ~200 days, without needing reauthentication to manage and automate account related actions and obtaining the session cookies mentioned earlier? At the end of this 200 days, the refresh token JWT (stored in the browser cookies?) would expire and a new login + guard satisfy would be required?
Ive also heard that these tokens are almost always used with API authorization, if this is true in this case, how is one able to use these tokens for obtaining web session cookies and logging in with node-steam-user?