Changes for page XWiki Two-Factor Authentication

Last modified by Agnease on 2026/05/23 18:56

Manage
- Copy
Actions
- Export
- Print Preview
Viewers
- Source
- Siblings
- Content
- Comments
- Attachments
- History
- Information
- Likes

From 1.7 to 1.6 From 1.15 to 1.14

From version 1.14

edited by Agnease
on 2026/05/22 03:43

Change comment: There is no comment for this version

To version 1.7

edited by Agnease
on 2026/05/19 06:09

Change comment: There is no comment for this version

Raw
Rendered

Summary

Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

@@ -17,8 +17,8 @@
      </p>
      <p class="hero-support">
--      This XWiki MFA / 2FA extension adds an additional verification step after the standard username and password login.
--      Users can verify access with authenticator app codes, email-delivered one-time codes, or a combined setup requiring both methods.
++      This extension protects XWiki accounts with time-based one-time verification codes while keeping the familiar
++      XWiki username and password authentication as the first login step.
      </p>
      <div class="hero-actions">
@@ -35,21 +35,19 @@
          <h2 id="overview-title">Stronger login protection for XWiki</h2>
          <p>
--          The XWiki MFA / Two-Factor Authentication extension adds additional verification after the standard
--          XWiki username and password login. It strengthens account protection without replacing the familiar
--          XWiki authentication flow.
++          The XWiki Two-Factor Authentication extension adds an additional verification screen after the standard
++          username and password login. Users confirm their identity with a time-based one-time code before accessing
++          the wiki.
          </p>
          <p>
--          The extension supports authenticator app codes using TOTP, email-delivered one-time verification codes,
--          and stricter configurations where both verification methods are required. This allows organizations to
--          choose between a simpler 2FA setup or a stronger multi-step MFA policy.
++          The extension is designed for organizations that want to improve account security while keeping authentication
++          close to the standard XWiki login experience.
          </p>
          <p>
--          Trusted clients can also be remembered for a configured period. In practice, this means that a known
--          browser or device can avoid repeated MFA prompts, while new or untrusted clients still require the
--          configured verification steps.
++          It can be useful for internal knowledge bases, intranets, documentation platforms, SOP systems, or other
++          XWiki environments where access to content and administration should be better protected.
          </p>
        </article>
@@ -57,11 +57,10 @@
          <h3 id="quick-facts-title">Quick facts</h3>
          <ul>
            <li>Works with the standard XWiki login flow</li>
--          <li>Supports authenticator app codes using TOTP</li>
--          <li>Supports email-delivered one-time verification codes</li>
--          <li>Can require app code and email code together for stricter MFA</li>
--          <li>Can remember trusted browsers or devices beyond the current session</li>
--          <li>Includes wiki administration and user profile controls</li>
++          <li>Adds a second TOTP verification step</li>
++          <li>Configuration available from wiki administration</li>
++          <li>User setup available during login or from the user profile</li>
++          <li>Administrators can enable, disable or reset MFA for users</li>
            <li>Can be used on the main wiki and subwikis</li>
          </ul>
        </aside>
@@ -84,43 +84,12 @@
          </div>
          <h3>Second login step</h3>
          <p>
--          After the username and password are verified, users are asked to enter an additional verification code
--          before accessing the wiki.
++          After the username and password are verified, users are asked to enter a time-based verification code.
          </p>
        </article>
        <article class="product-feature">
          <div class="feature-icon">
--          <i class="fa fa-mobile" aria-hidden="true"></i>
--        </div>
--        <h3>Authenticator app codes</h3>
--        <p>
--          Users can verify access with TOTP codes generated by authenticator applications on a mobile device or desktop.
--        </p>
--      </article>
--
--      <article class="product-feature">
--        <div class="feature-icon">
--          <i class="fa fa-envelope-o" aria-hidden="true"></i>
--        </div>
--        <h3>Email verification codes</h3>
--        <p>
--          Users can receive one-time verification codes by email, useful when an authenticator app is not available or preferred.
--        </p>
--      </article>
--
--      <article class="product-feature">
--        <div class="feature-icon">
--          <i class="fa fa-plus-circle" aria-hidden="true"></i>
--        </div>
--        <h3>Combined verification</h3>
--        <p>
--          The extension can also require both an authenticator app code and an email code for stricter multi-factor verification.
--        </p>
--      </article>
--
--      <article class="product-feature">
--        <div class="feature-icon">
            <i class="fa fa-qrcode" aria-hidden="true"></i>
          </div>
          <h3>User setup screen</h3>
@@ -131,21 +131,11 @@
        <article class="product-feature">
          <div class="feature-icon">
--          <i class="fa fa-laptop" aria-hidden="true"></i>
--        </div>
--        <h3>Remember trusted clients</h3>
--        <p>
--          Known browsers or devices can be remembered for a configured period, reducing repeated MFA prompts from trusted clients.
--        </p>
--      </article>
--
--      article class="product-feature">
--        <div class="feature-icon">
            <i class="fa fa-sliders" aria-hidden="true"></i>
          </div>
          <h3>Administration controls</h3>
          <p>
--          Administrators can configure MFA behavior, manage user activation, and reset user setup when required.
++          Administrators can enable the feature globally, manage user-level activation, and reset a user setup when required.
          </p>
        </article>
@@ -194,12 +194,6 @@
          </p>
          <p>
--          It can also support organizations that need MFA as part of their cybersecurity controls, including companies
--          working toward NIS 2 readiness. NIS 2 focuses on stronger cybersecurity risk management across essential and
--          important entities in the EU, and MFA is often expected as part of enterprise access protection programs.
--        </p>
--
--        <p>
            It is also useful when many users access the wiki remotely, when administrator accounts need stronger protection,
            or when the organization wants to reduce the risk of compromised passwords.
          </p>
@@ -219,46 +219,6 @@
    </div>
  </section>
--<section class="product-section-muted" aria-labelledby="compliance-title">
--  <div class="container">
--    <div class="product-layout">
--      <article class="product-summary-card">
--        <h2 id="compliance-title">Useful for MFA adoption and NIS 2 readiness</h2>
--
--        <p>
--          Many organizations now need multi-factor authentication for enterprise software, including internal
--          knowledge bases, documentation platforms, intranets and systems that contain operational procedures
--          or sensitive business information.
--        </p>
--
--        <p>
--          For organizations using XWiki, adding MFA directly to the standard XWiki login flow can help close a
--          practical access-control gap. The extension can support simple 2FA with one additional verification method,
--          or a stricter MFA setup where both authenticator app and email verification are required.
--        </p>
--
--        <p>
--          This can be relevant for organizations preparing for NIS 2, where multi-factor authentication or
--          continuous authentication is part of cybersecurity risk-management measures, where appropriate.
--          MFA support in XWiki is only one part of a broader compliance and security program, but it can be an
--          important technical control for protecting access to the wiki.
--        </p>
--      </article>
--
--      <aside class="product-info-card" aria-labelledby="mfa-readiness-title">
--        <h3 id="mfa-readiness-title">Security controls supported</h3>
--        <ul>
--          <li>Second-factor verification after password login</li>
--          <li>Authenticator app or email-based verification codes</li>
--          <li>Reduced repeated prompts for trusted clients</li>
--          <li>Administration controls for user-level MFA management</li>
--          <li>Better protection for administrator and remote-access accounts</li>
--        </ul>
--      </aside>
--    </div>
--  </div>
--</section>
--
  #*
  <section aria-labelledby="gallery-title">
    <div class="container">