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 6.9 to 6.8 From 7.1 to 6.13

From version 6.13

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

Change comment: There is no comment for this version

To version 6.9

edited by Agnease
on 2026/05/23 18:55

Change comment: There is no comment for this version

Raw
Rendered

Summary

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

Details

Page properties

Content

@@ -1,83 +1,9 @@
  {{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': 'MFA policy',
--  'icon': 'cog',
--  'content': '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"}}
--<section class="hero hero-centered" aria-labelledby="product-title">
++<section class="hero hero-centered" aria-labelledby="hero-title">
    <div class="container hero-inner">
      <div class="hero-kicker">
        <i class="fa fa-lock" aria-hidden="true"></i>
@@ -105,16 +105,20 @@
          <h2 id="overview-title">Two-factor authentication built into 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.
++          XWiki Two-Factor Authentication adds an additional verification screen after the standard
++          XWiki username and password login. It improves account protection without replacing the
++          familiar XWiki authentication flow.
          </p>
          <p>
--          The extension supports authenticator app codes, email-delivered verification codes, or a combined
--          setup where both methods are required. It improves account protection without replacing the familiar
--          XWiki authentication experience.
++          Users can verify access with TOTP codes generated by an authenticator app, with one-time
++          codes delivered by email, or with a combined setup requiring both methods.
          </p>
++
++        <p>
++          Trusted browsers or devices can be remembered for a configured period, reducing repeated
++          verification prompts on known clients while still requiring verification from new or untrusted ones.
++        </p>
        </article>
        <aside class="product-info-card" aria-labelledby="quick-facts-title">
@@ -121,12 +121,11 @@
          <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>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</li>
            <li>Can remember trusted browsers or devices</li>
--          <li>Includes administration and user controls</li>
++          <li>Includes administration and user setup controls</li>
          </ul>
        </aside>
      </div>
@@ -133,9 +133,9 @@
    </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.
@@ -142,201 +142,82 @@
      </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>
++      <article class="product-feature">
++        <div class="card-heading">
++          <div class="feature-icon">
++            <i class="fa fa-key" aria-hidden="true"></i>
            </div>
++          <h3>Second verification step</h3>
++        </div>
--          <p>$entry.content</p>
--        </article>
--      #end
--    </div>
--  </div>
--</section>
--
--<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>
--
          <p>
--          Many organizations need multi-factor authentication for internal tools, knowledge bases,
--          intranets, documentation platforms and systems containing operational or sensitive information.
++          After username and password verification, users complete an additional step before accessing XWiki.
++          The flow can require one verification method or both app and email codes.
          </p>
++      </article>
++      <article class="product-feature">
++        <div class="card-heading">
++          <div class="feature-icon">
++            <i class="fa fa-mobile" aria-hidden="true"></i>
++          </div>
++          <h3>Authenticator app codes</h3>
++        </div>
++
          <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.
++          Users can verify access with TOTP codes generated by authenticator applications on mobile or desktop devices.
          </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>
--
--<section aria-labelledby="admin-experience-title">
--  <div class="container">
--    <h2 id="admin-experience-title">Administrator experience</h2>
--
--    <p class="section-intro">
--      Administrators can configure the MFA policy, monitor adoption and reset user MFA setups when needed.
--    </p>
--
--    <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>
++      <article class="product-feature">
++        <div class="card-heading">
++          <div class="feature-icon">
++            <i class="fa fa-envelope-o" aria-hidden="true"></i>
            </div>
++          <h3>Email verification codes</h3>
++        </div>
--          <p>$entry.content</p>
--        </article>
--      #end
++        <p>
++          Users can receive one-time verification codes by email when an authenticator app is not available or preferred.
++        </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 class="product-section-muted" aria-labelledby="security-title">
    <div class="container">
--    <h2 id="user-experience-title">User experience</h2>
--
--    <p class="section-intro">
--      Users can configure MFA from their profile and complete the second verification step during login.
--    </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>$entry.content</p>
--        </article>
--      #end
--    </div>
--
--    <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
--    </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">
--  <div class="container">
      <div class="product-layout">
        <article class="product-summary-card">
--        <h2 id="rollout-title">Rollout recommendations</h2>
++        <h2 id="security-title">Useful for XWiki security 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 need multi-factor authentication for enterprise software, including internal
++          knowledge bases, intranets, documentation platforms and systems containing operational procedures
++          or sensitive business information.
          </p>
--        <ol class="process-list">
--          #foreach ($entry in $rolloutItems)
--            <li>
--              <strong>$entry.title</strong>
--              $entry.content
--            </li>
--          #end
--        </ol>
++        <p>
++          For organizations using XWiki, adding two-factor authentication directly to the standard login flow
++          can help close a practical access-control gap. It can be useful for administrator accounts, remote users,
++          private knowledge bases and broader security readiness initiatives such as NIS 2 preparation.
++        </p>
++
++        <p>
++          This extension is not a complete compliance solution on its own, but it can provide an important
++          technical control for protecting access to XWiki.
++        </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="security-controls-title">
++        <h3 id="security-controls-title">Useful for</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>XWiki 2FA rollout</li>
++          <li>XWiki MFA adoption</li>
++          <li>Administrator account protection</li>
++          <li>Remote user access protection</li>
++          <li>Private knowledge base security</li>
++          <li>NIS 2 readiness initiatives</li>
          </ul>
        </aside>
      </div>
@@ -347,13 +347,10 @@
    <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 need
++        authenticator app codes, email verification codes, combined verification, or trusted-device remembering.
        </p>
--
        <a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Contact Agnease</a>
      </div>
    </div>