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.5 to 1.6 From 1.11 to 1.12

From version 1.6

edited by Agnease
on 2026/05/12 20:32

Change comment: There is no comment for this version

To version 1.11

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

Change comment: There is no comment for this version

Raw
Rendered

Summary

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

Details

Page properties

Content

@@ -5,7 +5,7 @@
  <section class="hero hero-centered product-hero" aria-labelledby="product-title">
    <div class="container hero-inner">
--    <div class="product-kicker">
++    <div class="hero-kicker">
        <i class="fa fa-lock" aria-hidden="true"></i>
        XWiki security extension
      </div>
@@ -17,8 +17,8 @@
      </p>
      <p class="hero-support">
--      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.
++      This extension protects XWiki accounts with an additional verification step after the standard username and password login.
++      Users can verify access with an authenticator app code or an email-delivered code, while XWiki keeps its familiar login experience.
      </p>
      <div class="hero-actions">
@@ -36,13 +36,14 @@
          <p>
            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.
++          username and password login. Users confirm their identity with a time-based one-time code generated by an
++          authenticator app, or with a verification code delivered by email.
          </p>
          <p>
            The extension is designed for organizations that want to improve account security while keeping authentication
--          close to the standard XWiki login experience.
++          close to the standard XWiki login experience. It also supports remembering trusted clients beyond the current
++          session, so users are not forced to enter a second factor again on every login from the same trusted browser.
          </p>
          <p>
@@ -55,7 +55,9 @@
          <h3 id="quick-facts-title">Quick facts</h3>
          <ul>
            <li>Works with the standard XWiki login flow</li>
--          <li>Adds a second TOTP verification step</li>
++          <li>Supports authenticator app verification codes</li>
++          <li>Supports email-delivered verification codes</li>
++          <li>Can remember trusted clients beyond the current session</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>
@@ -81,12 +81,33 @@
          </div>
          <h3>Second login step</h3>
          <p>
--          After the username and password are verified, users are asked to enter a time-based verification code.
++          After the username and password are verified, users are asked to enter an additional verification code
++          before accessing the wiki.
          </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 codes generated by authenticator applications, such as mobile TOTP apps.
++        </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 also receive a verification code by email, useful when an authenticator app is not available.
++        </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>
@@ -97,6 +97,17 @@
        <article class="product-feature">
          <div class="feature-icon">
++          <i class="fa fa-clock-o" aria-hidden="true"></i>
++        </div>
++        <h3>Remember trusted clients</h3>
++        <p>
++          Trusted browsers can be remembered beyond the current session, reducing repeated MFA prompts while keeping
++          the second factor active for new or untrusted 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>
@@ -150,6 +150,12 @@
          </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>
@@ -169,6 +169,42 @@
    </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, especially when the
++          platform contains internal documentation, procedures, operational knowledge or sensitive business data.
++        </p>
++
++        <p>
++          For organizations using XWiki as a knowledge platform, having MFA embedded in the standard XWiki login
++          experience helps close a practical security gap without requiring a full replacement of the authentication flow.
++        </p>
++
++        <p>
++          This can be relevant for companies preparing for NIS 2 requirements, where MFA is part of a broader
++          cybersecurity risk management and access protection strategy.
++        </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">