Help:Two-factor authentication

See also: meta:Help:Two-factor authentication

2FA is like a software version of the security token devices used for online banking in some countries.

Two-factor authentication (2FA) is a method of adding additional security to your account. The first "factor" is your usual password that is standard for any account. The second "factor" is a verification code retrieved from an app on a mobile device or computer. 2FA is conceptually similar to a security token device that banks in some countries require for online banking. Other names for 2FA systems include OTP (one-time password) and TOTP (Time-based One-time Password algorithm).

This guide explains how to enable and disable 2FA on Wikipedia for your account. This guide is about the TOTP method, see notes about WebAuthn below.

If you decide to enable 2FA, you may want to enable the option "Send password reset emails only when both email address and username are provided" in the first tab of Special:Preferences.

Securing your account

See also: Wikipedia:User account security

Preferences with button to enable 2FA

It is extremely important for administrators and editors with advanced permissions to keep their account secure. A number of Wikipedia administrators (including the co-founder, Jimbo Wales) have had their accounts compromised, which were then used to vandalise the encyclopedia. As well as causing widespread disruption, the affected administrators' accounts were locked until it was beyond doubt they had regained control.

Any editor can improve their account security by using 2FA. This practice is recommended for editors with advanced permissions, highly recommended for administrators, and required for interface administrators, among others.

Before enabling 2FA, please ensure that you have a strong password that is exclusively used for Wikipedia. Consider using a password manager to generate strong, unique passwords for each of your online accounts.

Accessing 2FA

Main article: m:Help:Two-factor authentication § Accounts affected

On the English Wikipedia, the following groups automatically have access to 2FA:

• Administrators
• Bureaucrats
• Checkusers
• Edit filter managers
• Interface administrators
• Oversighters
• Template editors

If you are not in one of these groups, you need to submit a request at m:Steward requests/Global permissions#Requests for 2 Factor Auth tester permissions to obtain access to 2FA (see request examples), explicitly mentioning that you have read Help:Two-factor authentication on Meta (which is not the page you're reading now). Most users need to request access before they can use 2FA.

Users with advanced rights on other projects, including test wikis hosted by Wikimedia, can also enable 2FA from those projects.

Checking whether 2FA is enabled

To determine whether your account has 2FA enabled, go to Special:Preferences. Under "User profile", check the entry for "Two-factor authentication", which should be between "Global account" and "Global preferences":

• If the entry says "TOTP (one-time token)", 2FA is currently enabled on your account.
• If the entry says "None enabled", 2FA is currently disabled on your account.
• If there is no entry for "Two-factor authentication", your account currently doesn't have access to 2FA, and you'll need to request access at m:Steward requests/Global permissions#Requests for 2 Factor Auth tester permissions before you can enable 2FA.

Enabling 2FA on smartphones and tablet computers

Scanning a QR code with a smartphone's camera

Aegis app

If you have a smartphone or tablet computer with Android or iOS, a mobile app is the most secure and the easiest way to use 2FA. If you don't have a mobile device or if you want to use a Windows tablet, see "Enabling 2FA on desktop and laptop computers".

1. Download a 2FA app onto your mobile device. Some options include:
   • Aegis (Android): free and open-source
     • Android: Download from Google Play or F-Droid
   • AndOTP (Android): free and open-source (development discontinued)
     • Android: Download from Google Play
   • Authenticator (iOS): free and open-source
     • iOS: Download from the App Store
   • FreeOTP (Android, iOS): free and open-source
     • Android: Download from Google Play or F-Droid
     • iOS: Download from the App Store
   • Google Authenticator
     • Android: Download from Google Play
     • iOS: Download from the App Store
   • Microsoft Authenticator
     • Android: Download from Google Play
     • iOS: Download from the App Store
   • Numberstation
     • True Linux on mobile (Mobian, Ubuntu Touch, and similar OSes, but not Android): Install through your package manager, either in the command terminal, or via AppStream (if you have it installed) with the button here.

1. Go to Special:Manage Two-factor authentication. Click "Enable" next to "TOTP (one-time token)", and log in with your username and password.
2. The recommended authentication method is to scan a QR code in the app. In "Step 2" of the setup page, there is a box with a pattern which you have to point your device's camera toward. (Your device might ask you for permission to use the camera first.)
   • If you can't scan the QR code, you can enter the "Two-factor authentication secret key" from "Step 2" of the setup page into the app, which gives you the same result.
3. Go back to the 2FA enrollment page. Write down the scratch codes from "Step 3" and keep them in a secure location.
4. Type the 6-digit verification code from your app into the 2FA enrollment page under "Step 4".

That's it, you're all set up. Now, read "Scratch codes".

Enabling 2FA on desktop and laptop computers

You can use apps like WinAuth, Authenticator, and KeeWeb to handle 2FA tokens on many computers. This is the recommended way to use 2FA if you don't have a smartphone or tablet computer. Certain laptops (like Chromebooks) may need to use the "tablet" section above.

If you currently use a password manager, check whether it supports 2FA. (Your password manager may also refer to 2FA as OTP or TOTP.) Using your current password manager for 2FA is easier than setting up a new 2FA app.

