PREFIRE

Hello, I authorize to an account via refresh_token and I get a cookie in the response. Sessionid as I understood should be universal, but in fact it does not fit for steampowered. I have to make an extra request and parse the sessionid from the page code. Is it possible to get sessionid for steampowered domain additionally?

Hello, Steam has released an update that allows you to create a .maFile without a phone number (at least on a real phone). 

Is it currently possible to create .maFile without number via node-steam-user (5.0.4) or any of your other modules?

Many thanks!

Hi. I've created a similar topic before (https://dev.doctormckay.com/topic/4610-mailguard-spontaneous-activation/#comment-12157), but now the question has changed a bit. I noticed this peculiarity: after registering an account, if you log in via the web (normal browser) - MailGuard is not enabled, but if you do it via the client - it is automatically enabled.

The difference of the question from the previous topic: it used to be enabled even after logging in via web (regular browser), but the problem was solved by logging in via refresh_token through steam-session with further obtaining of cookies. 

Now I would like to know if it is possible to do something similar with the client, so that when logging in MailGuard is not activated arbitrarily?

I realize that this is not a module problem, but I couldn't find a better place for this question

Thanks in advance for the answer!
 

Hello!

Previously, my software had authorization of a newly registered account followed by saving authorization cookies via the following code:
 

const client = new (require('steam-user'))({
[`${[[PROXY_TYPE]].toLowerCase()}Proxy`]: [[PROXY_STRING]],
});

[[COOKIES]] = await(new Promise((resolve, reject) => {
    client.on('webSession', (_, cookies) => {
        resolve(cookies);
    });

    client.on('error', reject);

    client.logOn({
        accountName: [[LOGIN_STEAM]],
        password: [[PASSWORD_STEAM]],
    });
}));

but after some time I noticed that after such authorization - Steam turns on MailGuard spontaneously (if at the same time to fill out the profile, through requests, then turning on MailGuard - 100%).

In the same order of actions, but through emulation (I do everything through BAS) - MailGuard is not spontaneously enabled

I am wondering if there is any way to fix this so that MailGuard is not turned off all the time?

Or, is it possible to do authorization via steam-session, since I get RefreshToken after registering an account?

Here's an example of Steam's response after registering:
 

{"bSuccess":true,"bInSteamClient":false,"eresult":1,"refresh_token":"eyAidHlwIjogIkpXVCIsICJhbGciOiAiRWREU0EiIH0..."}

Many thanks!

Hi. I don't know much about the module system, so don't judge harshly. In general, authorization is used to create .maFile, but recently Steam started to automatically enable MailGuard (100% - if the profile is complete). This makes it difficult to create a .maFile, because you have to parse the code from the email. But, at the very first authorization, after registering an account - MailGuard is not needed. 

Now the essence of the question - how can I reuse cookies (and is it possible at all), so that I don't need to authorize again?

Cookies are taken after the first authorization when MailGuard is not yet activated

If you can, the code on NodeJs, I will be very much grateful. Thank you
.