Changes for page XWiki Two-Factor Authentication

Last modified by Agnease on 2026/06/24 16:39

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

From 1.11 to 1.10 From 6.13 to 6.12

From version 6.12

edited by Agnease
on 2026/06/23 07:40

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 (2 modified, 0 added, 0 removed)
Objects (0 modified, 0 added, 1 removed)
- Agnease.Code.SEODetailsClass[0]

Details

Page properties

Title

@@ -1,1 +1,1 @@
--XWiki Two-Factor Authentication
++xwiki-two-factor-authentication

Content

@@ -1,98 +1,26 @@
  {{velocity}}
  #set ($discard = $xwiki.ssx.use('PublicWebSite.WebHome'))
  #set ($discard = $xwiki.ssx.use('products.WebHome'))
--
--#set ($mainCapabilityItems = [{
--  'title': 'Second verification step',
--  'icon': 'key',
--  'content': 'Add an additional verification screen after the normal XWiki username and password login.'
--},{
--  'title': 'Authenticator app codes',
--  'icon': 'mobile',
--  'content': 'Let users verify access with time-based TOTP codes generated by authenticator applications.'
--},{
--  'title': 'Email verification codes',
--  'icon': 'envelope-o',
--  'content': 'Send one-time verification codes by email when this method is enabled or combined with app codes.'
--}])
--
--#set ($adminExperienceItems = [{
--  'title': 'Simple MFA policy',
--  'icon': 'cog',
--  'content': 'Administrators can make MFA optional or required for all users from the XWiki Administration section.'
--},{
--  'title': 'Recovery and trusted devices',
--  'icon': 'shield',
--  'content': 'Configure recovery-code count and trusted-device duration according to the organization security policy.'
--},{
--  'title': 'Administration overview',
--  'icon': 'table',
--  'content': 'Review MFA adoption across users with summary indicators and a filterable Live Data table.'
--}])
--
--#set ($userExperienceItems = [{
--  'title': 'Self-service setup',
--  'icon': 'qrcode',
--  'content': 'Users configure MFA from their profile by scanning a QR code or entering the setup key manually.'
--},{
--  'title': 'Familiar login flow',
--  'icon': 'sign-in',
--  'content': 'After the normal login, users enter the configured verification code before accessing XWiki.'
--},{
--  'title': 'Profile management',
--  'icon': 'user',
--  'content': 'Users can review MFA status, manage recovery codes and remove trusted devices from their profile.'
--}])
--
--#set ($recoveryItems = [{
--  'title': 'Recovery codes',
--  'icon': 'life-ring',
--  'content': 'Recovery codes provide backup access when a user loses access to the authenticator application.'
--},{
--  'title': 'Trusted devices',
--  'icon': 'desktop',
--  'content': 'Trusted browsers or devices can skip repeated MFA prompts for a configured period.'
--},{
--  'title': 'Administrator reset',
--  'icon': 'refresh',
--  'content': 'Administrators can reset a user MFA setup when the user needs to restart the configuration process.'
--}])
--
--#set ($rolloutItems = [{
--  'title': 'Start with a pilot group',
--  'content': 'Test the extension with administrators or a small user group before enabling it widely.'
--},{
--  'title': 'Define the MFA policy',
--  'content': 'Decide whether MFA should be optional, required for administrators, or required for all users.'
--},{
--  'title': 'Configure recovery options',
--  'content': 'Choose whether recovery codes and trusted devices should be enabled.'
--},{
--  'title': 'Inform users',
--  'content': 'Explain how users configure MFA, save recovery codes and manage trusted devices.'
--},{
--  'title': 'Monitor adoption',
--  'content': 'Use the administration overview to identify users who still need to configure MFA.'
--}])
--
  {{html clean="false"}}
--<div class="product-doc-page product-mfa-page">
--
--<section class="hero hero-centered" aria-labelledby="product-title">
++<section class="hero hero-centered product-hero" aria-labelledby="product-title">
    <div class="container hero-inner">
      <div class="hero-kicker">
        <i class="fa fa-lock" aria-hidden="true"></i>
