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 22.6 to 22.5 From 25.4 to 25.3

From version 25.3

edited by Agnease
on 2026/06/24 16:13

Change comment: There is no comment for this version

To version 22.6

edited by Agnease
on 2026/06/24 15:24

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,74 +1,106 @@
  {{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.'
++#set ($businessValueItems = [{
++  'title': 'Reduce account compromise risk',
++  'icon': 'shield',
++  'content': 'Add a second verification step after password login to better protect private XWiki content and administrator accounts.'
  },{
--  'title': 'Authenticator app codes',
--  'icon': 'mobile',
--  'content': 'Let users verify access with time-based TOTP codes generated by authenticator applications.'
++  'title': 'Keep the standard XWiki experience',
++  'icon': 'sign-in',
++  'content': 'Extend the familiar XWiki login flow instead of replacing it with a completely different authentication experience.'
  },{
--  'title': 'Recovery and trusted devices',
--  'icon': 'shield',
--  'content': 'Provide backup access with recovery codes and reduce repeated prompts on trusted browsers.'
++  'title': 'Support a controlled rollout',
++  'icon': 'tasks',
++  'content': 'Start with optional MFA, then require MFA for all users when the organization is ready.'
  }])
--#set ($adminExperienceItems = [{
--  'title': 'Rollout policy',
++#set ($adminControlItems = [{
++  'title': 'Global MFA policy',
    'icon': 'cog',
--  'content': 'Make additional verification optional at first or required for all users from the XWiki Administration section.'
++  'content': 'Administrators can decide whether MFA is optional or required for all users.'
  },{
--  'title': 'Configuration options',
--  'icon': 'sliders',
--  'content': 'Set the authenticator issuer name, recovery-code count and trusted-device duration.'
++  'title': 'Recovery policy',
++  'icon': 'life-ring',
++  'content': 'Configure how many one-time recovery codes are generated for each user, or disable recovery codes if needed.'
  },{
--  'title': 'Administration overview',
++  'title': 'Trusted-device policy',
++  'icon': 'desktop',
++  'content': 'Configure how long a trusted browser remains valid, or disable trusted devices for stricter environments.'
++}])
++
++#set ($adminVisibilityItems = [{
++  'title': 'MFA adoption overview',
++  'icon': 'bar-chart',
++  'content': 'Review how many users are scanned, how many have MFA configured, and how many still need attention.'
++},{
++  'title': 'Filterable user table',
    'icon': 'table',
--  'content': 'Review adoption with summary indicators and a filterable Live Data table.'
++  'content': 'Use the Live Data table to review configured users, recovery-code status and trusted-device usage.'
++},{
++  'title': 'Operational monitoring',
++  'icon': 'search',
++  'content': 'Identify accounts with missing recovery codes or trusted devices from the administration area.'
  }])
--#set ($userExperienceItems = [{
++#set ($userAdoptionItems = [{
    'title': 'Self-service setup',
    'icon': 'qrcode',
--  'content': 'Users configure the second verification step from their profile by scanning a QR code or entering the setup key manually.'
++  'content': 'Users can configure MFA by scanning a QR code with their authenticator application.'
  },{
--  'title': 'Login verification',
--  'icon': 'sign-in',
--  'content': 'After the normal login, users enter the verification code generated by their authenticator app.'
++  'title': 'Manual setup details',
++  'icon': 'keyboard-o',
++  'content': 'Users can also enter the account name and secret key manually if they cannot scan the QR code.'
  },{
++  'title': 'Enforced setup flow',
++  'icon': 'lock',
++  'content': 'When MFA is required, users are guided to complete setup before continuing.'
++}])
++
++#set ($loginProtectionItems = [{
++  'title': 'Second login step',
++  'icon': 'key',
++  'content': 'After the normal username and password login, users enter the verification code from their authenticator app.'
++},{
++  'title': 'Backup login option',
++  'icon': 'unlock-alt',
++  'content': 'If recovery codes are enabled, users can use a recovery code when they lose access to the authenticator app.'
++},{
    'title': 'Trusted browser option',
    'icon': 'desktop',
    'content': 'Users can trust the current browser for the configured duration after successful verification.'
  }])