Note: If you normally edit with your desktop computer, using a desktop 2FA app is slightly less secure than using a mobile 2FA app, as someone with access to both your computer and your password would still be able to log in to your account.

WinAuth (Windows)

WinAuth 2FA app

WinAuth is the recommended 2FA app for Windows users. It is free and open-source.

1. Download WinAuth onto your Windows PC.
2. Go to Special:Manage Two-factor authentication. Click "Enable" next to "TOTP (one-time token)", and log in with your username and password.
3. Click the "Add" button at the bottom-left of Authenticator. Select "Authenticator".
4. Type "Wikipedia" and your account name (e.g. "Wikipedia – Example") into the "Name" field.
5. Copy the "Two-factor authentication secret key" from "Step 2" of the setup page and paste it into the "Secret Code" field.
6. Leave the next option set to "Time-based".
7. Click "Verify authenticator" and then click "OK".
8. Optionally set a password for WinAuth. Click "OK".
9. Go back to the 2FA enrollment page. Write down the scratch codes from "Step 3" and keep them in a secure location.
10. Type the 6-digit verification code from WinAuth into the 2FA enrollment page under "Step 4". (Click the refresh button in WinAuth to generate another code.)

That's it, you're all set up. Now, read "Scratch codes".

Authenticator (Linux)

Authenticator 2FA app

Authenticator is the recommended 2FA app for Linux users. It is free and open-source.

1. Download Authenticator onto your Linux computer. (Authenticator requires Flatpak, which is available on all Linux distributions, including Ubuntu.)
2. Go to Special:Manage Two-factor authentication. Click "Enable", and log in with your username and password.
3. Click the + button at the top-left of Authenticator.
4. Add the secret 2FA key to Authenticator using either one of these methods:
   • Use Authenticator to take a screenshot of the QR code:
     1. Click the QR code button at the top-right of Authenticator.
     2. Position your pointer before the top-left corner of the QR code from "Step 2" of the 2FA setup page.
     3. Hold down the mouse button, move the pointer to after the bottom-right of the QR code, and then release the mouse button. The form in Authenticator should be automatically filled in.
   • Manually enter the secret key:
     1. Type "Wikipedia" into the "Provider" field, and your account name into the "Account Name" field.
     2. Copy the "Two-factor authentication secret key" from "Step 2" of the setup page and paste it into the "2FA Token" field.
5. Click "Add" at the top-right of Authenticator.
6. Go back to the 2FA enrollment page. Write down the scratch codes from "Step 3" and keep them in a secure location.
7. Type the 6-digit verification code from Authenticator into the 2FA enrollment page under "Step 4".
8. Click "Submit".

That's it, you're all set up. Now, read "Scratch codes".

KeeWeb (Windows, macOS, Linux, online)

Enabling 2FA with KeeWeb

KeeWeb is a free and open-source password manager that also handles 2FA. The app can be downloaded to your computer or used online without installation. KeeWeb refers to 2FA as one-time passwords (OTP).

1. Download KeeWeb onto your computer, or open KeeWeb's online web app.
2. Go to Special:Manage Two-factor authentication. Click "Enable", and log in with your username and password.
3. In KeeWeb, click "New" (the + icon).
4. Add a new entry: Click the + icon ("Add New") at the top. Then, click "Entry".
5. Give the entry a title (e.g. "Wikipedia").
6. In the right-side pane, click "more...". Then, click "One-time passwords" and click "Enter code manually".
7. Copy the "Two-factor authentication secret key" from "Step 2" of the setup page and paste it into the "otp" field in KeeWeb. Press ↵ Enter on your keyboard.
8. Go back to the 2FA enrollment page. Write down the scratch codes from "Step 3" and keep them in a secure location.
9. In KeeWeb, click on "otp" to copy the 6-digit verification code. Paste the code into the 2FA enrollment page under "Step 4".
10. Back up your 2FA settings:
    • Click on the ⚙️ gear icon ("Settings") at the bottom-right of the KeeWeb window. Click "New" on the left side of the screen.
    • Optionally set a password and a name, and then click "Save to...".
    • Click "File" to save your 2FA settings onto your computer, or choose one of the other options to sync with Dropbox, Google Drive, OneDrive, or WebDAV.

That's it, you're all set up. Now, read "Scratch codes".

Changing your authentication device

For any reason you may want to change your authentication device. This could be to move your authentications to a replacement computer or mobile device (for example if you buy a new smartphone). There is not currently a transfer function, however you may accomplish this by turning off 2FA, and then re-enrolling with your new device.

Scratch codes

Example of scratch codes

When you set up 2FA, you'll be given a number of 16-character scratch codes, each consisting of four alphanumeric blocks. You can use one of the scratch codes if you lose access to your 2FA app (e.g. if your phone or computer gets broken or stolen). You only see these codes while setting up 2FA (and never again), so copy them from your browser and save them offline in a safe place (e.g. on a memory stick or paper printout). If you don't keep these codes and encounter a problem with your 2FA device, you will be locked out of your account.

