Taimako: Tantance al’amura-biyu

From Meta, a Wikimedia project coordination wiki
This page is a translated version of the page Help:Two-factor authentication and the translation is 36% complete.
Wannan shafin yana bayanin tantacewar bayanai-biyu a shafukan Wikimidiya wikis. Kuna iya kara karantawa documentation of the extension wanda ke karin bayani game da wannan aiki.

Kaddamar da tantance bayanai biyu da gidauniyar Wikimidiya ta yi (2FA) hanya ce ta karfafa tsari ga asusu. Idan ka kaddamar da tantance bayanai-biyu, za’a rika tambayar ka lambobin sirri na lokaci daya-guda shida tare da lambobin ka na tsaro. Wani app ne ke samar da waannan lambobin sirri a cikin wayar ku na hannu ko kuma wasu nau’rar tantancewa. Don samun damar shiga, dole ka san lambobinka na sirri kuma ya zamana kana da nau’rar tantancewa wajen kikirar lambobin ka na sirri.

Asusun da suka shafa

Tantance bayanai-biyu a Wikimidiya a yanzu yana kan gwaji ne kuma sai idan mutum yana so (tare da wasu ‘yan iyakoki). Farawa na bukatar bayar da damar isa ga -$oathauth,a yanzu suna kan gwaji a wajen adiministoci (da editoci masu iko irin na adimin kamar interface editors), bureaucrats, checkusers, oversighters, stewards, edit filter managers and the OATH-testers global group.

Dukkannin asusun Wikitech LDAP (wanda kuma aka sani da asusun masu kirkira) suma suna da dama. Wadannan asusun basu cikin bangaren Single Unified Login.

Tilascin amfani na kungiyar editoci

Kunna tantance bayanai biyu

  • Samu damar isa ga kunna-$oathauth (akan tsari, adiministoci, bureaucrats, suppressors, masu duba editoci da kuma kungiyar editoci na musamman)
  • Samu ko shigar da abokin ciniki Algorithm na tushen lokaci guda ɗaya (TOTP). Ga yawancin masu amfani, wannan zai zama aikace-aikacen waya ko kwamfutar hannu. Abubuwan da aka fi ba da shawarar sun haɗa da:
    • Open-source: FreeOTP (Android, iOS), andOTP (Android), Authenticator (iOS), Authenticator.cc (Chrome, Firefox & Edge), Passman (NextCloud), KeePassXC (Linux, macOS, Windows)
    • Rufe tushe: Authy (Android, iOS, macOS, Windows), Google Authenticator (Android iOS)
    • General comparison of many common OTP applications which could be used as TOTP client for 2FA (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, Bitwarden, 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.

Shiga ciki

allon shiga
  • 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.

Ci gaba da shiga

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 browser cookies 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.

Samun damar API

Ba a amfani da ingantaccen abu biyu lokacin amfani da OAuth ko kalmomin shiga bot don shiga ta 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. You may find further information on how to configure this.

Disabling two-factor authentication

  • Go to Special:OATH or preferences. If you are no longer in groups that are permitted to enroll, you can still disable via Special:OATH.
  • On the disable two-factor authentication page, use your authentication device to generate a code to complete the process.

Recovery codes

OATH example recovery codes

When enrolling in two-factor authentication, you will be provided with a list of ten one-time recovery 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.

Disabling two-factor authentication without an authentication device

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

Recovering from a lost or broken authentication device

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 recovery 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 recovery codes to accomplish this:

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

If you don't have enough recovery codes, you may contact Trust and Safety at ca(_AT_)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.

See wikitech:Password and 2FA reset#For users for instructions on requesting 2FA removal for your Developer account.

Web Authentication Method

Please note, most of the directions on this page are specific to the TOTP method. The WebAuthn method is more experimental and currently has no recovery options (cf. related developer task).

WebAuthn has a known issue that you must make future logons on the same project that you initiate it from (tracking task).

Duba nan