UpdateMachineAuthCallback is not triggered

[ExistentialDysfunction]

Hello, I have added a functionality to fetch steam guard code from the email, but after successful authorization there is no UpdateMachineAuthCallback event triggered, so there is no sentry file generated for some reason. Any ideas what might be the issue?

[zxcvqwerasdf]

Becase it's deprecated now. It's not an issue.

[STRATZ-Ken]

Wanted to include an example. I believe its some type of race condition.

In the attached image, you can see I am attempting to connect to Steam with a Refresh Token. (No Idea why, but it expired and is invalid, if anyone has information on this, would love to know, Persistent = true already). Once I notice that the 2FA is required, it disconnects and now is going through the login process again.

I log in again, however this time I got 2FA. (Which I should). Now, its currently authSession.PollingWaitForResultAsync but again while I am waiting it disconnects. By the time I get the 2FA in, the connection is gone. Do I reuse the old 2FA token here or do I wait for the new one and hope the connect stays until its completed.

Lastly, it then gets the 2FA, and attempts to send the 2FA to Steam, but the connection is already dropped and thus we get Attempting to send while not connected error.

Thanks,

[Christian-Stieber]

Once I get the request for a 2FA, should I still get disconnected and then relog with the 2FA?

No, you won't get disconnected... I think. It's been a while since I worked on this, but a quick test with an EMail-guarded account and a look into the log suggests there's no disconnect happening anymore.
I'm still having some problem with EMail-guard code handling, but that's likely unrelated to the question.

For me, the basic flow looks like this:

• I'm sending CAuthentication_BeginAuthSessionViaCredentials_Request
• I'm receiving CAuthentication_BeginAuthSessionViaCredentials_Response, telling me the account has guard-email
• I receive the EMail, and copy-paste the code into the bot
• I send CAuthentication_UpdateAuthSessionWithSteamGuardCode_Request with the code
• I receive CAuthentication_UpdateAuthSessionWithSteamGuardCode_Response
• I send CAuthentication_PollAuthSessionStatus_Request
• I receive CAuthentication_PollAuthSessionStatus_Response, giving me my refresh token (which I'm storing for future logins)
• I perform the normal CMsgClientLogon

Also, should RefreshTokens remain active for long periods?

Yes. I expect them to expire eventually, but haven't seen it happen yet.

When I saw the token exp it says May of next year

Oh... so I guess SteamKit has code to decipher these tokens? Good to know, I want that too :-)
...
Ok, found ParseJsonWebToken() :-)

[STRATZ-Ken]

The issue with the expiration is, if you call LogOff at any point, all your tokens are now invalid. However, if you call a Disconnect, you can reconnect using the same token. Thanks, all is working now. Though, I completely removed the Polling and made my own method as it was not dynamic enough to support everything I needed.

[xPaw]

To get account in GetEmailCodeAsync, copy UserConsoleAuthenticator implementation, and change it to pass in whatever data you want, so when you do Authenticator = new UserConsoleAuthenticator(), you can instead do Authenticator = new MyAuthenticator(accountName) for example.

The IAuthenticator is very simple, and specifically was made for things like this.

To handle email 2FA, you have to store GuardData that comes from PollingWaitForResultAsync, and then pass it into AuthSessionDetails, this works similarly to old sentry files.

See e3950f9

[skylayer]

I'm working through sample 1a and hit a snag with the NewGuardData from Steam's 2FA. After successfully logging in and approving the login on my phone, I expected to receive usable guard data for future logins. However, the NewGuardData appears empty. Here's the relevant code snippet and the exact output:

if (pollResponse.NewGuardData != null) {
    previouslyStoredGuardData = pollResponse.NewGuardData;
    Console.WriteLine($"Received new guard data, store this for future logons: {previouslyStoredGuardData}");
    Console.WriteLine($"Length of guard data: {previouslyStoredGuardData.Length}");
}

Output:

Connecting to Steam...
Connected to Steam! Logging in '[username]'...
STEAM GUARD! Use the Steam Mobile App to confirm your sign in...
Received new guard data, store this for future logons: 
Length of guard data: 0

Has anyone else experienced this? Looking for insights or solutions.

[ExistentialDysfunction]

So, it is currently impossible to receive and update the sentry file?