• Each scratch code can only be used one time, and it takes two of them to turn off 2FA (the first to log in without 2FA, and the second to shut off 2FA after logging in).
• Don't store these only on your smartphone. If it gets lost you'll lose the codes!
• You still need to follow good security practices. Don't use your name, date of birth, or anything that can be guessed in a dictionary attack as a password. Don't write your password down in a place anyone else can see it, and consider whether or not it's a good idea to log in to your Wikipedia account on public terminals at schools, libraries, and airports.

If for some reason you need to use one or more scratch codes or feel that they have been compromised, you should generate a new set at your earliest convenience (especially if you are down to three or fewer remaining).

If you are totally locked out, regaining access to your account will be very difficult and usually involve proving your identity beyond the shadow of a doubt to Wikimedia Trust and Safety via cawikimedia.org. If T&S deny your request, it is impossible to turn 2FA off and you'll have to create a new account.

Generating new scratch codes

To generate a new batch of scratch codes, simply disable and then re-enable two-factor authentication. This will void all of your old scratch codes and create a new batch.

Logging in with 2FA

Web interface

Logging in with 2FA via the web interface

When you log in, after entering your password, you'll be asked for a verification code.

1. Open your 2FA app and you should see a 6-digit verification code.
2. Type the verification code in as is (with no spaces), and you should be logged back in

   Because the verification code is time-based, it may change while you're doing this, in which case you'll have to add the latest code instead. The application will normally indicate when a code is about to expire (e.g. in Google Authenticator, the code's colour changes from blue to red).

If you need to use a scratch code, enter it in place of the verification code. Scratch codes are case-sensitive and need to be entered in all caps. A scratch code will work either with or without the spaces between the clusters of characters.

Mobile app

2FA prompt in the mobile app

For the iOS and Android versions of the mobile app, when prompted for the verification code, you'll need to follow a similar process to the web interface.

If you need to use a scratch code, first choose to use a backup code, and then enter the scratch code. Scratch codes are case-sensitive and must be entered in all caps. The spaces separating the clusters of characters in the scratch code are optional.

API access

• AutoWikiBrowser and Huggle users need to create a bot password after enabling 2FA. Please see Wikipedia:Using AWB with 2FA and mw:Manual:Huggle/Bot passwords for instructions.
• Special client configuration to use the API is needed for two-factor authentication.

Disabling 2FA

Disabling 2FA

If you no longer want to use 2FA, go to Special:Manage Two-factor authentication and you'll be given the option to disable it. You'll need to enter a 6-digit verification code, just as you would when logging in. Alternatively enter one of your 16-character scratch codes. After this, 2FA will be turned off on your account.

To change your 2FA app or device, just disable 2FA and then follow the instructions at "Enabling 2FA on smartphones and tablet computers" or "Enabling 2FA on desktop and laptop computers" to enable it again.

Known issues

Multiple devices

Wikimedia's 2FA system is only designed to be used with one device. If you want to use 2FA on multiple devices, you must register all of your devices at the same time. To add 2FA to an additional device:

1. Have all of your devices on hand.
2. If 2FA is already enabled on your account, disable it.
3. Register all of your devices with the directions at "Enabling 2FA on smartphones and tablet computers" and/or "Enabling 2FA on desktop and laptop computers", but don't enter the 6-digit verification code into the Two-factor authentication page until all of your devices are registered.

To remove 2FA from a device, simply remove the Wikipedia entry from your 2FA app. Do not do this unless you have disabled 2FA entirely (see "Disabling 2FA") or you have access to 2FA for Wikipedia on another device.

Clock drift

If your 2FA device's clock becomes too inaccurate, it will generate the wrong verification codes and you will not be able to log in. To prevent this, the 2FA device's clock should be kept reasonably accurate. Most smartphones and computers keep the clock in sync when they are connected to the Internet, and you will most likely not have to do anything as long as your device is online.

WebAuthn

WebAuthn is another two-factor mechanism that may be enabled; it is currently not recommended as there is no recovery mechanism for lost keys and it has less support from community volunteers. If you use WebAuthn and have a technical issue, you may lose access to your account forever.

WebAuthn may require you to logon on the same project that you have set it up on, when logging on in the future. For example, if you enroll WebAuthn here on the English Wikipedia, then log out, you will not be able to log on at the Spanish Wikipedia - you would need to log on here first. This is a known issue.

WebAuthn is not currently supported on the mobile apps (see T230043).

More help

• Ask the computing reference desk or contact an editor willing to assist with 2FA if you need more help, or if you have any questions.
• If you find something on this page to be incomplete or unclear, please raise the issue on the talk page and someone will fix it.
• Email info-enwikimedia.org – your ticket will be dealt with by one of the OTRS technical agents.
• Discuss technical issues at the Technical village pump.
• Join #wikipedia-en ^connect and/or #wikipedia-tech ^connect.
• See also Metawiki help page for Meta-Wiki's overview of 2FA.
• There are many OTP clients available (c.f. comparison of OTP applications, see the publisher for application specific assistance.