--#set ($selfServiceItems = [{
--  'title': 'Recovery codes',
++#set ($continuityItems = [{
++  'title': 'One-time recovery codes',
    'icon': 'life-ring',
--  'content': 'Recovery codes provide backup access when a user loses access to the authenticator application.'
++  'content': 'Recovery codes help users regain access if they lose their authenticator device.'
  },{
--  'title': 'Trusted devices',
--  'icon': 'desktop',
--  'content': 'Trusted devices can be reviewed and removed from the user profile.'
++  'icon': 'life-ring',
++  'content': 'Recovery codes help users regain access if they lose their authenticator device.'
  },{
--  'title': 'Profile management',
--  'icon': 'user',
--  'content': 'Users can review status, generate recovery codes, manage trusted devices and reset their setup.'
++  'title': 'Codes shown once',
++  'icon': 'eye-slash',
++  'content': 'Recovery codes are displayed only once and each code can be used a single time.'
++},{
++  'title': 'Trusted-device management',
++  'icon': 'desktop',
++  'content': 'Users can review trusted devices, identify the current browser and remove devices they no longer use.'
  }])
  #set ($adminSupportItems = [{
--  'title': 'User status',
++  'title': 'User MFA status',
    'icon': 'user',
--  'content': 'Administrators can open a user profile and check the verification status for that account.'
++  'content': 'Administrators can open a user profile and check whether MFA is configured for that account.'
  },{
--  'title': 'Setup reset',
++  'title': 'Helpdesk recovery',
    'icon': 'refresh',
--  'content': 'Administrators can reset the setup when a user needs to restart the configuration process.'
++  'content': 'Administrators can reset MFA when a user loses access to the authenticator app or needs to restart setup.'
  },{
--  'title': 'Controlled recovery',
--  'icon': 'unlock-alt',
--  'content': 'Resetting the setup removes the authenticator configuration, recovery codes and trusted devices for that user.'
++  'title': 'Clean reset',
++  'icon': 'trash',
++  'content': 'Resetting MFA removes the authenticator setup, recovery codes and trusted devices for that user.'
  }])
  #set ($rolloutItems = [{
@@ -75,17 +75,17 @@
    'title': 'Start with a pilot group',
    'content': 'Test the extension with administrators or a small user group before enabling it widely.'
  },{
--  'title': 'Define the rollout policy',
--  'content': 'Decide whether additional verification should be optional at first or required for all users.'
++  'title': 'Define the MFA policy',
++  'content': 'Decide whether MFA should be optional at first or required for all users.'
  },{
    'title': 'Configure recovery options',
    'content': 'Choose the number of recovery codes and whether trusted devices should be allowed.'
  },{
--  'title': 'Inform users',
--  'content': 'Explain how users configure the authenticator app, save recovery codes and manage trusted devices.'
++  'title': 'Prepare user communication',
++  '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 protection.'
++  'content': 'Use the administration overview to identify users who still need to configure MFA.'
  }])
  {{html clean="false"}}
@@ -94,14 +94,14 @@
    <div class="container hero-inner">
      <div class="hero-kicker">
        <i class="fa fa-lock" aria-hidden="true"></i>
--      XWiki 2FA with MFA rollout support
++      XWiki 2FA and MFA
      </div>
      <h1 id="product-title">XWiki Two-Factor Authentication</h1>
      <p class="lead">
--      Protect XWiki logins with authenticator app verification, recovery codes,
--      trusted devices and administration controls for a safer rollout.
++      Protect XWiki logins with authenticator app verification, recovery codes, trusted devices
++      and administrator visibility.
      </p>
      <div class="hero-actions">
@@ -115,18 +115,18 @@
    <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">MFA protection built for XWiki</h2>
          <p>
--          XWiki Two-Factor Authentication adds an additional verification step to the standard
--          XWiki login flow. Users continue to sign in with their normal username and password,
--          then confirm access with a time-based code from an authenticator application.
++          XWiki Two-Factor Authentication adds a second verification step to the standard XWiki login flow.
++          Users continue to sign in with their normal username and password, then confirm access with a
++          time-based code generated by an authenticator application.
          </p>
          <p>