--      XWiki 2FA and MFA
++      XWiki security extension
      </div>
      <h1 id="product-title">XWiki Two-Factor Authentication</h1>
      <p class="lead">
--      Protect XWiki logins with a second verification step using authenticator app codes,
--      email verification codes, or both.
++      Add a second verification step to the standard XWiki login flow.
      </p>
++    <p class="hero-support">
++      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">
        <a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Ask about this extension</a>
        <a class="btn btn-secondary" href="$xwiki.getURL('products.WebHome')">View all products</a>
@@ -104,19 +104,24 @@
    <div class="container">
      <div class="product-layout">
        <article class="product-summary-card">
--        <h2 id="overview-title">Two-factor authentication built into XWiki</h2>
++        <h2 id="overview-title">Stronger login protection for XWiki</h2>
          <p>
--          XWiki Two-Factor Authentication adds MFA/2FA support to the standard XWiki login flow.
--          Users continue to sign in with their normal username and password, then confirm access with
--          an additional verification method.
++          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 generated by an
++          authenticator app, or with a verification code delivered by email.
          </p>
          <p>
--          The extension supports authenticator app codes, email-delivered verification codes, or a combined
--          setup where both methods are required. It is designed to improve account protection without replacing
--          the familiar XWiki authentication experience.
++          The extension is designed for organizations that want to improve account security while keeping authentication
++          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>
++          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>
        <aside class="product-info-card" aria-labelledby="quick-facts-title">
@@ -123,12 +123,13 @@
          <h3 id="quick-facts-title">Quick facts</h3>
          <ul>
            <li>Works with the standard XWiki login flow</li>
--          <li>Supports TOTP authenticator applications</li>
--          <li>Supports email-delivered one-time codes</li>
--          <li>Can require app and email verification together</li>
--          <li>Includes recovery codes for backup access</li>
--          <li>Can remember trusted browsers or devices</li>
--          <li>Includes administration and user controls</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>
++          <li>Can be used on the main wiki and subwikis</li>
          </ul>
        </aside>
      </div>
@@ -135,210 +135,177 @@
    </div>
  </section>
--<section aria-labelledby="capabilities-title">
++<section aria-labelledby="features-title">
    <div class="container">
--    <h2 id="capabilities-title">Main capabilities</h2>
--
++    <h2 id="features-title">Main capabilities</h2>
      <p class="section-intro">
--      A focused set of MFA/2FA features for stronger XWiki account protection without changing the standard login experience.
++      The extension focuses on adding a practical second authentication step while keeping the standard XWiki login
++      process and administration experience understandable.
      </p>
      <div class="product-feature-grid">
--      #foreach ($entry in $mainCapabilityItems)
--        <article class="product-feature">
--          <div class="card-heading">
--            <div class="feature-icon">
--              <i class="fa fa-$entry.icon" aria-hidden="true"></i>
--            </div>
--            <h3>$entry.title</h3>
--          </div>
++      <article class="product-feature">
++        <div class="feature-icon">
++          <i class="fa fa-key" aria-hidden="true"></i>
++        </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.
++        </p>
++      </article>
--          <p>$entry.content</p>
--        </article>
--      #end
--    </div>
--  </div>
--</section>
++      <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>
--<section class="product-section-muted" aria-labelledby="security-title">
--  <div class="container">
--    <div class="product-layout">
--      <article class="product-summary-card">
--        <h2 id="security-title">Useful for XWiki security and access protection</h2>
++      <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>
          <p>
--          Many organizations need multi-factor authentication for internal tools, knowledge bases,
--          intranets, documentation platforms and systems containing operational or sensitive information.
++          Users can configure their verification code setup during login or from their XWiki profile when needed.
          </p>
