Title: To-faktor
Author: WordPress.org
Published: <strong>10. august, 2015</strong>
Last modified: 27. mars, 2026

---

Søk i utvidelser

![](https://ps.w.org/two-factor/assets/banner-772x250.png?rev=2125197)

![](https://ps.w.org/two-factor/assets/icon.svg?rev=2887448)

# To-faktor

 Av [WordPress.org](https://profiles.wordpress.org/wordpressdotorg/)

[Last ned](https://downloads.wordpress.org/plugin/two-factor.0.16.0.zip)

[Forhåndsvisning](https://nb.wordpress.org/plugins/two-factor/?preview=1)

 * [Detaljer](https://nb.wordpress.org/plugins/two-factor/#description)
 * [Omtaler](https://nb.wordpress.org/plugins/two-factor/#reviews)
 * [Utvikling](https://nb.wordpress.org/plugins/two-factor/#developers)

 [Brukerstøtte](https://wordpress.org/support/plugin/two-factor/)

## Beskrivelse

Utvidelsen To-faktor legger et ekstra lag sikkerhet til WordPress-innloggingen din
ved å kreve at brukere oppgir en ekstra autentisering i tillegg til passordet. Dette
hjelper til med å beskytte mot uautorisert tilgang også om passord blir røpet.

### Oppsettsinstruksjoner

**Viktig**: Hver bruker må selv konfigurere sine innstillinger for to-faktor autentisering.

### For individuelle brukere

 1. **Navigate to your profile**: Go to «Users»  «Your Profile» in the WordPress admin
 2. **Find Two-Factor Options**: Scroll down to the «Two-Factor Options» section
 3. **Choose your methods**: Enable one or more authentication providers (noting a 
    site admin may have hidden one or more so what is available could vary):
 4.  * **Authenticator App (TOTP)** – Use apps like Google Authenticator, Authy, or
       1Password
     * **E-postkoder** – Receive one-time codes via email
     * **Backup Codes** – Generate one-time backup codes for emergencies
     * **Dummy Method** – For testing purposes only (requires WP_DEBUG)
 5. **Configure each method**: Follow the setup instructions for each enabled provider
 6. **Set primary method**: Choose which method to use as your default authentication
 7. **Save changes**: Click «Update Profile» to save your settings

### For nettstedsadministratorer

 * **Plugin settings**: The plugin provides a settings page under «Settings  Two-
   Factor» to configure which providers should be disabled site-wide.
 * **User management**: Administrators can configure 2FA for other users by editing
   their profiles
 * **Security recommendations**: Encourage users to enable backup methods to prevent
   account lockouts

### Tilgjengelige autentiseringsmetoder

### Autentiseringsapp (TOTP) – anbefalt

 * **Security**: High – Time-based one-time passwords
 * **Setup**: Scan QR code with authenticator app
 * **Compatibility**: Works with Google Authenticator, Authy, 1Password, and other
   TOTP apps
 * **Best for**: Most users, provides excellent security with good usability

### Reserverkoder – anbefalt

 * **Security**: Medium – One-time use codes
 * **Setup**: Generate 10 backup codes for emergency access
 * **Compatibility**: Works everywhere, no special hardware needed
 * **Best for**: Emergency access when other methods are unavailable

### E-postkoder

 * **Security**: Medium – One-time codes sent via email
 * **Setup**: Automatic – uses your WordPress email address
 * **Compatibility**: Works with any email-capable device
 * **Best for**: Users who prefer email-based authentication

### FIDO U2F Security Keys

 * Deprecated and removed due to loss of browser support.

### Dummy Method

 * **Security**: None – Always succeeds
 * **Setup**: Only available when WP_DEBUG is enabled
 * **Purpose**: Testing and development only
 * **Best for**: Developers testing the plugin

### Viktige merknader

### HTTPS Requirement

 * All methods work on both HTTP and HTTPS sites

### Browser Compatibility

 * TOTP and email methods work on all devices and browsers

### Account Recovery

 * Always enable backup codes to prevent being locked out of your account
 * If you lose access to all authentication methods, contact your site administrator

### Security Best Practices

 * Bruk flere autentiseringsmetoder når mulig.
 * Ha reservekodene på et sikkert sted
 * Regularly review and update your authentication settings

For more information about two-factor authentication in WordPress, see the [WordPress Advanced Administration Security Guide](https://developer.wordpress.org/advanced-administration/security/mfa/).

For mer historikk, se [dette innlegget](https://georgestephanis.wordpress.com/2013/08/14/two-cents-on-two-factor/).

#### Handlinger og filtre

Her er en liste over handlings- og filter-knagger som tilbys i utvidelsen:

 * Filteret `two_factor_providers` overstyrer de tilgjengelige tofaktorleverandørene
   som e-post- og tidsbaserte engangspassord. Rekkeverdiene er PHP-klassnavn for
   tofaktor-leverandørene.
 * Filteret `two_factor_providers_for_user` overstyrer de tilgjengelige tofaktorleverandørene
   for en bestemt bruker. Rekkeverdiene er instanser av leverandørklassser, og brukerobjektet`
   WP_User` er tilgjengelig som det andre argumentet.
 * Filteret `two_factor_enabled_providers_for_user` overstyrer listen over to-faktor-
   leverandører slått på for en bruker. Første argument er en rekke påslåtte leverandør-
   klassenavn som verdier, det andre argumentet er bruker-id-en.
 * Handlingen `two_factor_user_authenticated`, som mottar den innloggede `WP_User`-
   objektet som det første argumentet, for å fastsette den innloggede brukeren like
   etter autentiseringen.
 * `two_factor_user_api_login_enable`-filteret begrenser autentiseringen for REST
   API og XML-RPC til kun applikasjons passord. Gir bruker-ID som det andre argumentet.
 * Filteret `two_factor_token_ttl` overstyrer det tidsintervallet i sekunder som
   et e-postadgangstegn tas i betraktning etter generering. Aksepterer tiden i sekunder
   som det første argumentet og id-en til objektet `WP_User` som skal autentiseres.
 * Filteret `two_factor_email_token_length` overstyrer den standard 8-tegnsgrensen
   for adgangstegn via e-post.
 * Filteret `two_factor_backup_code_length` overstyrer den standard 8-tegnsgrensen
   for reservekoder. Leverer `WP_User` for den tilknyttede brukeren som det andre
   argumentet.
 * Filteret `two_factor_rest_api_can_edit_user` overstyrer hvirvidt en brukers tofaktor-
   innstillinger kan redigeres via RAT API. Det første argumentet er den nåværende
   boolske `$can_edit`, det andre er bruker-id.
 * `two_factor_before_authentication_prompt` action which receives the provider 
   object and fires prior to the prompt shown on the authentication input form.
 * `two_factor_after_authentication_prompt` action which receives the provider object
   and fires after the prompt shown on the authentication input form.
 * `two_factor_after_authentication_input` action which receives the provider object
   and fires after the input shown on the authentication input form (if form contains
   no input, action fires immediately after `two_factor_after_authentication_prompt`).
 * `two_factor_login_backup_links` filters the backup links displayed on the two-
   factor login form.

### Redirect After the Two-Factor Challenge

To redirect users to a specific URL after completing the two-factor challenge, use
WordPress Core built-in login_redirect filter. The filter works the same way as 
in a standard WordPress login flow:

    ```
    add_filter( 'login_redirect', function( $redirect_to, $requested_redirect_to, $user ) {
        return home_url( '/dashboard/' );
    }, 10, 3 );
    ```

## Skjermbilder

[⌊Two-factor options under User Profile - Shows the main configuration area where
users can enable different authentication methods.⌉⌊Two-factor options under User
Profile - Shows the main configuration area where users can enable different authentication
methods.⌉[

Two-factor options under User Profile – Shows the main configuration area where 
users can enable different authentication methods.

[⌊Email Code Authentication during WordPress Login - Shows the email verification
screen that appears during login.⌉⌊Email Code Authentication during WordPress Login-
Shows the email verification screen that appears during login.⌉[

Email Code Authentication during WordPress Login – Shows the email verification 
screen that appears during login.

[⌊Authenticator App (TOTP) setup with QR code - Demonstrates the QR code generation
and manual key entry for TOTP setup.⌉⌊Authenticator App (TOTP) setup with QR code-
Demonstrates the QR code generation and manual key entry for TOTP setup.⌉[

Authenticator App (TOTP) setup with QR code – Demonstrates the QR code generation
and manual key entry for TOTP setup.

[⌊Backup codes generation and management - Shows the backup codes interface for 
generating and managing emergency access codes.⌉⌊Backup codes generation and management-
Shows the backup codes interface for generating and managing emergency access codes
.⌉[

Backup codes generation and management – Shows the backup codes interface for generating
and managing emergency access codes.

## Ofte stilte spørsmål

### Hvilke PHP- og WordPress-versjoner støtter To-faktor?

Denne utvidelsen støtter de siste to hovedversjonene av WordPress og [minimum PHP-versjonen](https://make.wordpress.org/core/handbook/references/php-compatibility-and-wordpress-versions/)
søttet av de WordPress-versionene.

### Hvor kan jeg sende inn tilbakemeldinger eller få hjelp med en feil?

Det beste stedet å rapportere feil, forslag til funksjonalitet eller annnen (ikke
sikkerhet) tilbakemelding er på siden [Two Factor GitHub issues](https://github.com/WordPress/two-factor/issues).
Før du sender inn en ny sak, søk etter eksisterende saker for finne ut om noen andre
har gitt samme tilbakemelding.

### Hvor kan jeg rapportere feil som har med sikkerheten å gjøre?

Bidragsyterne til utvidelsen og WordPress-fellesskapet tar sikkerhetsfeil alvorlig.
Vi setter pris på at du rapporterer dine funn på en ansvarlig måte, og vi vil gjøre
vårt beste for å anerkjenne dine bidrag.

For å melde fra om et sikkerhetsproblem, besøk [WordPress HackerOne](https://hackerone.com/wordpress)-
programmet.

### Hva hvis jeg mister alle mine autentiseringsmetoder?

If you have backup codes enabled, you can use one of those to regain access. If 
you don’t have backup codes or have used them all, you’ll need to contact your site
administrator to reset your account. This is why it’s important to always enable
backup codes and keep them in a secure location.

### Can I use this plugin with WebAuthn?

The plugin previously supported FIDO U2F, which was a predecessor to WebAuthn. There
is an open issue to add WebAuthn support here: https://github.com/WordPress/two-
factor/pull/427

### Is there a recommended way to use passkeys or hardware security keys with Two-Factor?

Yes. For passkeys and hardware security keys, you can install the Two-Factor Provider:
WebAuthn plugin: https://wordpress.org/plugins/two-factor-provider-webauthn/ . It
integrates directly with Two-Factor and adds WebAuthn-based authentication as an
additional two-factor option for users.

## Vurderinger

![](https://secure.gravatar.com/avatar/c668cfd7546bdf441dfb1c1a446752fb2e85b63138bf1156bbdb8d46bd2c3223?
s=60&d=retro&r=g)

### 󠀁[Excellent](https://wordpress.org/support/topic/excellent-14290/)󠁿

 [jhonhorac](https://profiles.wordpress.org/jhonhorac/) 14. juni, 2026 1 svar

It’s an excellent plugin; I use it on all my sites.

![](https://secure.gravatar.com/avatar/8c1c05f37e3e86668403e34090253927c52e4afe83f644dc908abd975ec69f0a?
s=60&d=retro&r=g)

### 󠀁[Work as expect](https://wordpress.org/support/topic/work-as-expect-2/)󠁿

 [vee](https://profiles.wordpress.org/okvee/) 10. juni, 2026 1 svar

The basic options expected:1. I must be able to use any authentication app.2. An
option to use email as 2nd auth.But this plugin also have backup code.

![](https://secure.gravatar.com/avatar/a1caebbd32cbf159744024fbe6c91847b25f5d92810aff05faf1d67c46e4611a?
s=60&d=retro&r=g)

### 󠀁[Users can undermine, only suitable for admin](https://wordpress.org/support/topic/users-can-undermine-only-suitable-for-admin/)󠁿

 [kloproterra](https://profiles.wordpress.org/kloproterra/) 28. mai, 2026 1 svar

This plugin requires individual users to manage 2FA. Individual users can remove
2FA from their profile at any time leaving that account vulnerable. An admin would
need to check regularly that this hasn’t been removed. There is discussion about
a custom function to force a user back to the profile page. I tested this. A user
can still leave the account with 2FA off, albeit they cannot navigation anywhere
but the profile page. However, in this state a bad actor can login with a password
only to the unprotected account, then configure 2FA to their own device, this then
removes the redirect and therefore undermines the entire process. This is a significant
flaw. However, the plugin can protect a single admin account but any sort of user
hierarchy is not protected.

![](https://secure.gravatar.com/avatar/354687c737776f99f56f6193f4bd8dba750b9f965414e327b7e3ab68ce1b8c30?
s=60&d=retro&r=g)

### 󠀁[worked and super fast support time.](https://wordpress.org/support/topic/worked-and-super-fast-support-time/)󠁿

 [bowerwebsolutions](https://profiles.wordpress.org/bowerwebsolutions/) 7. mai, 
2026 1 svar

Not only did it work well for my use case with a customer who wanted to offer optional
2fa, but when i asked about customizing the code validation page i had a response
in minutes. Very impressive. Worked well with a theme my login branded site.

![](https://secure.gravatar.com/avatar/62378cdfa286ccf2f565c5a1fb7593d118aaa923923823ce3347e87b2f9162df?
s=60&d=retro&r=g)

### 󠀁[Excellent](https://wordpress.org/support/topic/excellent-14245/)󠁿

 [aelbo](https://profiles.wordpress.org/aelbo/) 27. april, 2026 1 svar

Fonctionne parfaitement, simple et fiable

![](https://secure.gravatar.com/avatar/9c7029080b1bdf11c5e8a70e83b0a4cabc81c421fa2efd3f49cc9fd8d25eac81?
s=60&d=retro&r=g)

### 󠀁[Version wordpress 6.9.4](https://wordpress.org/support/topic/version-wordpress-6-9-4/)󠁿

 [mjezegou35](https://profiles.wordpress.org/mjezegou35/) 23. april, 2026 1 svar

I am in version 6.6.2 of WordPress and in multisite network version. Is it possible
to activate your plugin despite the constraint tested up to 6.9.1, please? I can’t
activate it at the network level?

 [ Les alle 209 vurderinger ](https://wordpress.org/support/plugin/two-factor/reviews/)

## Bidragsytere og utviklere

«To-faktor» er programvare med åpen kildekode. Følgende personer har bidratt til
denne utvidelsen:

Bidragsytere

 *   [ WordPress.org ](https://profiles.wordpress.org/wordpressdotorg/)
 *   [ George Stephanis ](https://profiles.wordpress.org/georgestephanis/)
 *   [ Kaspars ](https://profiles.wordpress.org/kasparsd/)
 *   [ Brian Haas ](https://profiles.wordpress.org/masteradhoc/)
 *   [ Derek Herman ](https://profiles.wordpress.org/valendesigns/)
 *   [ Steven Word ](https://profiles.wordpress.org/stevenkword/)
 *   [ Daisuke Takahashi ](https://profiles.wordpress.org/extendwings/)
 *   [ Scott Grant ](https://profiles.wordpress.org/sgrant/)
 *   [ Aaron D. Campbell ](https://profiles.wordpress.org/aaroncampbell/)
 *   [ John Blackbourn ](https://profiles.wordpress.org/johnbillion/)
 *   [ Steve Grunwell ](https://profiles.wordpress.org/stevegrunwell/)
 *   [ Stephen Edgar ](https://profiles.wordpress.org/netweb/)
 *   [ Ali Husnain ](https://profiles.wordpress.org/alihusnainarshad/)
 *   [ Arslan Kalwar ](https://profiles.wordpress.org/passoniate/)

«To-faktor» har blitt oversatt til 40 språk. Takk til [oversetterne](https://translate.wordpress.org/projects/wp-plugins/two-factor/contributors)
for deres bidrag.

[Oversett «To-faktor» til ditt språk.](https://translate.wordpress.org/projects/wp-plugins/two-factor)

### Interessert i utvikling?

[Bla gjennom koden](https://plugins.trac.wordpress.org/browser/two-factor/), sjekk
ut [SVN-repositoriet](https://plugins.svn.wordpress.org/two-factor/), eller abonner
på [utviklingsloggen](https://plugins.trac.wordpress.org/log/two-factor/) med [RSS](https://plugins.trac.wordpress.org/log/two-factor/?limit=100&mode=stop_on_copy&format=rss).

## Endringslogg

#### 0.16.0 – 2026-03-27

 * **Breaking Changes:** Remove legacy FIDO U2F provider support by [#439](https://github.com/WordPress/two-factor/pull/439).
 * **New Features:** Add a dedicated settings page for plugin configuration in wp-
   admin by [#764](https://github.com/WordPress/two-factor/pull/764).
 * **New Features:** Add a support links filter so consumers can customize contextual
   recovery/help links by [#615](https://github.com/WordPress/two-factor/pull/615).
 * **New Features:** Refresh backup codes UI styling and behavior by [#804](https://github.com/WordPress/two-factor/pull/804).
 * **Bug Fixes:** Delete stored TOTP secrets when the TOTP provider is disabled 
   by [#802](https://github.com/WordPress/two-factor/pull/802).
 * **Bug Fixes:** Harden provider handling so login/settings checks do not fail 
   open when expected providers disappear by [#586](https://github.com/WordPress/two-factor/pull/586).
 * **Bug Fixes:** Ensure only configured providers are saved and enabled in user
   settings by [#798](https://github.com/WordPress/two-factor/pull/798).
 * **Bug Fixes:** Improve settings-page accessibility and fix profile settings link
   behavior by [#828](https://github.com/WordPress/two-factor/pull/828) and [#830](https://github.com/WordPress/two-factor/pull/830).
 * **Bug Fixes:** Resolve PHPCS violations in provider files by [#851](https://github.com/WordPress/two-factor/pull/851).
 * **Development Updates:** Move login styles and provider scripts from inline output
   to enqueued/external assets by [#807](https://github.com/WordPress/two-factor/pull/807)
   and [#814](https://github.com/WordPress/two-factor/pull/814).
 * **Development Updates:** Improve inline docs and static-analysis compatibility(
   WPCS/phpstan) by [#810](https://github.com/WordPress/two-factor/pull/810), [#815](https://github.com/WordPress/two-factor/pull/815),
   and [#817](https://github.com/WordPress/two-factor/pull/817).
 * **Development Updates:** Improve unit test reliability and integrate CI code 
   coverage reporting by [#825](https://github.com/WordPress/two-factor/pull/825),
   [#841](https://github.com/WordPress/two-factor/pull/841), and [#842](https://github.com/WordPress/two-factor/pull/842).
 * **Development Updates:** Update readme docs and modernize CI workflow infrastructure
   by [#835](https://github.com/WordPress/two-factor/pull/835), [#837](https://github.com/WordPress/two-factor/pull/837),
   [#843](https://github.com/WordPress/two-factor/pull/843), and [#849](https://github.com/WordPress/two-factor/pull/849).
 * **Dependency Updates:** Bump `qs` from 6.14.1 to 6.14.2 by [#794](https://github.com/WordPress/two-factor/pull/794).
 * **Dependency Updates:** Bump `basic-ftp` from 5.0.5 to 5.2.0 by [#816](https://github.com/WordPress/two-factor/pull/816).
 * **Dependency Updates:** Apply automatic lint/format updates and associated Composer
   package refreshes by [#799](https://github.com/WordPress/two-factor/pull/799).

#### 0.15.0 – 2026-02-13

 * **Breaking Changes:** Trigger two-factor flow only when expected by @kasparsd
   in [#660](https://github.com/WordPress/two-factor/pull/660) and [#793](https://github.com/WordPress/two-factor/pull/793).
 * **New Features:** Include user IP address and contextual warning in two-factor
   code emails by @todeveni in [#728](https://github.com/WordPress/two-factor/pull/728)
 * **New Features:** Optimize email text for TOTP by @masteradhoc in [#789](https://github.com/WordPress/two-factor/pull/789)
 * **New Features:** Add «Settings» action link to plugin list for quick access 
   to profile by @hardikRathi in [#740](https://github.com/WordPress/two-factor/pull/740)
 * **New Features:** Additional form hooks by @eric-michel in [#742](https://github.com/WordPress/two-factor/pull/742)
 * **New Features:** Full RFC6238 Compatibility by @ericmann in [#656](https://github.com/WordPress/two-factor/pull/656)
 * **New Features:** Consistent user experience for TOTP setup by @kasparsd in [#792](https://github.com/WordPress/two-factor/pull/792)
 * **Documentation:** `@since` docs by @masteradhoc in [#781](https://github.com/WordPress/two-factor/pull/781)
 * **Documentation:** Update user and admin docs, prepare for more screenshots by
   @jeffpaul in [#701](https://github.com/WordPress/two-factor/pull/701)
 * **Documentation:** Add changelog & credits, update release notes by @jeffpaul
   in [#696](https://github.com/WordPress/two-factor/pull/696)
 * **Documentation:** Clear readme.txt by @masteradhoc in [#785](https://github.com/WordPress/two-factor/pull/785)
 * **Documentation:** Add date and time information above TOTP setup instructions
   by @masteradhoc in [#772](https://github.com/WordPress/two-factor/pull/772)
 * **Documentation:** Clarify TOTP setup instructions by @masteradhoc in [#763](https://github.com/WordPress/two-factor/pull/763)
 * **Documentation:** Update RELEASING.md by @jeffpaul in [#787](https://github.com/WordPress/two-factor/pull/787)
 * **Development Updates:** Pause deploys to SVN trunk for merges to `master` by
   @kasparsd in [#738](https://github.com/WordPress/two-factor/pull/738)
 * **Development Updates:** Fix CI checks for PHP compatability by @kasparsd in 
   [#739](https://github.com/WordPress/two-factor/pull/739)
 * **Development Updates:** Fix Playground refs by @kasparsd in [#744](https://github.com/WordPress/two-factor/pull/744)
 * **Development Updates:** Persist existing translations when introducing new helper
   text in emails by @kasparsd in [#745](https://github.com/WordPress/two-factor/pull/745)
 * **Development Updates:** Fix `missing_direct_file_access_protection` by @masteradhoc
   in [#760](https://github.com/WordPress/two-factor/pull/760)
 * **Development Updates:** Fix `mismatched_plugin_name` by @masteradhoc in [#754](https://github.com/WordPress/two-factor/pull/754)
 * **Development Updates:** Introduce Props Bot workflow by @jeffpaul in [#749](https://github.com/WordPress/two-factor/pull/749)
 * **Development Updates:** Plugin Check: Fix Missing $domain parameter by @masteradhoc
   in [#753](https://github.com/WordPress/two-factor/pull/753)
 * **Development Updates:** Tests: Update to supported WP version 6.8 by @masteradhoc
   in [#770](https://github.com/WordPress/two-factor/pull/770)
 * **Development Updates:** Fix PHP 8.5 deprecated message by @masteradhoc in [#762](https://github.com/WordPress/two-factor/pull/762)
 * **Development Updates:** Exclude 7.2 and 7.3 checks against trunk by @masteradhoc
   in [#769](https://github.com/WordPress/two-factor/pull/769)
 * **Development Updates:** Fix Plugin Check errors: `MissingTranslatorsComment`&`
   MissingSingularPlaceholder` by @masteradhoc in [#758](https://github.com/WordPress/two-factor/pull/758)
 * **Development Updates:** Add PHP 8.5 tests for latest and trunk version of WP
   by @masteradhoc in [#771](https://github.com/WordPress/two-factor/pull/771)
 * **Development Updates:** Add `phpcs:ignore` for falsepositives by @masteradhoc
   in [#777](https://github.com/WordPress/two-factor/pull/777)
 * **Development Updates:** Fix(totp): `otpauth` link in QR code URL by @sjinks 
   in [#784](https://github.com/WordPress/two-factor/pull/784)
 * **Development Updates:** Update deploy.yml by @masteradhoc in [#773](https://github.com/WordPress/two-factor/pull/773)
 * **Development Updates:** Update required WordPress Version by @masteradhoc in
   [#765](https://github.com/WordPress/two-factor/pull/765)
 * **Development Updates:** Fix: ensure execution stops after redirects by @sjinks
   in [#786](https://github.com/WordPress/two-factor/pull/786)
 * **Development Updates:** Fix `WordPress.Security.EscapeOutput.OutputNotEscaped`
   errors by @masteradhoc in [#776](https://github.com/WordPress/two-factor/pull/776)
 * **Dependency Updates:** Bump qs and express by @dependabot[bot] in [#746](https://github.com/WordPress/two-factor/pull/746)
 * **Dependency Updates:** Bump lodash from 4.17.21 to 4.17.23 by @dependabot[bot]
   in [#750](https://github.com/WordPress/two-factor/pull/750)
 * **Dependency Updates:** Bump lodash-es from 4.17.21 to 4.17.23 by @dependabot[
   bot] in [#748](https://github.com/WordPress/two-factor/pull/748)
 * **Dependency Updates:** Bump phpunit/phpunit from 8.5.44 to 8.5.52 by @dependabot[
   bot] in [#755](https://github.com/WordPress/two-factor/pull/755)
 * **Dependency Updates:** Bump symfony/process from 5.4.47 to 5.4.51 by @dependabot[
   bot] in [#756](https://github.com/WordPress/two-factor/pull/756)
 * **Dependency Updates:** Bump qs and body-parser by @dependabot[bot] in [#782](https://github.com/WordPress/two-factor/pull/782)
 * **Dependency Updates:** Bump webpack from 5.101.3 to 5.105.0 by @dependabot[bot]
   in [#780](https://github.com/WordPress/two-factor/pull/780)

#### 0.14.2 – 2025-12-11

 * **New Features:** Add filter for rest_api_can_edit_user_and_update_two_factor_options
   by @gutobenn in [#689](https://github.com/WordPress/two-factor/pull/689)
 * **Development Updates:** Remove Coveralls tooling and add inline coverage report
   by @kasparsd in [#717](https://github.com/WordPress/two-factor/pull/717)
 * **Development Updates:** Update blueprint path to pull from main branch instead
   of a deleted f… by @georgestephanis in [#719](https://github.com/WordPress/two-factor/pull/719)
 * **Development Updates:** Fix blueprint and wporg asset deploys by @kasparsd in
   [#734](https://github.com/WordPress/two-factor/pull/734)
 * **Development Updates:** Upload release only on tag releases by @kasparsd in 
   [#735](https://github.com/WordPress/two-factor/pull/735)
 * **Development Updates:** Bump playwright and @playwright/test by @dependabot[
   bot] in [#721](https://github.com/WordPress/two-factor/pull/721)
 * **Development Updates:** Bump tar-fs from 3.1.0 to 3.1.1 by @dependabot[bot] 
   in [#720](https://github.com/WordPress/two-factor/pull/720)
 * **Development Updates:** Bump node-forge from 1.3.1 to 1.3.2 by @dependabot[bot]
   in [#724](https://github.com/WordPress/two-factor/pull/724)
 * **Development Updates:** Bump js-yaml by @dependabot[bot] in [#725](https://github.com/WordPress/two-factor/pull/725)
 * **Development Updates:** Mark as tested with the latest WP core version by @kasparsd
   in [#730](https://github.com/WordPress/two-factor/pull/730)

#### 0.14.1 – 2025-09-05

 * Don’t URI encode the TOTP url for display. by @dd32 in [#711](https://github.com/WordPress/two-factor/pull/711)
 * Removed the duplicate Security.md by @slvignesh05 in [#712](https://github.com/WordPress/two-factor/pull/712)
 * Fixed linting issues by @sudar in [#707](https://github.com/WordPress/two-factor/pull/707)
 * Update development dependencies and fix failing QR unit test by @kasparsd in 
   [#714](https://github.com/WordPress/two-factor/pull/714)
 * Trigger checkbox js change event by @gedeminas in [#688](https://github.com/WordPress/two-factor/pull/688)

#### 0.14.0 – 2025-07-03

 * **Features:** Enable Application Passwords for REST API and XML-RPC authentication(
   by default) by @joostdekeijzer in [#697](https://github.com/WordPress/two-factor/pull/697)
   and [#698](https://github.com/WordPress/two-factor/pull/698). Previously this
   required two_factor_user_api_login_enable filter to be set to true which is now
   the default during application password auth. XML-RPC login is still disabled
   for regular user passwords.
 * **Features:** Label recommended methods to simplify the configuration by @kasparsd
   in [#676](https://github.com/WordPress/two-factor/pull/676) and [#675](https://github.com/WordPress/two-factor/pull/675)
 * **Documentation:** Add WP.org plugin demo by @kasparsd in [#667](https://github.com/WordPress/two-factor/pull/667)
 * **Documentation:** Document supported versions of WP core and PHP by @jeffpaul
   in [#695](https://github.com/WordPress/two-factor/pull/695)
 * **Documentation:** Document the release process by @jeffpaul in [#684](https://github.com/WordPress/two-factor/pull/684)
 * **Tooling:** Remove duplicate WP.org screenshots and graphics from SVN trunk 
   by @jeffpaul in [#683](https://github.com/WordPress/two-factor/pull/683)

#### 0.13.0 – 2025-04-02

 * Add two_factor_providers_for_user filter to limit two-factor providers available
   to each user by @kasparsd in [#669](https://github.com/WordPress/two-factor/pull/669)
 * Update automated testing to cover PHP 8.4 and default to PHP 8.3 by @BrookeDot
   in [#665](https://github.com/WordPress/two-factor/pull/665)

[View the complete changelog details here](https://github.com/wordpress/two-factor/blob/master/CHANGELOG.md).

## Felleskapsutvidelse

This plugin is developed and supported by a community. [Bidra til denne utvidelsen](https://github.com/WordPress/two-factor/)

## Meta

 *  Versjon **0.16.0**
 *  Sist oppdatert **3 måneder siden**
 *  Aktive installasjoner **100 000+**
 *  WordPress-versjon ** 6.8 eller nyere **
 *  Testet opp til **6.9.4**
 *  PHP-versjon ** 7.2 eller nyere **
 *  Språk
 * [Albanian](https://sq.wordpress.org/plugins/two-factor/), [Arabic](https://ar.wordpress.org/plugins/two-factor/),
   [Asturian](https://ast.wordpress.org/plugins/two-factor/), [Catalan](https://ca.wordpress.org/plugins/two-factor/),
   [Chinese (China)](https://cn.wordpress.org/plugins/two-factor/), [Chinese (Hong Kong)](https://zh-hk.wordpress.org/plugins/two-factor/),
   [Chinese (Taiwan)](https://tw.wordpress.org/plugins/two-factor/), [Czech](https://cs.wordpress.org/plugins/two-factor/),
   [Danish](https://da.wordpress.org/plugins/two-factor/), [Dutch](https://nl.wordpress.org/plugins/two-factor/),
   [Dutch (Belgium)](https://nl-be.wordpress.org/plugins/two-factor/), [English (Australia)](https://en-au.wordpress.org/plugins/two-factor/),
   [English (Canada)](https://en-ca.wordpress.org/plugins/two-factor/), [English (UK)](https://en-gb.wordpress.org/plugins/two-factor/),
   [English (US)](https://wordpress.org/plugins/two-factor/), [Finnish](https://fi.wordpress.org/plugins/two-factor/),
   [French (Canada)](https://fr-ca.wordpress.org/plugins/two-factor/), [French (France)](https://fr.wordpress.org/plugins/two-factor/),
   [Galician](https://gl.wordpress.org/plugins/two-factor/), [German](https://de.wordpress.org/plugins/two-factor/),
   [German (Switzerland)](https://de-ch.wordpress.org/plugins/two-factor/), [Italian](https://it.wordpress.org/plugins/two-factor/),
   [Japanese](https://ja.wordpress.org/plugins/two-factor/), [Korean](https://ko.wordpress.org/plugins/two-factor/),
   [Kurdish (Sorani)](https://ku.wordpress.org/plugins/two-factor/), [Norwegian (Bokmål)](https://nb.wordpress.org/plugins/two-factor/),
   [Persian](https://fa.wordpress.org/plugins/two-factor/), [Polish](https://pl.wordpress.org/plugins/two-factor/),
   [Portuguese (Brazil)](https://br.wordpress.org/plugins/two-factor/), [Russian](https://ru.wordpress.org/plugins/two-factor/),
   [Slovak](https://sk.wordpress.org/plugins/two-factor/), [Spanish (Chile)](https://cl.wordpress.org/plugins/two-factor/),
   [Spanish (Colombia)](https://es-co.wordpress.org/plugins/two-factor/), [Spanish (Ecuador)](https://es-ec.wordpress.org/plugins/two-factor/),
   [Spanish (Mexico)](https://es-mx.wordpress.org/plugins/two-factor/), [Spanish (Spain)](https://es.wordpress.org/plugins/two-factor/),
   [Spanish (Venezuela)](https://ve.wordpress.org/plugins/two-factor/), [Swedish](https://sv.wordpress.org/plugins/two-factor/),
   [Turkish](https://tr.wordpress.org/plugins/two-factor/), [Urdu](https://ur.wordpress.org/plugins/two-factor/)
   og [Vietnamese](https://vi.wordpress.org/plugins/two-factor/).
 *  [Oversett til ditt språk](https://translate.wordpress.org/projects/wp-plugins/two-factor)
 * Stikkord
 * [2FA](https://nb.wordpress.org/plugins/tags/2fa/)[authentication](https://nb.wordpress.org/plugins/tags/authentication/)
   [MFA](https://nb.wordpress.org/plugins/tags/mfa/)[security](https://nb.wordpress.org/plugins/tags/security/)
   [totp](https://nb.wordpress.org/plugins/tags/totp/)
 *  [Avansert visning](https://nb.wordpress.org/plugins/two-factor/advanced/)

## Vurderinger

 4.8 av 5 stjerner.

 *  [  185 5-star reviews     ](https://wordpress.org/support/plugin/two-factor/reviews/?filter=5)
 *  [  15 4-star reviews     ](https://wordpress.org/support/plugin/two-factor/reviews/?filter=4)
 *  [  0 3-star reviews     ](https://wordpress.org/support/plugin/two-factor/reviews/?filter=3)
 *  [  2 2-star reviews     ](https://wordpress.org/support/plugin/two-factor/reviews/?filter=2)
 *  [  7 1-star reviews     ](https://wordpress.org/support/plugin/two-factor/reviews/?filter=1)

[Your review](https://wordpress.org/support/plugin/two-factor/reviews/#new-post)

[Se alle omtalene](https://wordpress.org/support/plugin/two-factor/reviews/)

## Bidragsytere

 *   [ WordPress.org ](https://profiles.wordpress.org/wordpressdotorg/)
 *   [ George Stephanis ](https://profiles.wordpress.org/georgestephanis/)
 *   [ Kaspars ](https://profiles.wordpress.org/kasparsd/)
 *   [ Brian Haas ](https://profiles.wordpress.org/masteradhoc/)
 *   [ Derek Herman ](https://profiles.wordpress.org/valendesigns/)
 *   [ Steven Word ](https://profiles.wordpress.org/stevenkword/)
 *   [ Daisuke Takahashi ](https://profiles.wordpress.org/extendwings/)
 *   [ Scott Grant ](https://profiles.wordpress.org/sgrant/)
 *   [ Aaron D. Campbell ](https://profiles.wordpress.org/aaroncampbell/)
 *   [ John Blackbourn ](https://profiles.wordpress.org/johnbillion/)
 *   [ Steve Grunwell ](https://profiles.wordpress.org/stevegrunwell/)
 *   [ Stephen Edgar ](https://profiles.wordpress.org/netweb/)
 *   [ Ali Husnain ](https://profiles.wordpress.org/alihusnainarshad/)
 *   [ Arslan Kalwar ](https://profiles.wordpress.org/passoniate/)

## Brukerstøtte

Saker løst siste to måneder:

     2 av 2

 [Vis brukerstøtteforumet](https://wordpress.org/support/plugin/two-factor/)