-
-
Notifications
You must be signed in to change notification settings - Fork 1k
Two factor authentication fr FR
Steam includes two-factor authentication system that requires extra details for various account-related activity. Vous pouvez en apprendre plus par rapport à ce système ici et ici. This page considers that 2FA system as well as our solution that integrates with it, called ASF 2FA.
Regardless if you use ASF 2FA or not, ASF includes proper logic and is fully aware of accounts protected by 2FA on Steam. It will ask you for required details when they're needed (such as during logging in). While you can manually provide that information, certain ASF functionalities (such as MatchActively
) require ASF 2FA to be operative on your bot account, which can automatically respond to 2FA prompts, automatically, whenever required by ASF.
ASF 2FA is a built-in module responsible for providing 2FA features to the ASF process, such as generating tokens and accepting confirmations. It can work either in standalone mode, or by duplicating your existing authenticator details (so that you can use your current authenticator and ASF 2FA at the same time).
You can verify whether your bot account is using ASF 2FA already by executing 2fa
commands. Without setting up ASF 2FA, all standard 2fa
commands will be non-operative, which means that your bot is unavailable for advanced ASF features that require the module to be operative.
There are a lot of ways to make ASF 2FA operative, here we include our recommendations based on your current situation:
- If you're already using unofficial third-party app that allows you to extract 2FA details with ease, just import those to ASF.
- If you're using official app and you don't mind resetting your 2FA credentials, the best way is to disable 2FA, then create new 2FA credentials by using joint authenticator, which will allow you to use official app and ASF 2FA. This method doesn't require root or advanced knowledge, barely following instructions written here, and is arguably superior for this scenario.
- If you're using official app and don't want to recreate your 2FA credentials, your options are very limited, typically you'll need root and extra fiddling around to import those details, and even with that it might be impossible.
- If you're not using 2FA yet and don't care, we recommend you to use ASF 2FA with standalone authenticator or joint authenticator with official app (same as above).
Below we discuss all possible options and known to us methods.
ASF comes with an official MobileAuthenticator
plugin that further extends ASF 2FA, allowing you to link a completely new 2FA authenticator. This can be useful in case you're unable or unwilling to use other tools and do not mind ASF 2FA becoming your main (and maybe only) authenticator. Creation process is also used in joint-authenticator method, naturally in this scenario your authenticator can co-exist in two places at once - both will generate the same codes and both will be able to confirm the same confirmations.
No matter if you plan to use ASF as the standalone or joint authenticator, you need to do those initialization steps:
- Create an ASF bot for the target account, start it, and log in, which you probably already did.
- Assign a working and operational phone number to the account here to be used by the bot. This will allow you to receive SMS code and allow recovery if needed. This step is not mandatory in all scenarios, however, we recommend it unless you know what you're doing.
- Ensure you're not using 2FA yet for your account, if you do, disable it first. This will put your account on temporary trade-hold, there is no way around it, only import process can skip it.
- Execute the
2fainit [Bot]
command, replacing[Bot]
with your bot's name.
Assuming you got a successful reply, the following two things have happened:
- A new
<Bot>.maFile.PENDING
file was generated by ASF in yourconfig
directory. - SMS was sent from Steam to the phone number you have assigned for the account above. If you didn't set a phone number, then an email was sent instead to the account e-mail address.
The authenticator details are not operational yet, however, you can review the generated file if you'd like to. If you want to be double safe, you can, for example, already write down the revocation code. The next steps will depend on your selected scenario.
If you want to use ASF as your main (or even only) authenticator, now you need to do the final finalization step:
- Execute the
2fafinalize [Bot] <ActivationCode>
command, replacing[Bot]
with your bot's name and<ActivationCode>
with the code you've received through SMS or e-mail in the previous step.
If you want to have the same authenticator in both ASF and the official Steam mobile app, now you need to do the next, more tricky steps:
- Ignore the SMS or e-mail code that you've received in the previous step.
- Install the Steam mobile app if it's not installed yet, and open it. Navigate to the Steam Guard tab and add a new authenticator by following the app's instructions.
- After your authenticator in the mobile app is added and working, return to ASF. Now, instead of finalization, we only need to inform ASF that mobile app already activated our previously-generated details:
- Wait until the next 2FA code is shown in the Steam mobile app, and use the command
2fafinalized [Bot] <2FACodeFromApp>
replacing[Bot]
with your bot's name and<2FACodeFromApp>
with the code you currently see in the Steam mobile app. If the code generated by ASF and the code you provided are equal, ASF will assume that an authenticator was added correctly and proceed with importing your newly created authenticator. - We strongly recommend to do the above in order to ensure that your credentials are valid. However, if you don't want to (or can't) check if codes are the same and you know what you're doing, you can instead use the command
2fafinalizedforce [Bot]
, replacing[Bot]
with your bot's name. ASF will assume that the authenticator was added correctly and proceed with importing your newly created authenticator.
Assuming everything worked properly, the previously generated <Bot>.maFile.PENDING
file was renamed to <Bot>.maFile.NEW
. This indicates that your 2FA credentials are now valid and active. We recommend that you create a copy of that file and keep it in a secure and safe location. In addition to that, if you've decided to use standalone authenticator, then we recommend you to open the file in your editor of choice and write down the revocation_code
, which will allow you to, as the name implies, revoke the authenticator in case you lose it. In joint-authenticator method, you should've already done that in Steam mobile app, but feel free to do the same in case you need to.
In regards to technical details, the generated maFile
includes all details that we've received from the Steam server during linking the authenticator, and in addition to that, the device_id
field, which may be needed for other (third-party) authenticators, if you ever decide to import that maFile
into them.
ASF automatically imports your authenticator once the procedure is done, and therefore 2fa
and other related commands should now be operational for the bot account you linked the authenticator to. We recommend you to verify that.
Import process requires already linked and operational authenticator that is supported by ASF. We have instructions for a few different official and unofficial sources of 2FA, on top of manual method which allows you to provide required credentials yourself. Please note that those instructions should be used only if you're already using given solution - since process here involves third-party apps and tools, we do not recommend using them, and we're mentioning it exclusively for people that already decided to use them and would like to import generated details into ASF 2FA.
Tous les guides suivants exigent que vous ayez déjà un authentificateur ** fonctionnel et opérationnel </ 0> utilisé avec un outil / ou une application tiers. ASF 2FA ne fonctionnera pas correctement si vous importez des données non valides. Assurez-vous donc que votre authentificateur fonctionne correctement avant de tenter de l'importer. Cela inclut de tester et de vérifier que les fonctions suivantes de l'authentificateur fonctionnent correctement:
- Vous pouvez générer des jetons et ces jetons sont acceptés par le réseau Steam
- Vous pouvez récupérer les confirmations et elles arrivent sur votre authentificateur mobile
- You can react to those confirmations, and they're properly recognized by Steam network as confirmed/rejected
Ensure that your authenticator works by checking if above actions work - if they don't, then they won't work in ASF either.
In general for importing authenticator from your Android phone you will need root access. The below instructions require from you fairly decent knowledge in Android modding world, we're definitely not going to explain every step here, visit XDA and other resources for additional information/help with below.
Assuming you have official Steam app working and operational (requires rooting your device):
- Install Magisk and enable Zygisk in the settings.
- Install LSPosed (for Zygisk) and ensure it works.
- Install SteamGuardExtractor LSPosed module and enable it in LSPosed settings.
- Force kill Steam app, then open it, a window with extracted details should pop up, click copy.
Now that you've successfully extracted required details, disable the module to prevent the window from showing each time, then copy value of shared_secret
and identity_secret
of the account that you intend to add to ASF 2FA, into a new text file with below structure:
{
"shared_secret": "STRING",
"identity_secret": "STRING"
}
Replace each STRING
value with appropriate private key from extracted details. Once you do that, rename the file to BotName.maFile
, where BotName
is the name of your bot you're adding ASF 2FA to, and put it in ASF's config
directory if you haven't yet.
Launch ASF, which should notice your file and import it. Assuming that you've imported the correct file with valid secrets, everything should work properly, which you can verify by using 2fa
commands. If you made a mistake, you can always remove Bot.db
and start over if needed.
Si vous avez votre authentificateur SDA déjà en fonctionnement, vous devriez remarquer que le fichier steamID.maFile
est disponible dans le dossier maFiles
. Make sure that maFile
is in unencrypted form, as ASF can't decrypt SDA files - unencrypted file content should start with {
and end with }
character. If needed, you can remove the encryption from SDA settings first, and enable it again when you're done. Once the file is in unencrypted form, copy it to config
directory of ASF.
You can now rename steamID.maFile
to BotName.maFile
in ASF config directory, where BotName
is the name of your bot you're adding ASF 2FA to. Sinon, vous pouvez le laisser tel quel, ASF le sélectionnera automatiquement après vous être connecté. Renaming the file helps ASF by making it possible to use ASF 2FA before logging in, if you don't do that, then the file can be picked only after ASF successfully logs in (as ASF doesn't know steamID
of your account before in fact logging in).
Launch ASF, which should notice your file and import it. Assuming that you've imported the correct file with valid secrets, everything should work properly, which you can verify by using 2fa
commands. If you made a mistake, you can always remove Bot.db
and start over if needed.
Une fois que votre fichier est sur votre PC, saisissez-le sous la forme `BotName.maFile</ 0> dans le répertoire de configuration ASF, où BotName</ 0> correspond au nom de votre bot auquel vous ajoutez ASF 2FA. Si vous indiquez un nom incorrect, il ne sera pas sélectionné par ASF.
Maintenant, lancez WinAuth comme d’habitude. Faites un clic droit sur l'icône Steam et sélectionnez "Afficher le code SteamGuard et le code de récupération". Puis cochez "Autoriser la copie". Vous devez connaître la structure JSON que vous connaissez bien en bas de la fenêtre, en commençant par { 0>. Copiez le texte entier dans un fichier
BotName.maFile 0> créé par vous même à l'étape précédente.
Launch ASF, which should notice your file and import it. Assuming that you've imported the correct file with valid secrets, everything should work properly, which you can verify by using 2fa` commands. If you made a mistake, you can always remove `Bot.db` and start over if needed.
Si vous êtes un utilisateur expérimenté, vous pouvez également générer manuellement le fichier maFile. Cela peut être utilisé dans le cas où vous vouliez importer un authentificateur depuis d'autres sources que celles que nous avons décrites ci-dessus. Il devrait avoir une structure JSON valide de ce type :
{
"shared_secret": "STRING",
"identity_secret": "STRING"
}
Les données d'authentificateur standard comportent plus de champs. ASF les ignore totalement lors de l'importation, car elles ne sont pas nécessaires. You don't need to remove them - ASF only requires valid JSON with 2 mandatory fields described above, and will ignore additional fields (if any). Of course, you need to replace STRING
placeholder in the example above with valid values for your account. Each STRING
should be base64-encoded representation of bytes the appropriate private key is made of.
Si ASF 2FA est disponible, ASF l'utilisera pour la confirmation automatique des transactions en cours d'envoi / acceptées par ASF. Il sera également capable de générer automatiquement des jetons 2FA au besoin, par exemple pour se connecter. De plus, ASF 2FA active également les commandes ` 2fa </ 0> que vous pouvez utiliser.
Vous aurez besoin du jeton 2FA pour accéder à un compte protégé par 2FA, qui comprend également chaque compte ASF 2FA. If you've decided to use standalone authenticator, then you should use 2fa ` command to generate temporary token for given bot instances. In all other scenarios, we recommend to use original authenticator that you've used, although you can use the command as well if it's more convenient to you.
Oui, votre authentificateur d'origine reste fonctionnel et vous pouvez l'utiliser avec ASF 2FA. Keep in mind however that if you invalidate it through any method, then linked ASF 2FA credentials will also no longer be valid.
Arrêtez simplement ASF et supprimez le fichier BotName.db</ 0> du bot associé à ASF 2FA que vous souhaitez supprimer. This option will remove associated imported 2FA with ASF, but will NOT invalidate (unlink) your authenticator. If you instead want to invalidate your authenticator, apart from removing it from ASF (firstly), you should unlink it in original authenticator of your choice. If you can't do that for some reason, for example because you're using ASF 2FA in standalone mode, then use revocation code that you've received during setup, on the Steam website. It's not possible to invalidate your authenticator through ASF.
I linked authenticator in third-party app, then imported to ASF. Can I now link it again on my phone?
Non Doing so will invalidate the previously imported credentials and your ASF 2FA will stop functioning (by generating codes no longer being accepted by Steam). Firstly decide where you want to have your original or third-party authenticator located, then import it as ASF 2FA.
Oui 0>, à plusieurs niveaux. Le premier et le plus important - utiliser ASF 2FA de manière significative 0> augmente votre sécurité, car le module ASF 2FA garantit qu'ASF n'acceptera automatiquement que ses propres confirmations. Ainsi, même si l'attaquant demande une transaction, ASF 2FA n'acceptera pas un tel échange, car il n'a pas été généré par ASF. In addition to security part, using ASF 2FA also brings performance/optimization benefits, as ASF 2FA fetches and accepts confirmations immediately after they're generated, and only then, as opposed to inefficient polling for confirmations each X minutes which is achieved by other solutions. There is no reason to use third-party authenticator over ASF 2FA, if you plan on automating confirmations generated by ASF - that's exactly what ASF 2FA is for, and using it does not conflict with you confirming everything else in authenticator of your choice. We strongly recommend to use ASF 2FA for entire ASF activity.
- 🏡 Accueil
- 🔧 Configuration
- 💬 FAQ
- Mise en place (commencez ici)
- 👥 Collecte de cartes en arrière plan
- 📢 Commandes
- 🛠️ Compatibilité
- 🧩 ItemsMatcherPlugin
- 📋 Gestion
- ⏱️ Performance
- 📡 Communication à distance
- 👪 Partage familial Steam
- 🔄 Échange
- ⌨️ Arguments de ligne de commande
- 🚧 Fonctions Obsolètes
- 🐳 Docker
- 🤔 FAQ Supplémentaires
- 🚀 Configuration à hautes performances
- 🔗 IPC
- 🌐 Localisation
- 📝 Journalisation
- 💾 Configuration avec peu de mémoire
- 🕵🏼♂️ MonitoringPlugin
- 🔌 Extensions
- 🔐 Sécurité
- 🧩 SteamTokenDumperPlugin
- 📦 Tierce-partie
- 📵 Authentification à deux facteurs