++      </article>
++      <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>
--          For XWiki, adding two-factor authentication directly to the standard login flow helps protect
--          administrator accounts, remote users, private knowledge bases and customer or partner portals.
++          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>
--      <aside class="product-info-card" aria-labelledby="use-cases-title">
--        <h3 id="use-cases-title">Typical use cases</h3>
--        <ul>
--          <li>Administrator account protection</li>
--          <li>Internal knowledge base security</li>
--          <li>Private documentation platforms</li>
--          <li>Remote user access protection</li>
--          <li>Customer or partner portals</li>
--          <li>Security review and NIS 2 readiness initiatives</li>
--        </ul>
--      </aside>
--    </div>
--  </div>
--</section>
++      <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 enable the feature globally, manage user-level activation, and reset a user setup when required.
++        </p>
++      </article>
--<section aria-labelledby="admin-experience-title">
--  <div class="container">
--    <h2 id="admin-experience-title">Administrator experience</h2>
++      <article class="product-feature">
++        <div class="feature-icon">
++          <i class="fa fa-user" aria-hidden="true"></i>
++        </div>
++        <h3>Profile integration</h3>
++        <p>
++          The extension adds user profile controls so the second-factor setup can be reviewed or reset from XWiki.
++        </p>
++      </article>
--    <p class="section-intro">
--      Administrators can configure the MFA policy, monitor adoption and reset user MFA setups when needed.
--    </p>
++      <article class="product-feature">
++        <div class="feature-icon">
++          <i class="fa fa-random" aria-hidden="true"></i>
++        </div>
++        <h3>Fallback behavior</h3>
++        <p>
++          The extension can fall back to standard XWiki authentication when the feature is not enabled or not configured.
++        </p>
++      </article>
--    <div class="product-feature-grid">
--      #foreach ($entry in $adminExperienceItems)
--        <article class="product-feature">
--          <div class="card-heading">
--            <div class="feature-icon">
--              <i class="fa fa-$entry.icon" aria-hidden="true"></i>
--            </div>
--            <h3>$entry.title</h3>
--          </div>
--
--          <p>$entry.content</p>
--        </article>
--      #end
++      <article class="product-feature">
++        <div class="feature-icon">
++          <i class="fa fa-sitemap" aria-hidden="true"></i>
++        </div>
++        <h3>Main wiki and subwikis</h3>
++        <p>
++          The extension is designed to support XWiki environments using the main wiki and subwikis.
++        </p>
++      </article>
      </div>
--
--    <p class="product-gallery-caption">
--      Administration screens for configuring MFA and reviewing MFA adoption across users.
--    </p>
    </div>
  </section>
--{{/html}}
--
--{{gallery}}
--[[image:mfa-admin-configuration.png]]
--[[image:mfa-admin-overview.png]]
--{{/gallery}}
--
--{{html clean="false"}}
--
--<section class="product-section-muted" aria-labelledby="user-experience-title">
++<section aria-labelledby="use-cases-title">
    <div class="container">
--    <h2 id="user-experience-title">User experience</h2>
++    <div class="product-layout">
++      <article class="product-summary-card">
++        <h2 id="use-cases-title">When this extension is useful</h2>
--    <p class="section-intro">
--      Users can configure MFA from their profile and complete the second verification step during login.
--    </p>
++        <p>
++          Two-factor authentication is especially relevant when XWiki contains internal documentation, procedures,
++          customer information, project knowledge, administrative pages, or business-critical content.
++        </p>
--    <div class="product-feature-grid">
--      #foreach ($entry in $userExperienceItems)
--        <article class="product-feature">
--          <div class="card-heading">
--            <div class="feature-icon">
--              <i class="fa fa-$entry.icon" aria-hidden="true"></i>
--            </div>
--            <h3>$entry.title</h3>
--          </div>
++        <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>$entry.content</p>
--        </article>
--      #end
--    </div>
++        <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>
++      </article>
--    <p class="product-gallery-caption">
--      User setup and login verification screens.
--    </p>
--  </div>
--</section>
--
--{{/html}}
--
--{{gallery}}
--[[image:mfa-user-setup-qr.png]]
--[[image:mfa-login-verification.png]]
--{{/gallery}}
--
--{{html clean="false"}}
--
--<section aria-labelledby="recovery-title">
--  <div class="container">
--    <h2 id="recovery-title">Recovery codes and trusted devices</h2>
--
--    <p class="section-intro">
--      Recovery codes and trusted devices help balance stronger access protection with a smoother user experience.
--    </p>
--
--    <div class="product-feature-grid">
--      #foreach ($entry in $recoveryItems)
--        <article class="product-feature">
--          <div class="card-heading">
--            <div class="feature-icon">
--              <i class="fa fa-$entry.icon" aria-hidden="true"></i>
--            </div>
--            <h3>$entry.title</h3>
--          </div>
--
--          <p>$entry.content</p>
--        </article>
--      #end
++      <aside class="product-info-card" aria-labelledby="good-fit-title">
++        <h3 id="good-fit-title">Good fit for</h3>
++        <ul>
++          <li>Private XWiki knowledge bases</li>
++          <li>Company intranets</li>
++          <li>SOP and controlled-document platforms</li>
++          <li>Documentation portals with sensitive content</li>
++          <li>Wikis with several administrators or remote users</li>
++        </ul>
++      </aside>
      </div>
