Skip to Content
Last modified by Alex Cotiuga on 2026/07/13 06:59
From version 30.7
edited by Alex Cotiuga
on 2026/07/13 06:59
Change comment: There is no comment for this version
To version 24.1
edited by Alex Cotiuga
on 2026/06/24 16:04
Change comment: Rollback to version 23.10

Summary

Details

Page properties
Default language
... ... @@ -1,0 +1,1 @@
1 +en
Hidden
... ... @@ -1,1 +1,1 @@
1 -true
1 +false
Content
... ... @@ -1,5 +1,6 @@
1 1  {{velocity}}
2 2  #set ($discard = $xwiki.ssx.use('PublicWebSite.WebHome'))
3 +#set ($discard = $xwiki.ssx.use('products.WebHome'))
3 3  
4 4  #set ($mainCapabilityItems = [{
5 5   'title': 'Second verification step',
... ... @@ -16,9 +16,9 @@
16 16  }])
17 17  
18 18  #set ($adminExperienceItems = [{
19 - 'title': 'Rollout policy',
20 + 'title': 'MFA policy',
20 20   'icon': 'cog',
21 - 'content': 'Make additional verification optional at first or required for all users from the XWiki Administration section.'
22 + 'content': 'Make MFA optional or required for all users from the XWiki Administration section.'
22 22  },{
23 23   'title': 'Configuration options',
24 24   'icon': 'sliders',
... ... @@ -26,17 +26,17 @@
26 26  },{
27 27   'title': 'Administration overview',
28 28   'icon': 'table',
29 - 'content': 'Review adoption with summary indicators and a filterable Live Data table.'
30 + 'content': 'Review MFA adoption with summary indicators and a filterable Live Data table.'
30 30  }])
31 31  
32 32  #set ($userExperienceItems = [{
33 33   'title': 'Self-service setup',
34 34   'icon': 'qrcode',
35 - 'content': 'Users configure the second verification step from their profile by scanning a QR code or entering the setup key manually.'
36 + 'content': 'Users configure MFA from their profile by scanning a QR code or entering the setup key manually.'
36 36  },{
37 37   'title': 'Login verification',
38 38   'icon': 'sign-in',
39 - 'content': 'After the normal login, users enter the verification code generated by their authenticator app.'
40 + 'content': 'After the normal login, users enter the code generated by their authenticator app.'
40 40  },{
41 41   'title': 'Trusted browser option',
42 42   'icon': 'desktop',
... ... @@ -54,21 +54,21 @@
54 54  },{
55 55   'title': 'Profile management',
56 56   'icon': 'user',
57 - 'content': 'Users can review status, generate recovery codes, manage trusted devices and reset their setup.'
58 + 'content': 'Users can review MFA status, generate recovery codes, manage trusted devices and reset MFA.'
58 58  }])
59 59  
60 60  #set ($adminSupportItems = [{
61 - 'title': 'User status',
62 + 'title': 'User MFA status',
62 62   'icon': 'user',
63 - 'content': 'Administrators can open a user profile and check the verification status for that account.'
64 + 'content': 'Administrators can open a user profile and check the MFA status for that account.'
64 64  },{
65 - 'title': 'Setup reset',
66 + 'title': 'MFA reset',
66 66   'icon': 'refresh',
67 - 'content': 'Administrators can reset the setup when a user needs to restart the configuration process.'
68 + 'content': 'Administrators can reset MFA when a user needs to restart the configuration process.'
68 68  },{
69 69   'title': 'Controlled recovery',
70 70   'icon': 'unlock-alt',
71 - 'content': 'Resetting the setup removes the authenticator configuration, recovery codes and trusted devices for that user.'
72 + 'content': 'Resetting MFA removes the authenticator setup, recovery codes and trusted devices for that user.'
72 72  }])
73 73  
74 74  #set ($rolloutItems = [{
... ... @@ -75,17 +75,17 @@
75 75   'title': 'Start with a pilot group',
76 76   'content': 'Test the extension with administrators or a small user group before enabling it widely.'
77 77  },{
78 - 'title': 'Define the rollout policy',
79 - 'content': 'Decide whether additional verification should be optional at first or required for all users.'
79 + 'title': 'Define the MFA policy',
80 + 'content': 'Decide whether MFA should be optional at first or required for all users.'
80 80  },{
81 81   'title': 'Configure recovery options',
82 82   'content': 'Choose the number of recovery codes and whether trusted devices should be allowed.'
83 83  },{
84 84   'title': 'Inform users',
85 - 'content': 'Explain how users configure the authenticator app, save recovery codes and manage trusted devices.'
86 + 'content': 'Explain how users configure MFA, save recovery codes and manage trusted devices.'
86 86  },{
87 87   'title': 'Monitor adoption',
88 - 'content': 'Use the administration overview to identify users who still need to configure protection.'
89 + 'content': 'Use the administration overview to identify users who still need to configure MFA.'
89 89  }])
90 90  
91 91  {{html clean="false"}}
... ... @@ -94,25 +94,19 @@
94 94   <div class="container hero-inner">
95 95   <div class="hero-kicker">
96 96   <i class="fa fa-lock" aria-hidden="true"></i>
97 - XWiki 2FA with MFA rollout support
98 + XWiki 2FA and MFA
98 98   </div>
99 99  
100 - <h1 id="product-title">XWiki Two-Factor Authentication</h1>
101 + <h1 id="product-title">XWiki Two-Factor Authentication (2FA/MFA)</h1>
101 101  
102 102   <p class="lead">
103 - Protect XWiki logins with authenticator app verification, recovery codes,
104 - trusted devices and administration controls for a safer rollout.
104 + Protect XWiki logins with a second verification step using authenticator app codes,
105 + recovery codes and trusted devices.
105 105   </p>
106 106  
107 - <ul class="benefits">
108 - <li><strong>Extension from €75/year</strong></li>
109 - <li><strong>Basic setup from €150</strong></li>
110 - <li>MFA rollout support available</li>
111 - </ul>
112 -
113 113   <div class="hero-actions">
114 114   <a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Ask about this extension</a>
115 - <a class="btn btn-secondary" href="$xwiki.getURL('pricing.WebHome')#common-packages">View MFA setup price</a>
110 + <a class="btn btn-secondary" href="$xwiki.getURL('products.WebHome')">View all products</a>
116 116   </div>
117 117   </div>
118 118  </section>
... ... @@ -124,15 +124,15 @@
124 124   <h2 id="overview-title">Two-factor authentication built into XWiki</h2>
125 125  
126 126   <p>
127 - XWiki Two-Factor Authentication adds an additional verification step to the standard
128 - XWiki login flow. Users continue to sign in with their normal username and password,
129 - then confirm access with a time-based code from an authenticator application.
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.
130 130   </p>
131 131  
132 132   <p>
133 - The application has evolved beyond a simple login-code screen. It supports global
134 - enforcement, recovery codes, trusted devices, user self-service, administrator
135 - reset actions and an overview for monitoring adoption.
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.
136 136   </p>
137 137   </article>
138 138  
... ... @@ -141,7 +141,7 @@
141 141   <ul>
142 142   <li>Works with the standard XWiki login flow</li>
143 143   <li>Supports TOTP authenticator applications</li>
144 - <li>Can require additional verification for all users</li>
139 + <li>Can require MFA for all users</li>
145 145   <li>Includes one-time recovery codes</li>
146 146   <li>Can remember trusted browsers or devices</li>
147 147   <li>Includes user self-service controls</li>
... ... @@ -157,8 +157,7 @@
157 157   <h2 id="capabilities-title">Main capabilities</h2>
158 158  
159 159   <p class="section-intro">
160 - A focused set of authentication protection features for stronger XWiki account security
161 - without replacing the familiar login experience.
155 + A focused set of MFA features for stronger XWiki account protection without replacing the familiar login experience.
162 162   </p>
163 163  
164 164   <div class="product-feature-grid">
... ... @@ -186,7 +186,7 @@
186 186  
187 187   <p>
188 188   Many organizations use XWiki to store internal documentation, procedures, operational
189 - knowledge and business-critical information. Adding an additional authentication factor helps
183 + knowledge and business-critical information. Adding a second authentication factor helps
190 190   reduce the risk of account compromise when a password is exposed or reused.
191 191   </p>
192 192  
... ... @@ -216,8 +216,7 @@
216 216   <h2 id="admin-experience-title">Administrator configuration and monitoring</h2>
217 217  
218 218   <p class="section-intro">
219 - Administrators can configure the policy, define recovery options and monitor adoption
220 - from the XWiki Administration section.
213 + Administrators can configure the MFA policy, define recovery options and monitor adoption from the XWiki Administration section.
221 221   </p>
222 222  
223 223   <div class="product-feature-grid">
... ... @@ -246,7 +246,7 @@
246 246  {{html clean="false"}}
247 247  
248 248   <p class="product-gallery-caption">
249 - Administration screens for configuring the policy and reviewing adoption across users.
242 + Administration screens for configuring MFA and reviewing MFA adoption across users.
250 250   </p>
251 251   </div>
252 252  </section>
... ... @@ -256,8 +256,7 @@
256 256   <h2 id="user-experience-title">User setup and login verification</h2>
257 257  
258 258   <p class="section-intro">
259 - Users can configure the authenticator app from their profile or during the enforced setup flow,
260 - then verify future logins with a generated code.
252 + Users can configure MFA from their profile or during the enforced setup flow, then verify future logins with their authenticator app.
261 261   </p>
262 262  
263 263   <div class="product-feature-grid">
... ... @@ -286,7 +286,7 @@
286 286  {{html clean="false"}}
287 287  
288 288   <p class="product-gallery-caption">
289 - User setup, enforced configuration and login verification screens.
281 + User setup, enforced MFA configuration and login verification screens.
290 290   </p>
291 291   </div>
292 292  </section>
... ... @@ -327,7 +327,7 @@
327 327  {{html clean="false"}}
328 328  
329 329   <p class="product-gallery-caption">
330 - User profile screens for recovery codes, trusted devices and self-service management.
322 + User profile screens for recovery codes, trusted devices and MFA self-service management.
331 331   </p>
332 332   </div>
333 333  </section>
... ... @@ -337,7 +337,7 @@
337 337   <h2 id="admin-support-title">Administrator support and user recovery</h2>
338 338  
339 339   <p class="section-intro">
340 - Administrators can help users recover from lost devices or restart setup when needed.
332 + Administrators can help users recover from lost devices or restart MFA setup when needed.
341 341   </p>
342 342  
343 343   <div class="product-feature-grid">
... ... @@ -364,91 +364,20 @@
364 364  {{html clean="false"}}
365 365  
366 366   <p class="product-gallery-caption">
367 - Administrator view for checking and resetting a user setup.
359 + Administrator view for checking and resetting a user MFA setup.
368 368   </p>
369 369   </div>
370 370  </section>
371 371  
372 -<section aria-labelledby="faq-title">
364 +<section aria-labelledby="rollout-title">
373 373   <div class="container">
374 - <h2 id="faq-title">Frequently asked questions</h2>
375 -
376 - <p class="section-intro">
377 - Common questions about how the extension works, how users configure it and how administrators can manage rollout and recovery.
378 - </p>
379 -
380 - <div class="resource-content">
381 - <details class="resource-faq-item">
382 - <summary>Does this extension replace the standard XWiki login?</summary>
383 - <p>
384 - No. Users still sign in with their normal XWiki username and password. The extension adds
385 - an additional verification step after the standard login check.
386 - </p>
387 - </details>
388 -
389 - <details class="resource-faq-item">
390 - <summary>Which verification method is used?</summary>
391 - <p>
392 - Users verify access with time-based codes generated by an authenticator application.
393 - The setup page provides a QR code and a manual setup key.
394 - </p>
395 - </details>
396 -
397 - <details class="resource-faq-item">
398 - <summary>Can the second verification step be required for all users?</summary>
399 - <p>
400 - Yes. Administrators can make the verification step optional or required for all users
401 - from the XWiki Administration section.
402 - </p>
403 - </details>
404 -
405 - <details class="resource-faq-item">
406 - <summary>What happens if a user loses access to the authenticator app?</summary>
407 - <p>
408 - Recovery codes can provide backup access when enabled. Administrators can also reset
409 - the user setup so the configuration process can be restarted.
410 - </p>
411 - </details>
412 -
413 - <details class="resource-faq-item">
414 - <summary>Can trusted browsers or devices be disabled?</summary>
415 - <p>
416 - Yes. Administrators can configure how long trusted devices remain valid. Setting the
417 - trusted-device duration to 0 disables this option.
418 - </p>
419 - </details>
420 -
421 - <details class="resource-faq-item">
422 - <summary>Is this only a basic 2FA login-code screen?</summary>
423 - <p>
424 - No. The main login mechanism is two-factor authentication, but the application also includes
425 - features needed for a safer organization-wide rollout: enforcement policy, recovery codes,
426 - trusted devices, user self-service, administrator monitoring and administrator reset actions.
427 - </p>
428 - </details>
429 -
430 - <details class="resource-faq-item">
431 - <summary>Is this enough for compliance on its own?</summary>
432 - <p>
433 - No. This extension provides an important access-protection control, but it should be part
434 - of a broader security and compliance approach that includes permissions, upgrades,
435 - infrastructure, monitoring and operational procedures.
436 - </p>
437 - </details>
438 - </div>
439 - </div>
440 -</section>
441 -
442 -<section class="product-section-muted" aria-labelledby="rollout-title">
443 - <div class="container">
444 444   <div class="product-layout">
445 445   <article class="product-summary-card">
446 446   <h2 id="rollout-title">Rollout recommendations</h2>
447 447  
448 448   <p>
449 - For a smooth rollout, start with a small administrator or pilot group before requiring
450 - the additional verification step for everyone. This helps validate the configuration,
451 - prepare user communication and reduce support issues.
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.
452 452   </p>
453 453  
454 454   <ol class="process-list">
... ... @@ -472,7 +472,7 @@
472 472   <li>XWiki version</li>
473 473   <li>Single wiki or wiki farm with subwikis</li>
474 474   <li>Current authentication setup</li>
475 - <li>Optional or required rollout policy</li>
396 + <li>Optional or globally required MFA policy</li>
476 476   <li>Trusted-device policy</li>
477 477   <li>Recovery-code policy</li>
478 478   <li>Rollout communication needs</li>
... ... @@ -488,11 +488,10 @@
488 488   <h2 id="cta-title">Interested in using this extension?</h2>
489 489  
490 490   <p>
491 - Send a short message with your XWiki version, current authentication setup and rollout goal.
412 + Send a short message with your XWiki version, current authentication setup and MFA rollout goal.
492 492   </p>
493 493  
494 494   <a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Contact Agnease</a>
495 - <a class="btn btn-secondary" href="$xwiki.getURL('pricing.WebHome')#common-packages">View MFA setup price</a>
496 496   </div>
497 497   </div>
498 498  </section>
2fa-authenticator.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Admin
Size
... ... @@ -1,1 +1,0 @@
1 -1.1 MB
Content
mfa-admin-user-management.png
Size
... ... @@ -1,1 +1,1 @@
1 -90.8 KB
1 +26.9 KB
Content
Agnease.Code.SEODetailsClass[0]
metaDescription
... ... @@ -1,1 +1,1 @@
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.
1 +Agnease Multi‑Factor Authentication for XWiki adds secure login verification using authenticator app codes, email codes, combined verification, recovery codes, and trusted‑device remembering.
metaTitle
... ... @@ -1,1 +1,1 @@
1 -XWiki Two-Factor Authentication with 2FA and MFA Support | Agnease
1 +XWiki Multi‑Factor Authentication (MFA) with 2FA Support | Agnease