--          The application has evolved beyond a simple login-code screen. It supports global
--          enforcement, recovery codes, trusted devices, user self-service, administrator
--          reset actions and an overview for monitoring adoption.
++          The extension is designed for organizations that use XWiki to manage internal documentation,
++          procedures, knowledge bases, customer portals or other private collaboration spaces where
++          stronger account protection is needed.
          </p>
        </article>
@@ -134,12 +134,12 @@
          <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>Can require additional verification for all users</li>
++          <li>Uses TOTP authenticator applications</li>
++          <li>Can require MFA for all users</li>
            <li>Includes one-time recovery codes</li>
--          <li>Can remember trusted browsers or devices</li>
++          <li>Supports trusted browsers or devices</li>
            <li>Includes user self-service controls</li>
--          <li>Includes an administration overview</li>
++          <li>Includes administration monitoring</li>
          </ul>
        </aside>
      </div>
@@ -146,17 +146,16 @@
    </div>
  </section>
--<section aria-labelledby="capabilities-title">
++<section class="product-section-muted" aria-labelledby="business-value-title">
    <div class="container">
--    <h2 id="capabilities-title">Main capabilities</h2>
++    <h2 id="business-value-title">Business value</h2>
      <p class="section-intro">
--      A focused set of authentication protection features for stronger XWiki account security
--      without replacing the familiar login experience.
++      The extension helps organizations strengthen XWiki access protection without making login and account recovery unnecessarily complex.
      </p>
      <div class="product-feature-grid">
--      #foreach ($entry in $mainCapabilityItems)
++      #foreach ($entry in $businessValueItems)
          <article class="product-feature">
            <div class="card-heading">
              <div class="feature-icon">
@@ -172,50 +172,53 @@
    </div>
  </section>
--<section class="product-section-muted" aria-labelledby="security-title">
++<section aria-labelledby="admin-control-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>
++    <h2 id="admin-control-title">Administrator control</h2>
--        <p>
--          Many organizations use XWiki to store internal documentation, procedures, operational
--          knowledge and business-critical information. Adding an additional authentication factor helps
--          reduce the risk of account compromise when a password is exposed or reused.
--        </p>
++    <p class="section-intro">
++      Administrators configure the MFA policy directly from the XWiki Administration section, without editing configuration files for day-to-day policy changes.
++    </p>
--        <p>
--          The extension is especially useful for protecting administrator accounts, remote users,
--          private knowledge bases and customer or partner portals.
--        </p>
--      </article>
++    <div class="product-feature-grid">
++      #foreach ($entry in $adminControlItems)
++        <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>
--      <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, MFA rollout and compliance readiness</li>
--        </ul>
--      </aside>
++          <p>$entry.content</p>
++        </article>
++      #end
      </div>
++
++{{/html}}
++
++{{gallery}}
++[[image:mfa-admin-configuration.png]]
++{{/gallery}}
++
++{{html clean="false"}}
++
++    <p class="product-gallery-caption">
++      Administration configuration for requiring MFA, setting the authenticator issuer name, recovery-code count and trusted-device duration.
++    </p>
    </div>
  </section>
--<section aria-labelledby="admin-experience-title">
++<section class="product-section-muted" aria-labelledby="admin-visibility-title">
    <div class="container">
--    <h2 id="admin-experience-title">Administrator configuration and monitoring</h2>
++    <h2 id="admin-visibility-title">Administration overview and monitoring</h2>
      <p class="section-intro">
--      Administrators can configure the policy, define recovery options and monitor adoption
--      from the XWiki Administration section.
++      The administration overview helps teams understand MFA adoption and identify users who still need to complete setup or maintain recovery options.
      </p>
      <div class="product-feature-grid">
--      #foreach ($entry in $adminExperienceItems)
++      #foreach ($entry in $adminVisibilityItems)
          <article class="product-feature">
            <div class="card-heading">
              <div class="feature-icon">
@@ -232,7 +232,6 @@
  {{/html}}
  {{gallery}}
--[[image:mfa-admin-configuration.png]]
  [[image:mfa-admin-overview.png]]
  [[image:mfa-admin-full.png]]
  {{/gallery}}
@@ -240,22 +240,21 @@
  {{html clean="false"}}
      <p class="product-gallery-caption">
