Skip to Content
Last modified by Agnease on 2026/06/24 16:39
From version 23.8
edited by Agnease
on 2026/06/24 15:55
Change comment: There is no comment for this version
To version 25.4
edited by Agnease
on 2026/06/24 16:14
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,6 +1,5 @@
1 1  {{velocity}}
2 2  #set ($discard = $xwiki.ssx.use('PublicWebSite.WebHome'))
3 -#set ($discard = $xwiki.ssx.use('products.WebHome'))
4 4  
5 5  #set ($mainCapabilityItems = [{
6 6   'title': 'Second verification step',
... ... @@ -17,9 +17,9 @@
17 17  }])
18 18  
19 19  #set ($adminExperienceItems = [{
20 - 'title': 'MFA policy',
19 + 'title': 'Rollout policy',
21 21   'icon': 'cog',
22 - 'content': 'Make MFA optional or required for all users from the XWiki Administration section.'
21 + 'content': 'Make additional verification optional at first or required for all users from the XWiki Administration section.'
23 23  },{
24 24   'title': 'Configuration options',
25 25   'icon': 'sliders',
... ... @@ -27,17 +27,17 @@
27 27  },{
28 28   'title': 'Administration overview',
29 29   'icon': 'table',
30 - 'content': 'Review MFA adoption with summary indicators and a filterable Live Data table.'
29 + 'content': 'Review adoption with summary indicators and a filterable Live Data table.'
31 31  }])
32 32  
33 33  #set ($userExperienceItems = [{
34 34   'title': 'Self-service setup',
35 35   'icon': 'qrcode',
36 - 'content': 'Users configure MFA from their profile by scanning a QR code or entering the setup key manually.'
35 + 'content': 'Users configure the second verification step from their profile by scanning a QR code or entering the setup key manually.'
37 37  },{
38 38   'title': 'Login verification',
39 39   'icon': 'sign-in',
40 - 'content': 'After the normal login, users enter the code generated by their authenticator app.'
39 + 'content': 'After the normal login, users enter the verification code generated by their authenticator app.'
41 41  },{
42 42   'title': 'Trusted browser option',
43 43   'icon': 'desktop',
... ... @@ -55,21 +55,21 @@
55 55  },{
56 56   'title': 'Profile management',
57 57   'icon': 'user',
58 - 'content': 'Users can review MFA status, generate recovery codes, manage trusted devices and reset MFA.'
57 + 'content': 'Users can review status, generate recovery codes, manage trusted devices and reset their setup.'
59 59  }])
60 60  
61 61  #set ($adminSupportItems = [{
62 - 'title': 'User MFA status',
61 + 'title': 'User status',
63 63   'icon': 'user',
64 - 'content': 'Administrators can open a user profile and check the MFA status for that account.'
63 + 'content': 'Administrators can open a user profile and check the verification status for that account.'
65 65  },{
66 - 'title': 'MFA reset',
65 + 'title': 'Setup reset',
67 67   'icon': 'refresh',
68 - 'content': 'Administrators can reset MFA when a user needs to restart the configuration process.'
67 + 'content': 'Administrators can reset the setup when a user needs to restart the configuration process.'
69 69  },{
70 70   'title': 'Controlled recovery',
71 71   'icon': 'unlock-alt',
72 - 'content': 'Resetting MFA removes the authenticator setup, recovery codes and trusted devices for that user.'
71 + 'content': 'Resetting the setup removes the authenticator configuration, recovery codes and trusted devices for that user.'
73 73  }])
74 74  
75 75  #set ($rolloutItems = [{
... ... @@ -76,17 +76,17 @@
76 76   'title': 'Start with a pilot group',
77 77   'content': 'Test the extension with administrators or a small user group before enabling it widely.'
78 78  },{
79 - 'title': 'Define the MFA policy',
80 - 'content': 'Decide whether MFA should be optional at first or required for all users.'
78 + 'title': 'Define the rollout policy',
79 + 'content': 'Decide whether additional verification should be optional at first or required for all users.'
81 81  },{
82 82   'title': 'Configure recovery options',
83 83   'content': 'Choose the number of recovery codes and whether trusted devices should be allowed.'
84 84  },{
85 85   'title': 'Inform users',
86 - 'content': 'Explain how users configure MFA, save recovery codes and manage trusted devices.'
85 + 'content': 'Explain how users configure the authenticator app, save recovery codes and manage trusted devices.'
87 87  },{
88 88   'title': 'Monitor adoption',
89 - 'content': 'Use the administration overview to identify users who still need to configure MFA.'
88 + 'content': 'Use the administration overview to identify users who still need to configure protection.'
90 90  }])
91 91  
92 92  {{html clean="false"}}
... ... @@ -95,14 +95,14 @@
95 95   <div class="container hero-inner">
96 96   <div class="hero-kicker">
97 97   <i class="fa fa-lock" aria-hidden="true"></i>
98 - XWiki 2FA and MFA
97 + XWiki 2FA with MFA rollout support
99 99   </div>
100 100  
101 - <h1 id="product-title">XWiki Two-Factor Authentication (2FA/MFA)</h1>
100 + <h1 id="product-title">XWiki Two-Factor Authentication</h1>
102 102  
103 103   <p class="lead">
104 - Protect XWiki logins with a second verification step using authenticator app codes,
105 - recovery codes and trusted devices.
103 + Protect XWiki logins with authenticator app verification, recovery codes,
104 + trusted devices and administration controls for a safer rollout.
106 106   </p>
107 107  
108 108   <div class="hero-actions">
... ... @@ -119,15 +119,15 @@
119 119   <h2 id="overview-title">Two-factor authentication built into XWiki</h2>
120 120  
121 121   <p>
122 - XWiki Two-Factor Authentication adds MFA support to the standard XWiki login flow.
123 - Users continue to sign in with their normal username and password, then confirm access
124 - with a time-based verification code from an authenticator application.
121 + XWiki Two-Factor Authentication adds an additional verification step to the standard
122 + XWiki login flow. Users continue to sign in with their normal username and password,
123 + then confirm access with a time-based code from an authenticator application.
125 125   </p>
126 126  
127 127   <p>
128 - The extension is designed for organizations that want stronger access protection for
129 - internal knowledge bases, intranets, documentation platforms, customer portals and other
130 - XWiki-based applications.
127 + The application has evolved beyond a simple login-code screen. It supports global
128 + enforcement, recovery codes, trusted devices, user self-service, administrator
129 + reset actions and an overview for monitoring adoption.
131 131   </p>
132 132   </article>
133 133  
... ... @@ -136,7 +136,7 @@
136 136   <ul>
137 137   <li>Works with the standard XWiki login flow</li>
138 138   <li>Supports TOTP authenticator applications</li>
139 - <li>Can require MFA for all users</li>
138 + <li>Can require additional verification for all users</li>
140 140   <li>Includes one-time recovery codes</li>
141 141   <li>Can remember trusted browsers or devices</li>
142 142   <li>Includes user self-service controls</li>
... ... @@ -152,7 +152,8 @@
152 152   <h2 id="capabilities-title">Main capabilities</h2>
153 153  
154 154   <p class="section-intro">
155 - A focused set of MFA features for stronger XWiki account protection without replacing the familiar login experience.
154 + A focused set of authentication protection features for stronger XWiki account security
155 + without replacing the familiar login experience.
156 156   </p>
157 157  
158 158   <div class="product-feature-grid">
... ... @@ -180,7 +180,7 @@
180 180  
181 181   <p>
182 182   Many organizations use XWiki to store internal documentation, procedures, operational
183 - knowledge and business-critical information. Adding a second authentication factor helps
183 + knowledge and business-critical information. Adding an additional authentication factor helps
184 184   reduce the risk of account compromise when a password is exposed or reused.
185 185   </p>
186 186  
... ... @@ -210,7 +210,8 @@
210 210   <h2 id="admin-experience-title">Administrator configuration and monitoring</h2>
211 211  
212 212   <p class="section-intro">
213 - Administrators can configure the MFA policy, define recovery options and monitor adoption from the XWiki Administration section.
213 + Administrators can configure the policy, define recovery options and monitor adoption
214 + from the XWiki Administration section.
214 214   </p>
215 215  
216 216   <div class="product-feature-grid">
... ... @@ -239,7 +239,7 @@
239 239  {{html clean="false"}}
240 240  
241 241   <p class="product-gallery-caption">
242 - Administration screens for configuring MFA and reviewing MFA adoption across users.
243 + Administration screens for configuring the policy and reviewing adoption across users.
243 243   </p>
244 244   </div>
245 245  </section>
... ... @@ -249,7 +249,8 @@
249 249   <h2 id="user-experience-title">User setup and login verification</h2>
250 250  
251 251   <p class="section-intro">
252 - Users can configure MFA from their profile or during the enforced setup flow, then verify future logins with their authenticator app.
253 + Users can configure the authenticator app from their profile or during the enforced setup flow,
254 + then verify future logins with a generated code.
253 253   </p>
254 254  
255 255   <div class="product-feature-grid">
... ... @@ -278,7 +278,7 @@
278 278  {{html clean="false"}}
279 279  
280 280   <p class="product-gallery-caption">
281 - User setup, enforced MFA configuration and login verification screens.
283 + User setup, enforced configuration and login verification screens.
282 282   </p>
283 283   </div>
284 284  </section>
... ... @@ -319,7 +319,7 @@
319 319  {{html clean="false"}}
320 320  
321 321   <p class="product-gallery-caption">
322 - User profile screens for recovery codes, trusted devices and MFA self-service management.
324 + User profile screens for recovery codes, trusted devices and self-service management.
323 323   </p>
324 324   </div>
325 325  </section>
... ... @@ -329,7 +329,7 @@
329 329   <h2 id="admin-support-title">Administrator support and user recovery</h2>
330 330  
331 331   <p class="section-intro">
332 - Administrators can help users recover from lost devices or restart MFA setup when needed.
334 + Administrators can help users recover from lost devices or restart setup when needed.
333 333   </p>
334 334  
335 335   <div class="product-feature-grid">
... ... @@ -356,20 +356,91 @@
356 356  {{html clean="false"}}
357 357  
358 358   <p class="product-gallery-caption">
359 - Administrator view for checking and resetting a user MFA setup.
361 + Administrator view for checking and resetting a user setup.
360 360   </p>
361 361   </div>
362 362  </section>
363 363  
364 -<section aria-labelledby="rollout-title">
366 +<section aria-labelledby="faq-title">
365 365   <div class="container">
368 + <h2 id="faq-title">Frequently asked questions</h2>
369 +
370 + <p class="section-intro">
371 + Common questions about how the extension works, how users configure it and how administrators can manage rollout and recovery.
372 + </p>
373 +
374 + <div class="resource-content">
375 + <details class="resource-faq-item">
376 + <summary>Does this extension replace the standard XWiki login?</summary>
377 + <p>
378 + No. Users still sign in with their normal XWiki username and password. The extension adds
379 + an additional verification step after the standard login check.
380 + </p>
381 + </details>
382 +
383 + <details class="resource-faq-item">
384 + <summary>Which verification method is used?</summary>
385 + <p>
386 + Users verify access with time-based codes generated by an authenticator application.
387 + The setup page provides a QR code and a manual setup key.
388 + </p>
389 + </details>
390 +
391 + <details class="resource-faq-item">
392 + <summary>Can the second verification step be required for all users?</summary>
393 + <p>
394 + Yes. Administrators can make the verification step optional or required for all users
395 + from the XWiki Administration section.
396 + </p>
397 + </details>
398 +
399 + <details class="resource-faq-item">
400 + <summary>What happens if a user loses access to the authenticator app?</summary>
401 + <p>
402 + Recovery codes can provide backup access when enabled. Administrators can also reset
403 + the user setup so the configuration process can be restarted.
404 + </p>
405 + </details>
406 +
407 + <details class="resource-faq-item">
408 + <summary>Can trusted browsers or devices be disabled?</summary>
409 + <p>
410 + Yes. Administrators can configure how long trusted devices remain valid. Setting the
411 + trusted-device duration to 0 disables this option.
412 + </p>
413 + </details>
414 +
415 + <details class="resource-faq-item">
416 + <summary>Is this only a basic 2FA login-code screen?</summary>
417 + <p>
418 + No. The main login mechanism is two-factor authentication, but the application also includes
419 + features needed for a safer organization-wide rollout: enforcement policy, recovery codes,
420 + trusted devices, user self-service, administrator monitoring and administrator reset actions.
421 + </p>
422 + </details>
423 +
424 + <details class="resource-faq-item">
425 + <summary>Is this enough for compliance on its own?</summary>
426 + <p>
427 + No. This extension provides an important access-protection control, but it should be part
428 + of a broader security and compliance approach that includes permissions, upgrades,
429 + infrastructure, monitoring and operational procedures.
430 + </p>
431 + </details>
432 + </div>
433 + </div>
434 +</section>
435 +
436 +<section class="product-section-muted" aria-labelledby="rollout-title">
437 + <div class="container">
366 366   <div class="product-layout">
367 367   <article class="product-summary-card">
368 368   <h2 id="rollout-title">Rollout recommendations</h2>
369 369  
370 370   <p>
371 - For a smooth rollout, start with a small administrator or pilot group before requiring MFA for everyone.
372 - This helps validate the configuration, prepare user communication and reduce support issues.
443 + For a smooth rollout, start with a small administrator or pilot group before requiring
444 + the additional verification step for everyone. This helps validate the configuration,
445 + prepare user communication and reduce support issues.
373 373   </p>
374 374  
375 375   <ol class="process-list">
... ... @@ -393,7 +393,7 @@
393 393   <li>XWiki version</li>
394 394   <li>Single wiki or wiki farm with subwikis</li>
395 395   <li>Current authentication setup</li>
396 - <li>Optional or globally required MFA policy</li>
469 + <li>Optional or required rollout policy</li>
397 397   <li>Trusted-device policy</li>
398 398   <li>Recovery-code policy</li>
399 399   <li>Rollout communication needs</li>
... ... @@ -409,7 +409,7 @@
409 409   <h2 id="cta-title">Interested in using this extension?</h2>
410 410  
411 411   <p>
412 - Send a short message with your XWiki version, current authentication setup and MFA rollout goal.
485 + Send a short message with your XWiki version, current authentication setup and rollout goal.
413 413   </p>
414 414  
415 415   <a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Contact Agnease</a>
Agnease.Code.SEODetailsClass[0]
metaTitle
... ... @@ -1,1 +1,1 @@
1 -XWiki Multi‑Factor Authentication (MFA) with 2FA Support | Agnease
1 +XWiki Two-Factor Authentication with 2FA and MFA Support | Agnease