Question about the login process. #3335
-
|
Hello dear ASF team, I am very enthusiastic about your program and it really works very well! The program has motivated me to try something with the Steam API myself and to write some scripts that track certain community mark histories. Thank you very much for your answers! |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 4 replies
-
|
ASF goes through login gate set up by Steam, we use SteamKit2 library for that, passing the gate requires login, password and optionally also 2FA detail such as mobile token or e-mail one. After passing the gate, we're given access and refresh token to work. Access token is valid only for around 24h, while refresh token is valid for much longer period. Refresh token is used to obtain new access token when old one is close to expiration, it's also used for refreshing the refresh token as well. The cookie value you've asked is created from constructing You have the full source of ASF if you want to dig deeper and see the code responsible for above. You might also have more luck coding your stuff using ASF plugins, which will allow you to use existing ASF mechanisms and skip 9 years of headaches that we (especially me) had to resolve before you. Or do it the hard way if you like 😉 |
Beta Was this translation helpful? Give feedback.
-
|
Thank you very much for your answer! You have very good points there, and I think I won't be able to realize it without using ASF. You only work with Steam Session Cookies and not the Steam API, right? Could I then get the session cookie for my program (ASF is running for me anyway) every 24 hours and continue working with it in another program? |
Beta Was this translation helpful? Give feedback.
-
|
ASF works with everything, for API access token can be used instead of API key in some endpoints, other require API key or different credentials.
That's not supported scenario, ASF credentials, including tokens, are expected to be used by ASF exclusively. Most likely they'll not work for you either due to different user-agents, method of obtaining them (CM servers) and likewise, even if you "steal" them from ASF.
Advantage includes not wasting hours trying to get all the missing bits and pieces together by writing code that can focus on your needs right away. You could like, skip whole this thread asking how to obtain session cookies and just tell ASF to send your web request. If you intend to go hard way and do it yourself then you're more than welcome to, but don't expect from me to do your homework in how to get there, I've already spent last 9 years doing it in ASF 🙂 |
Beta Was this translation helpful? Give feedback.
-
|
Wow, that was a quick answer, thank you! You're 100% right, of course. I'll try to read more of your good and really detailed documentation to get a bit more understanding. |
Beta Was this translation helpful? Give feedback.
-
|
Quick question: Where can I find the information about ArchiWebHandler? |
Beta Was this translation helpful? Give feedback.
-
|
Source code. |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
ASF goes through login gate set up by Steam, we use SteamKit2 library for that, passing the gate requires login, password and optionally also 2FA detail such as mobile token or e-mail one.
After passing the gate, we're given access and refresh token to work. Access token is valid only for around 24h, while refresh token is valid for much longer period. Refresh token is used to obtain new access token when old one is close to expiration, it's also used for refreshing the refresh token as well. The cookie value you've asked is created from constructing
{steamID}||{accessToken}value, where access token is as described before, whilesteamIDis simply steam identificator of the account in its…