--      Administration screens for configuring the policy and reviewing adoption across users.
++      MFA adoption indicators and a filterable user overview for administrators.
      </p>
    </div>
  </section>
--<section class="product-section-muted" aria-labelledby="user-experience-title">
++<section aria-labelledby="user-adoption-title">
    <div class="container">
--    <h2 id="user-experience-title">User setup and login verification</h2>
++    <h2 id="user-adoption-title">User setup and adoption</h2>
      <p class="section-intro">
--      Users can configure the authenticator app from their profile or during the enforced setup flow,
--      then verify future logins with a generated code.
++      Users can configure MFA themselves by scanning a QR code or entering the setup information manually in their authenticator application.
      </p>
      <div class="product-feature-grid">
--      #foreach ($entry in $userExperienceItems)
++      #foreach ($entry in $userAdoptionItems)
          <article class="product-feature">
            <div class="card-heading">
              <div class="feature-icon">
@@ -274,27 +274,26 @@
  {{gallery}}
  [[image:mfa-user-setup-qr.png]]
  [[image:mfa-login-verification-setup.png]]
--[[image:mfa-login-verification-code.png]]
  {{/gallery}}
  {{html clean="false"}}
      <p class="product-gallery-caption">
--      User setup, enforced configuration and login verification screens.
++      Profile-based setup and enforced setup during login when MFA is required.
      </p>
    </div>
  </section>
--<section aria-labelledby="self-service-title">
++<section class="product-section-muted" aria-labelledby="login-protection-title">
    <div class="container">
--    <h2 id="self-service-title">Recovery codes and trusted devices</h2>
++    <h2 id="login-protection-title">Login protection</h2>
      <p class="section-intro">
--      Recovery codes and trusted devices help balance stronger access protection with a smoother user experience.
++      After MFA is configured, XWiki asks for a verification code after the normal username and password step.
      </p>
      <div class="product-feature-grid">
--      #foreach ($entry in $selfServiceItems)
++      #foreach ($entry in $loginProtectionItems)
          <article class="product-feature">
            <div class="card-heading">
              <div class="feature-icon">
@@ -311,31 +311,27 @@
  {{/html}}
  {{gallery}}
--[[image:mfa-user-profile-overview.png]]
--[[image:mfa-recovery-codes-not-generated.png]]
--[[image:mfa-recovery-codes-generated.png]]
--[[image:mfa-trusted-devices.png]]
--[[image:mfa-user-profile-full.png]]
++[[image:mfa-login-verification-code.png]]
  {{/gallery}}
  {{html clean="false"}}
      <p class="product-gallery-caption">
--      User profile screens for recovery codes, trusted devices and self-service management.
++      Verification screen displayed after the standard XWiki username and password login.
      </p>
    </div>
  </section>
--<section class="product-section-muted" aria-labelledby="admin-support-title">
++<section aria-labelledby="continuity-title">
    <div class="container">
--    <h2 id="admin-support-title">Administrator support and user recovery</h2>
++    <h2 id="continuity-title">Recovery codes and trusted devices</h2>
      <p class="section-intro">
--      Administrators can help users recover from lost devices or restart setup when needed.
++      Recovery codes and trusted devices help balance stronger access protection with practical day-to-day usability.
      </p>
      <div class="product-feature-grid">
--      #foreach ($entry in $adminSupportItems)
++      #foreach ($entry in $continuityItems)
          <article class="product-feature">
            <div class="card-heading">
              <div class="feature-icon">
@@ -352,88 +352,59 @@
  {{/html}}
  {{gallery}}
--[[image:mfa-admin-user-management.png]]
++[[image:mfa-recovery-codes-not-generated.png]]
++[[image:mfa-recovery-codes-generated.png]]
++[[image:mfa-trusted-devices.png]]
++[[image:mfa-user-profile-overview.png]]
++[[image:mfa-user-profile-full.png]]
  {{/gallery}}
  {{html clean="false"}}
      <p class="product-gallery-caption">
--      Administrator view for checking and resetting a user setup.
++      User profile screens for recovery-code generation, trusted-device review and MFA self-service management.
      </p>
    </div>
  </section>
