Ajuda:Autenticação de dois fatores

From Meta, a Wikimedia project coordination wiki
Jump to navigation Jump to search
This page is a translated version of the page Help:Two-factor authentication and the translation is 10% complete.

Outdated translations are marked like this.
Other languages:
Bahasa Indonesia • ‎Deutsch • ‎English • ‎Esperanto • ‎Nederlands • ‎Tiếng Việt • ‎Türkçe • ‎asturianu • ‎dansk • ‎español • ‎français • ‎galego • ‎italiano • ‎norsk bokmål • ‎polski • ‎português • ‎português do Brasil • ‎română • ‎беларуская (тарашкевіца)‎ • ‎русский • ‎سنڌي • ‎فارسی • ‎नेपाली • ‎हिन्दी • ‎বাংলা • ‎മലയാളം • ‎ไทย • ‎ქართული • ‎中文 • ‎日本語
Páginas de ajuda Ajuda sobre a autenticação de dois fatores

Esta página explica a autenticação de dois fatores nas wikis da Fundação Wikimedia. Se deseja consultar a documentação da extensão que ativa este recurso, acesse: mw:Wikimedia Security Team/Two-factor Authentication for CentralAuth wikis.

A implementação da autenticação de dois fatores (2FA) da Wikimedia é uma forma de aumentar a segurança da sua conta. Se você ativar a autenticação de dois fatores, todas as vezes em que você efetuar login na sua conta, ser-lhe-á solicitado um número de seis dígitos adicionalmente à sua palavra-chave. Este número de seis dígitos pode ser fornecido por um aplicativo em seu smartphone ou outro dispositivo de autenticação. Para efetuar o login, você deverá saber a sua palavra-chave e ter o seu dispositivo de autenticação disponível para gerar o código.

Accounts affected

Two-factor authentication on Wikimedia is currently experimental and optional. Enrollment requires (oathauth-enable) access, currently in production testing with administrators (and users with admin-like permissions like interface editors), bureaucrats, checkusers, oversighters, stewards, edit filter managers and the OATH-testers global group.

Wikitech LDAP accounts are also eligible.

Mandatory use user groups

Ativação

Para configurar a autenticação de dois fatores:

  • Have (oathauth-enable) access
  • Have or install a Time-based One-time Password Algorithm (TOTP) client. For most users, this will be a phone or tablet application. Commonly recommended apps include:
    • Open-source: FreeOTP (Android, iOS), andOTP (Android), Authenticator (iOS)
    • Closed-source: Authy (Android, iOS, MacOS, Windows, Chrome/Chromium-extension), Google Authenticator (Android iOS)
    • other clients compared at English Wikipedia
    • You can also use a desktop client such as the OATH Toolkit (Linux, macOS via Homebrew), or WinAuth (Windows). Keep in mind that if you log in from the computer used to generate TOTP codes, this approach does not protect your account if an attacker gains access to your computer.
    • Password managers such as 1Password, LastPass, and KeePass also tend to support/have plugins to support TOTP. This bears the same limitations as the above, but may be worth looking into if you already use one for other things.
Overview of preferences section to enable two-factor authentication.
  • Go to Special:OATH on the project you hold one of the above rights on (this link is also available from your preferences). (For most users, this will not be here on the meta-wiki.)
  • Special:OATH presents you with a QR code containing the Two-factor account name and Two-factor secret key. This is needed to pair your client with the server.
  • Scan the QR code with, or enter the two-factor account name and key into, your TOTP client.
  • Enter the authentication code from your TOTP client into the OATH screen to complete the enrollment.
Warning WARNING: You will also be presented with a series of 10 one-time scratch codes. You should safely store a copy of these codes. If you lose or have a problem with your TOTP client, you will be locked out of your account unless you have access to these codes.

Logging in

Login screen
  • Provide your username and password, and submit as before.
  • Enter in a one-time six digit authentication code as provided by the TOTP client. Note: This code changes about every thirty seconds.

Mantenha-me logado

If you choose this option when logging in, you normally will not need to enter an authentication code when using the same browser. Actions such as logging out or clearing the browser cache will require a code on your next login.

Some security sensitive actions, such as changing your email address or password, may require you to re-authenticate with a code even if you chose the keep-me-logged-in option.

API access

Two-factor authentication is not utilized when using OAuth or bot passwords to log in via the API.

You may use OAuth or bot passwords to restrict API sessions to specific actions, while still using two-factor authentication to protect your full access. Please note, OAuth and bot passwords can not be used to log on interactively to the website, only to the API.

For example, tools like AutoWikiBrowser (AWB) do not yet support two-factor authentication, but can use bot passwords.

Disabling two-factor authentication

Unenrolling
Warning

If you already have 2FA enabled, removing the permission that allows you to enroll 2FA WILL NOT disable 2FA. You need to follow the process below to disable it.

  • On the disable two-factor authentication page, use your authentication device to generate a code to complete the process.

Scratch codes

OATH example scratch codes

When enrolling in two-factor authentication, you will be provided with a list of ten one-time scratch codes. Please print those codes and store them in a safe place, as you may need to use them in case you lose access to your 2FA device. It is important to note that each of these codes is single use; it may only ever be used once and then expires. After using one, you can scratch it through with a pen or otherwise mark that the code has been used. To generate a new set of codes, you will need to disable and re-enable two-factor authentication.

Importante: A desativação sem um dispositivo de autenticação pode requerer o uso de dois códigos de recuperação: uma para efetuar o login na conta, e outro para desativar o recurso. Toda vez que você precisar usar qualquer dos seus códigos de recuperação, é extremamente recomendado que desative e reative o recurso assim que possível, de modo a gerar um novo conjunto de códigos.

This may require two scratch codes: one to log in, and another to disable. Should you ever need to use any of your scratch codes, it is advisable to disable and re-enable to generate a fresh set of codes as soon as possible.

Recuperação a partir de um dispositivo de autenticação perdido ou danificado

Você precisará acessar os códigos de recuperação que lhe foram fornecidos ao ativar a autenticação de dois fatores de modo a desativá-la. Para tanto, você precisará utilizar até dois códigos de recuperação para fazer isso:

If you have an existing 2FA device which has simply stopped generating the correct codes, check that its clock is reasonably accurate. Time-based OTP on our wikis has been known to fail with 2 minutes difference.

You will need access to the scratch codes that you were provided when enrolling in order to un-enroll from two-factor authentication. It will require you to use up to two scratch codes to accomplish this:

  • You need to be logged in. If you are not already logged in, this will require use of a scratch code.
  • Visit Special:OATH and use a different scratch code to disable two-factor authentication.

If you don't have enough scratch codes, you may contact Trust and Safety at ca@wikimedia.org to request removal of 2FA from your account (please send an email using your registered email address of your wiki account). You should also create a task on Phabricator if you still have access to it. Please note, 2FA removal by staff is not always granted.

Ver também