--
--    <p class="product-gallery-caption">
--      Recovery codes, trusted devices and user profile management.
--    </p>
    </div>
  </section>
--{{/html}}
--
--{{gallery}}
--[[image:mfa-recovery-codes.png]]
--[[image:mfa-trusted-devices.png]]
--[[image:mfa-user-profile-overview.png]]
--[[image:mfa-admin-user-management.png]]
--{{/gallery}}
--
--{{html clean="false"}}
--
--<section class="product-section-muted" aria-labelledby="rollout-title">
++<section class="product-section-muted" aria-labelledby="compliance-title">
    <div class="container">
      <div class="product-layout">
        <article class="product-summary-card">
--        <h2 id="rollout-title">Rollout recommendations</h2>
++        <h2 id="compliance-title">Useful for MFA adoption and NIS 2 readiness</h2>
          <p>
--          For a smooth rollout, start with a small administrator or pilot group before requiring MFA for everyone.
--          This helps validate the configuration, prepare user communication and reduce support issues.
++          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>
--        <ol class="process-list">
--          #foreach ($entry in $rolloutItems)
--            <li>
--              <strong>$entry.title</strong>
--              $entry.content
--            </li>
--          #end
--        </ol>
++        <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="planning-title">
--        <h3 id="planning-title">Useful information before installation</h3>
++      <aside class="product-info-card" aria-labelledby="mfa-readiness-title">
++        <h3 id="mfa-readiness-title">Security controls supported</h3>
          <ul>
--          <li>XWiki version</li>
--          <li>Single wiki or wiki farm with subwikis</li>
--          <li>Current authentication setup</li>
--          <li>Optional or globally required MFA policy</li>
--          <li>Trusted-device policy</li>
--          <li>Recovery-code policy</li>
--          <li>Rollout communication needs</li>
++          <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>
@@ -345,23 +345,35 @@
    </div>
  </section>
++#*
++<section aria-labelledby="gallery-title">
++  <div class="container">
++    <div class="product-gallery-panel">
++      <h2 id="gallery-title">Screenshots</h2>
++      <p class="gallery-note">
++        Use this area to show the login verification screen, first-time setup, user profile controls,
++        and administration configuration.
++      </p>
++
++      <div class="product-gallery-placeholder">
++        Replace this placeholder with the XWiki gallery macro and 3-5 screenshots from the application.
++      </div>
++    </div>
++  </div>
++</section>
++*#
  <section class="cta-section" aria-labelledby="cta-title">
    <div class="container">
      <div class="cta-panel">
        <h2 id="cta-title">Interested in using this extension?</h2>
--
        <p>
--        Send a short message with your XWiki version, authentication setup and whether you need
--        authenticator app codes, email verification codes, combined verification, recovery codes
--        or trusted-device remembering.
++        Send a short message with your XWiki version, authentication setup, and whether you use a single wiki
++        or a main wiki with subwikis.
        </p>
--
        <a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Contact Agnease</a>
      </div>
    </div>
  </section>
--</div>
--
  {{/html}}
  {{/velocity}}

Agnease.Code.SEODetailsClass[0]

metaDescription

...	...	@@ -1,1 +1,0 @@
1		-Agnease Two-Factor Authentication for XWiki adds a second login verification step with authenticator app codes, email codes, combined verification and trusted-device remembering.

metaTitle

...	...	@@ -1,1 +1,0 @@
1		-XWiki Two-Factor Authentication with 2FA and MFA Support \| Agnease