--<section aria-labelledby="faq-title">
++<section class="product-section-muted" aria-labelledby="admin-support-title">
    <div class="container">
--    <h2 id="faq-title">Frequently asked questions</h2>
++    <h2 id="admin-support-title">Administrator support and user recovery</h2>
      <p class="section-intro">
--      Common questions about how the extension works, how users configure it and how administrators can manage rollout and recovery.
++      Administrators can help users recover from lost devices or restart MFA setup when needed.
      </p>
--    <div class="resource-content">
--      <details class="resource-faq-item">
--        <summary>Does this extension replace the standard XWiki login?</summary>
--        <p>
--          No. Users still sign in with their normal XWiki username and password. The extension adds
--          an additional verification step after the standard login check.
--        </p>
--      </details>
++    <div class="product-feature-grid">
++      #foreach ($entry in $adminSupportItems)
++        <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>
--      <details class="resource-faq-item">
--        <summary>Which verification method is used?</summary>
--        <p>
--          Users verify access with time-based codes generated by an authenticator application.
--          The setup page provides a QR code and a manual setup key.
--        </p>
--      </details>
++          <p>$entry.content</p>
++        </article>
++      #end
++    </div>
--      <details class="resource-faq-item">
--        <summary>Can the second verification step be required for all users?</summary>
--        <p>
--          Yes. Administrators can make the verification step optional or required for all users
--          from the XWiki Administration section.
--        </p>
--      </details>
++{{/html}}
--      <details class="resource-faq-item">
--        <summary>What happens if a user loses access to the authenticator app?</summary>
--        <p>
--          Recovery codes can provide backup access when enabled. Administrators can also reset
--          the user setup so the configuration process can be restarted.
--        </p>
--      </details>
++{{gallery}}
++[[image:mfa-admin-user-management.png]]
++{{/gallery}}
--      <details class="resource-faq-item">
--        <summary>Can trusted browsers or devices be disabled?</summary>
--        <p>
--          Yes. Administrators can configure how long trusted devices remain valid. Setting the
--          trusted-device duration to 0 disables this option.
--        </p>
--      </details>
++{{html clean="false"}}
--      <details class="resource-faq-item">
--        <summary>Is this only a basic 2FA login-code screen?</summary>
--        <p>
--          No. The main login mechanism is two-factor authentication, but the application also includes
--          features needed for a safer organization-wide rollout: enforcement policy, recovery codes,
--          trusted devices, user self-service, administrator monitoring and administrator reset actions.
--        </p>
--      </details>
--
--      <details class="resource-faq-item">
--        <summary>Is this enough for compliance on its own?</summary>
--        <p>
--          No. This extension provides an important access-protection control, but it should be part
--          of a broader security and compliance approach that includes permissions, upgrades,
--          infrastructure, monitoring and operational procedures.
--        </p>
--      </details>
--    </div>
++    <p class="product-gallery-caption">
++      Administrator view for checking and resetting a user MFA setup.
++    </p>
    </div>
  </section>
--<section class="product-section-muted" aria-labelledby="rollout-title">
++<section aria-labelledby="rollout-title">
    <div class="container">
      <div class="product-layout">
        <article class="product-summary-card">
@@ -440,9 +440,8 @@
          <h2 id="rollout-title">Rollout recommendations</h2>
          <p>
--          For a smooth rollout, start with a small administrator or pilot group before requiring
--          the additional verification step for everyone. This helps validate the configuration,
--          prepare user communication and reduce support issues.
++          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.
          </p>
          <ol class="process-list">
@@ -466,7 +466,7 @@
            <li>XWiki version</li>
            <li>Single wiki or wiki farm with subwikis</li>
            <li>Current authentication setup</li>
--          <li>Optional or required rollout policy</li>
++          <li>Optional or globally required MFA policy</li>
            <li>Trusted-device policy</li>
            <li>Recovery-code policy</li>
            <li>Rollout communication needs</li>
@@ -482,7 +482,7 @@
        <h2 id="cta-title">Interested in using this extension?</h2>
        <p>
--        Send a short message with your XWiki version, current authentication setup and rollout goal.
++        Send a short message with your XWiki version, current authentication setup and MFA rollout goal.
        </p>
        <a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Contact Agnease</a>