Skip to Content
Last modified by Alex Cotiuga on 2026/07/13 06:59
From version 30.5
edited by Alex Cotiuga
on 2026/07/13 06:57
Change comment: There is no comment for this version
To version 1.15
edited by Alex Cotiuga
on 2026/05/22 03:46
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -XWiki Two-Factor Authentication
1 +xwiki-two-factor-authentication
Default language
... ... @@ -1,0 +1,1 @@
1 +en
Hidden
... ... @@ -1,1 +1,1 @@
1 -true
1 +false
Content
... ... @@ -1,117 +1,29 @@
1 1  {{velocity}}
2 2  #set ($discard = $xwiki.ssx.use('PublicWebSite.WebHome'))
3 -
4 -#set ($mainCapabilityItems = [{
5 - 'title': 'Second verification step',
6 - 'icon': 'key',
7 - 'content': 'Add an additional verification screen after the normal XWiki username and password login.'
8 -},{
9 - 'title': 'Authenticator app codes',
10 - 'icon': 'mobile',
11 - 'content': 'Let users verify access with time-based TOTP codes generated by authenticator applications.'
12 -},{
13 - 'title': 'Recovery and trusted devices',
14 - 'icon': 'shield',
15 - 'content': 'Provide backup access with recovery codes and reduce repeated prompts on trusted browsers.'
16 -}])
17 -
18 -#set ($adminExperienceItems = [{
19 - 'title': 'Rollout policy',
20 - 'icon': 'cog',
21 - 'content': 'Make additional verification optional at first or required for all users from the XWiki Administration section.'
22 -},{
23 - 'title': 'Configuration options',
24 - 'icon': 'sliders',
25 - 'content': 'Set the authenticator issuer name, recovery-code count and trusted-device duration.'
26 -},{
27 - 'title': 'Administration overview',
28 - 'icon': 'table',
29 - 'content': 'Review adoption with summary indicators and a filterable Live Data table.'
30 -}])
31 -
32 -#set ($userExperienceItems = [{
33 - 'title': 'Self-service setup',
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 -},{
37 - 'title': 'Login verification',
38 - 'icon': 'sign-in',
39 - 'content': 'After the normal login, users enter the verification code generated by their authenticator app.'
40 -},{
41 - 'title': 'Trusted browser option',
42 - 'icon': 'desktop',
43 - 'content': 'Users can trust the current browser for the configured duration after successful verification.'
44 -}])
45 -
46 -#set ($selfServiceItems = [{
47 - 'title': 'Recovery codes',
48 - 'icon': 'life-ring',
49 - 'content': 'Recovery codes provide backup access when a user loses access to the authenticator application.'
50 -},{
51 - 'title': 'Trusted devices',
52 - 'icon': 'desktop',
53 - 'content': 'Trusted devices can be reviewed and removed from the user profile.'
54 -},{
55 - 'title': 'Profile management',
56 - 'icon': 'user',
57 - 'content': 'Users can review status, generate recovery codes, manage trusted devices and reset their setup.'
58 -}])
59 -
60 -#set ($adminSupportItems = [{
61 - 'title': 'User status',
62 - 'icon': 'user',
63 - 'content': 'Administrators can open a user profile and check the verification status for that account.'
64 -},{
65 - 'title': 'Setup reset',
66 - 'icon': 'refresh',
67 - 'content': 'Administrators can reset the setup when a user needs to restart the configuration process.'
68 -},{
69 - 'title': 'Controlled recovery',
70 - 'icon': 'unlock-alt',
71 - 'content': 'Resetting the setup removes the authenticator configuration, recovery codes and trusted devices for that user.'
72 -}])
73 -
74 -#set ($rolloutItems = [{
75 - 'title': 'Start with a pilot group',
76 - 'content': 'Test the extension with administrators or a small user group before enabling it widely.'
77 -},{
78 - 'title': 'Define the rollout policy',
79 - 'content': 'Decide whether additional verification should be optional at first or required for all users.'
80 -},{
81 - 'title': 'Configure recovery options',
82 - 'content': 'Choose the number of recovery codes and whether trusted devices should be allowed.'
83 -},{
84 - 'title': 'Inform users',
85 - 'content': 'Explain how users configure the authenticator app, save recovery codes and manage trusted devices.'
86 -},{
87 - 'title': 'Monitor adoption',
88 - 'content': 'Use the administration overview to identify users who still need to configure protection.'
89 -}])
90 -
3 +#set ($discard = $xwiki.ssx.use('products.WebHome'))
91 91  {{html clean="false"}}
92 92  
93 -<section class="hero hero-centered" aria-labelledby="product-title">
6 +<section class="hero hero-centered product-hero" aria-labelledby="product-title">
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
10 + XWiki security extension
98 98   </div>
99 99  
100 100   <h1 id="product-title">XWiki Two-Factor Authentication</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.
16 + Add a second verification step to the standard XWiki login flow.
105 105   </p>
106 106  
107 - <div class="product-card-kicker">
108 - <i class="fa fa-tag" aria-hidden="true"></i>
109 - Extension from €95/year · Basic setup from €150
110 - </div>
19 + <p class="hero-support">
20 + This XWiki MFA / 2FA extension adds an additional verification step after the standard username and password login.
21 + Users can verify access with authenticator app codes, email-delivered one-time codes, or a combined setup requiring both methods.
22 + </p>
111 111  
112 112   <div class="hero-actions">
113 113   <a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Ask about this extension</a>
114 - <a class="btn btn-secondary" href="$xwiki.getURL('pricing.WebHome')#common-packages">View MFA setup price</a>
26 + <a class="btn btn-secondary" href="$xwiki.getURL('products.WebHome')">View all products</a>
115 115   </div>
116 116   </div>
117 117  </section>
... ... @@ -120,19 +120,25 @@
120 120   <div class="container">
121 121   <div class="product-layout">
122 122   <article class="product-summary-card">
123 - <h2 id="overview-title">Two-factor authentication built into XWiki</h2>
35 + <h2 id="overview-title">Stronger login protection for XWiki</h2>
124 124  
125 125   <p>
126 - XWiki Two-Factor Authentication adds an additional verification step to the standard
127 - XWiki login flow. Users continue to sign in with their normal username and password,
128 - then confirm access with a time-based code from an authenticator application.
38 + The XWiki MFA / Two-Factor Authentication extension adds additional verification after the standard
39 + XWiki username and password login. It strengthens account protection without replacing the familiar
40 + XWiki authentication flow.
129 129   </p>
130 130  
131 131   <p>
132 - The application has evolved beyond a simple login-code screen. It supports global
133 - enforcement, recovery codes, trusted devices, user self-service, administrator
134 - reset actions and an overview for monitoring adoption.
44 + The extension supports authenticator app codes using TOTP, email-delivered one-time verification codes,
45 + and stricter configurations where both verification methods are required. This allows organizations to
46 + choose between a simpler 2FA setup or a stronger multi-step MFA policy.
135 135   </p>
48 +
49 + <p>
50 + Trusted clients can also be remembered for a configured period. In practice, this means that a known
51 + browser or device can avoid repeated MFA prompts, while new or untrusted clients still require the
52 + configured verification steps.
53 + </p>
136 136   </article>
137 137  
138 138   <aside class="product-info-card" aria-labelledby="quick-facts-title">
... ... @@ -139,12 +139,12 @@
139 139   <h3 id="quick-facts-title">Quick facts</h3>
140 140   <ul>
141 141   <li>Works with the standard XWiki login flow</li>
142 - <li>Supports TOTP authenticator applications</li>
143 - <li>Can require additional verification for all users</li>
144 - <li>Includes one-time recovery codes</li>
145 - <li>Can remember trusted browsers or devices</li>
146 - <li>Includes user self-service controls</li>
147 - <li>Includes an administration overview</li>
60 + <li>Supports authenticator app codes using TOTP</li>
61 + <li>Supports email-delivered one-time verification codes</li>
62 + <li>Can require app code and email code together for stricter MFA</li>
63 + <li>Can remember trusted browsers or devices beyond the current session</li>
64 + <li>Includes wiki administration and user profile controls</li>
65 + <li>Can be used on the main wiki and subwikis</li>
148 148   </ul>
149 149   </aside>
150 150   </div>
... ... @@ -151,330 +151,190 @@
151 151   </div>
152 152  </section>
153 153  
154 -<section aria-labelledby="capabilities-title">
72 +<section aria-labelledby="features-title">
155 155   <div class="container">
156 - <h2 id="capabilities-title">Main capabilities</h2>
157 -
74 + <h2 id="features-title">Main capabilities</h2>
158 158   <p class="section-intro">
159 - A focused set of authentication protection features for stronger XWiki account security
160 - without replacing the familiar login experience.
76 + The extension focuses on adding a practical second authentication step while keeping the standard XWiki login
77 + process and administration experience understandable.
161 161   </p>
162 162  
163 163   <div class="product-feature-grid">
164 - #foreach ($entry in $mainCapabilityItems)
165 - <article class="product-feature">
166 - <div class="card-heading">
167 - <div class="feature-icon">
168 - <i class="fa fa-$entry.icon" aria-hidden="true"></i>
169 - </div>
170 - <h3>$entry.title</h3>
171 - </div>
81 + <article class="product-feature">
82 + <div class="feature-icon">
83 + <i class="fa fa-key" aria-hidden="true"></i>
84 + </div>
85 + <h3>Second login step</h3>
86 + <p>
87 + After the username and password are verified, users are asked to enter an additional verification code
88 + before accessing the wiki.
89 + </p>
90 + </article>
172 172  
173 - <p>$entry.content</p>
174 - </article>
175 - #end
176 - </div>
177 - </div>
178 -</section>
92 + <article class="product-feature">
93 + <div class="feature-icon">
94 + <i class="fa fa-mobile" aria-hidden="true"></i>
95 + </div>
96 + <h3>Authenticator app codes</h3>
97 + <p>
98 + Users can verify access with TOTP codes generated by authenticator applications on a mobile device or desktop.
99 + </p>
100 + </article>
179 179  
180 -<section class="product-section-muted" aria-labelledby="security-title">
181 - <div class="container">
182 - <div class="product-layout">
183 - <article class="product-summary-card">
184 - <h2 id="security-title">Useful for XWiki security and access protection</h2>
102 + <article class="product-feature">
103 + <div class="feature-icon">
104 + <i class="fa fa-envelope-o" aria-hidden="true"></i>
105 + </div>
106 + <h3>Email verification codes</h3>
107 + <p>
108 + Users can receive one-time verification codes by email, useful when an authenticator app is not available or preferred.
109 + </p>
110 + </article>
185 185  
112 + <article class="product-feature">
113 + <div class="feature-icon">
114 + <i class="fa fa-plus-circle" aria-hidden="true"></i>
115 + </div>
116 + <h3>Combined verification</h3>
186 186   <p>
187 - Many organizations use XWiki to store internal documentation, procedures, operational
188 - knowledge and business-critical information. Adding an additional authentication factor helps
189 - reduce the risk of account compromise when a password is exposed or reused.
118 + The extension can also require both an authenticator app code and an email code for stricter multi-factor verification.
190 190   </p>
120 + </article>
191 191  
122 + <article class="product-feature">
123 + <div class="feature-icon">
124 + <i class="fa fa-qrcode" aria-hidden="true"></i>
125 + </div>
126 + <h3>User setup screen</h3>
192 192   <p>
193 - The extension is especially useful for protecting administrator accounts, remote users,
194 - private knowledge bases and customer or partner portals.
128 + Users can configure their verification code setup during login or from their XWiki profile when needed.
195 195   </p>
196 196   </article>
197 197  
198 - <aside class="product-info-card" aria-labelledby="use-cases-title">
199 - <h3 id="use-cases-title">Typical use cases</h3>
200 - <ul>
201 - <li>Administrator account protection</li>
202 - <li>Internal knowledge base security</li>
203 - <li>Private documentation platforms</li>
204 - <li>Remote user access protection</li>
205 - <li>Customer or partner portals</li>
206 - <li>Security review, MFA rollout and compliance readiness</li>
207 - </ul>
208 - </aside>
209 - </div>
210 - </div>
211 -</section>
132 + <article class="product-feature">
133 + <div class="feature-icon">
134 + <i class="fa fa-laptop" aria-hidden="true"></i>
135 + </div>
136 + <h3>Remember trusted clients</h3>
137 + <p>
138 + Known browsers or devices can be remembered for a configured period, reducing repeated MFA prompts from trusted clients.
139 + </p>
140 + </article>
212 212  
213 -<section aria-labelledby="admin-experience-title">
214 - <div class="container">
215 - <h2 id="admin-experience-title">Administrator configuration and monitoring</h2>
216 -
217 - <p class="section-intro">
218 - Administrators can configure the policy, define recovery options and monitor adoption
219 - from the XWiki Administration section.
220 - </p>
221 -
222 - <div class="product-feature-grid">
223 - #foreach ($entry in $adminExperienceItems)
224 - <article class="product-feature">
225 - <div class="card-heading">
226 - <div class="feature-icon">
227 - <i class="fa fa-$entry.icon" aria-hidden="true"></i>
228 - </div>
229 - <h3>$entry.title</h3>
230 - </div>
231 -
232 - <p>$entry.content</p>
233 - </article>
234 - #end
235 - </div>
236 -
237 -{{/html}}
238 -
239 -{{gallery}}
240 -[[image:mfa-admin-configuration.png]]
241 -[[image:mfa-admin-overview.png]]
242 -[[image:mfa-admin-full.png]]
243 -{{/gallery}}
244 -
245 -{{html clean="false"}}
246 -
247 - <p class="product-gallery-caption">
248 - Administration screens for configuring the policy and reviewing adoption across users.
249 - </p>
250 - </div>
251 -</section>
252 -
253 -<section class="product-section-muted" aria-labelledby="user-experience-title">
254 - <div class="container">
255 - <h2 id="user-experience-title">User setup and login verification</h2>
256 -
257 - <p class="section-intro">
258 - Users can configure the authenticator app from their profile or during the enforced setup flow,
259 - then verify future logins with a generated code.
260 - </p>
261 -
262 - <div class="product-feature-grid">
263 - #foreach ($entry in $userExperienceItems)
264 - <article class="product-feature">
265 - <div class="card-heading">
266 - <div class="feature-icon">
267 - <i class="fa fa-$entry.icon" aria-hidden="true"></i>
268 - </div>
269 - <h3>$entry.title</h3>
270 - </div>
271 -
272 - <p>$entry.content</p>
273 - </article>
274 - #end
275 - </div>
276 -
277 -{{/html}}
278 -
279 -{{gallery}}
280 -[[image:mfa-user-setup-qr.png]]
281 -[[image:mfa-login-verification-setup.png]]
282 -[[image:mfa-login-verification-code.png]]
283 -{{/gallery}}
284 -
285 -{{html clean="false"}}
286 -
287 - <p class="product-gallery-caption">
288 - User setup, enforced configuration and login verification screens.
289 - </p>
290 - </div>
291 -</section>
292 -
293 -<section aria-labelledby="self-service-title">
294 - <div class="container">
295 - <h2 id="self-service-title">Recovery codes and trusted devices</h2>
296 -
297 - <p class="section-intro">
298 - Recovery codes and trusted devices help balance stronger access protection with a smoother user experience.
299 - </p>
300 -
301 - <div class="product-feature-grid">
302 - #foreach ($entry in $selfServiceItems)
303 - <article class="product-feature">
304 - <div class="card-heading">
305 - <div class="feature-icon">
306 - <i class="fa fa-$entry.icon" aria-hidden="true"></i>
307 - </div>
308 - <h3>$entry.title</h3>
309 - </div>
310 -
311 - <p>$entry.content</p>
312 - </article>
313 - #end
314 - </div>
315 -
316 -{{/html}}
317 -
318 -{{gallery}}
319 -[[image:mfa-user-profile-overview.png]]
320 -[[image:mfa-recovery-codes-not-generated.png]]
321 -[[image:mfa-recovery-codes-generated.png]]
322 -[[image:mfa-trusted-devices.png]]
323 -[[image:mfa-user-profile-full.png]]
324 -{{/gallery}}
325 -
326 -{{html clean="false"}}
327 -
328 - <p class="product-gallery-caption">
329 - User profile screens for recovery codes, trusted devices and self-service management.
330 - </p>
331 - </div>
332 -</section>
333 -
334 -<section class="product-section-muted" aria-labelledby="admin-support-title">
335 - <div class="container">
336 - <h2 id="admin-support-title">Administrator support and user recovery</h2>
337 -
338 - <p class="section-intro">
339 - Administrators can help users recover from lost devices or restart setup when needed.
340 - </p>
341 -
342 - <div class="product-feature-grid">
343 - #foreach ($entry in $adminSupportItems)
344 - <article class="product-feature">
345 - <div class="card-heading">
346 - <div class="feature-icon">
347 - <i class="fa fa-$entry.icon" aria-hidden="true"></i>
348 - </div>
349 - <h3>$entry.title</h3>
350 - </div>
351 -
352 - <p>$entry.content</p>
353 - </article>
354 - #end
355 - </div>
356 -
357 -{{/html}}
358 -
359 -{{gallery}}
360 -[[image:mfa-admin-user-management.png]]
361 -{{/gallery}}
362 -
363 -{{html clean="false"}}
364 -
365 - <p class="product-gallery-caption">
366 - Administrator view for checking and resetting a user setup.
367 - </p>
368 - </div>
369 -</section>
370 -
371 -<section aria-labelledby="faq-title">
372 - <div class="container">
373 - <h2 id="faq-title">Frequently asked questions</h2>
374 -
375 - <p class="section-intro">
376 - Common questions about how the extension works, how users configure it and how administrators can manage rollout and recovery.
377 - </p>
378 -
379 - <div class="resource-content">
380 - <details class="resource-faq-item">
381 - <summary>Does this extension replace the standard XWiki login?</summary>
142 + <article class="product-feature">
143 + <div class="feature-icon">
144 + <i class="fa fa-sliders" aria-hidden="true"></i>
145 + </div>
146 + <h3>Administration controls</h3>
382 382   <p>
383 - No. Users still sign in with their normal XWiki username and password. The extension adds
384 - an additional verification step after the standard login check.
148 + Administrators can configure MFA behavior, manage user activation, and reset user setup when required.
385 385   </p>
386 - </details>
150 + </article>
387 387  
388 - <details class="resource-faq-item">
389 - <summary>Which verification method is used?</summary>
152 + <article class="product-feature">
153 + <div class="feature-icon">
154 + <i class="fa fa-user" aria-hidden="true"></i>
155 + </div>
156 + <h3>Profile integration</h3>
390 390   <p>
391 - Users verify access with time-based codes generated by an authenticator application.
392 - The setup page provides a QR code and a manual setup key.
158 + The extension adds user profile controls so the second-factor setup can be reviewed or reset from XWiki.
393 393   </p>
394 - </details>
160 + </article>
395 395  
396 - <details class="resource-faq-item">
397 - <summary>Can the second verification step be required for all users?</summary>
162 + <article class="product-feature">
163 + <div class="feature-icon">
164 + <i class="fa fa-random" aria-hidden="true"></i>
165 + </div>
166 + <h3>Fallback behavior</h3>
398 398   <p>
399 - Yes. Administrators can make the verification step optional or required for all users
400 - from the XWiki Administration section.
168 + The extension can fall back to standard XWiki authentication when the feature is not enabled or not configured.
401 401   </p>
402 - </details>
170 + </article>
403 403  
404 - <details class="resource-faq-item">
405 - <summary>What happens if a user loses access to the authenticator app?</summary>
172 + <article class="product-feature">
173 + <div class="feature-icon">
174 + <i class="fa fa-sitemap" aria-hidden="true"></i>
175 + </div>
176 + <h3>Main wiki and subwikis</h3>
406 406   <p>
407 - Recovery codes can provide backup access when enabled. Administrators can also reset
408 - the user setup so the configuration process can be restarted.
178 + The extension is designed to support XWiki environments using the main wiki and subwikis.
409 409   </p>
410 - </details>
180 + </article>
181 + </div>
182 + </div>
183 +</section>
411 411  
412 - <details class="resource-faq-item">
413 - <summary>Can trusted browsers or devices be disabled?</summary>
185 +<section aria-labelledby="use-cases-title">
186 + <div class="container">
187 + <div class="product-layout">
188 + <article class="product-summary-card">
189 + <h2 id="use-cases-title">When this extension is useful</h2>
190 +
414 414   <p>
415 - Yes. Administrators can configure how long trusted devices remain valid. Setting the
416 - trusted-device duration to 0 disables this option.
192 + Two-factor authentication is especially relevant when XWiki contains internal documentation, procedures,
193 + customer information, project knowledge, administrative pages, or business-critical content.
417 417   </p>
418 - </details>
419 419  
420 - <details class="resource-faq-item">
421 - <summary>Is this only a basic 2FA login-code screen?</summary>
422 422   <p>
423 - No. The main login mechanism is two-factor authentication, but the application also includes
424 - features needed for a safer organization-wide rollout: enforcement policy, recovery codes,
425 - trusted devices, user self-service, administrator monitoring and administrator reset actions.
197 + It can also support organizations that need MFA as part of their cybersecurity controls, including companies
198 + working toward NIS 2 readiness. NIS 2 focuses on stronger cybersecurity risk management across essential and
199 + important entities in the EU, and MFA is often expected as part of enterprise access protection programs.
426 426   </p>
427 - </details>
428 428  
429 - <details class="resource-faq-item">
430 - <summary>Is this enough for compliance on its own?</summary>
431 431   <p>
432 - No. This extension provides an important access-protection control, but it should be part
433 - of a broader security and compliance approach that includes permissions, upgrades,
434 - infrastructure, monitoring and operational procedures.
203 + It is also useful when many users access the wiki remotely, when administrator accounts need stronger protection,
204 + or when the organization wants to reduce the risk of compromised passwords.
435 435   </p>
436 - </details>
206 + </article>
207 +
208 + <aside class="product-info-card" aria-labelledby="good-fit-title">
209 + <h3 id="good-fit-title">Good fit for</h3>
210 + <ul>
211 + <li>Private XWiki knowledge bases</li>
212 + <li>Company intranets</li>
213 + <li>SOP and controlled-document platforms</li>
214 + <li>Documentation portals with sensitive content</li>
215 + <li>Wikis with several administrators or remote users</li>
216 + </ul>
217 + </aside>
437 437   </div>
438 438   </div>
439 439  </section>
440 440  
441 -<section class="product-section-muted" aria-labelledby="rollout-title">
222 +<section class="product-section-muted" aria-labelledby="compliance-title">
442 442   <div class="container">
443 443   <div class="product-layout">
444 444   <article class="product-summary-card">
445 - <h2 id="rollout-title">Rollout recommendations</h2>
226 + <h2 id="compliance-title">Useful for MFA adoption and NIS 2 readiness</h2>
446 446  
447 447   <p>
448 - For a smooth rollout, start with a small administrator or pilot group before requiring
449 - the additional verification step for everyone. This helps validate the configuration,
450 - prepare user communication and reduce support issues.
229 + Many organizations now need multi-factor authentication for enterprise software, including internal
230 + knowledge bases, documentation platforms, intranets and systems that contain operational procedures
231 + or sensitive business information.
451 451   </p>
452 452  
453 - <ol class="process-list">
454 - #foreach ($entry in $rolloutItems)
455 - <li>
456 - <strong>$entry.title</strong>
457 - $entry.content
458 - </li>
459 - #end
460 - </ol>
461 - </article>
234 + <p>
235 + For organizations using XWiki, adding MFA directly to the standard XWiki login flow can help close a
236 + practical access-control gap. The extension can support simple 2FA with one additional verification method,
237 + or a stricter MFA setup where both authenticator app and email verification are required.
238 + </p>
462 462  
463 - <aside class="product-info-card" aria-labelledby="planning-title">
464 - <h3 id="planning-title">Useful information before installation</h3>
465 -
466 - <p class="product-card-note">
467 - These details help evaluate compatibility, rollout scope and configuration options.
240 + <p>
241 + This can be relevant for organizations preparing for NIS 2, where multi-factor authentication or
242 + continuous authentication is part of cybersecurity risk-management measures, where appropriate.
243 + MFA support in XWiki is only one part of a broader compliance and security program, but it can be an
244 + important technical control for protecting access to the wiki.
468 468   </p>
246 + </article>
469 469  
248 + <aside class="product-info-card" aria-labelledby="mfa-readiness-title">
249 + <h3 id="mfa-readiness-title">Security controls supported</h3>
470 470   <ul>
471 - <li>XWiki version</li>
472 - <li>Single wiki or wiki farm with subwikis</li>
473 - <li>Current authentication setup</li>
474 - <li>Optional or required rollout policy</li>
475 - <li>Trusted-device policy</li>
476 - <li>Recovery-code policy</li>
477 - <li>Rollout communication needs</li>
251 + <li>Second-factor verification after password login</li>
252 + <li>Authenticator app or email-based verification codes</li>
253 + <li>Reduced repeated prompts for trusted clients</li>
254 + <li>Administration controls for user-level MFA management</li>
255 + <li>Better protection for administrator and remote-access accounts</li>
478 478   </ul>
479 479   </aside>
480 480   </div>
... ... @@ -481,17 +481,32 @@
481 481   </div>
482 482  </section>
483 483  
262 +#*
263 +<section aria-labelledby="gallery-title">
264 + <div class="container">
265 + <div class="product-gallery-panel">
266 + <h2 id="gallery-title">Screenshots</h2>
267 + <p class="gallery-note">
268 + Use this area to show the login verification screen, first-time setup, user profile controls,
269 + and administration configuration.
270 + </p>
271 +
272 + <div class="product-gallery-placeholder">
273 + Replace this placeholder with the XWiki gallery macro and 3-5 screenshots from the application.
274 + </div>
275 + </div>
276 + </div>
277 +</section>
278 +*#
484 484  <section class="cta-section" aria-labelledby="cta-title">
485 485   <div class="container">
486 486   <div class="cta-panel">
487 487   <h2 id="cta-title">Interested in using this extension?</h2>
488 -
489 489   <p>
490 - Send a short message with your XWiki version, current authentication setup and rollout goal.
284 + Send a short message with your XWiki version, authentication setup, and whether you use a single wiki
285 + or a main wiki with subwikis.
491 491   </p>
492 -
493 493   <a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Contact Agnease</a>
494 - <a class="btn btn-secondary" href="$xwiki.getURL('pricing.WebHome')#common-packages">View MFA setup price</a>
495 495   </div>
496 496   </div>
497 497  </section>
2fa-authenticator.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Admin
Size
... ... @@ -1,1 +1,0 @@
1 -1.1 MB
Content
mfa-admin-configuration.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Admin
Size
... ... @@ -1,1 +1,0 @@
1 -125.3 KB
Content
mfa-admin-full.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Admin
Size
... ... @@ -1,1 +1,0 @@
1 -184.3 KB
Content
mfa-admin-overview.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Admin
Size
... ... @@ -1,1 +1,0 @@
1 -64.7 KB
Content
mfa-admin-user-management.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Admin
Size
... ... @@ -1,1 +1,0 @@
1 -90.8 KB
Content
mfa-login-verification-code.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Admin
Size
... ... @@ -1,1 +1,0 @@
1 -23.6 KB
Content
mfa-login-verification-setup.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Admin
Size
... ... @@ -1,1 +1,0 @@
1 -115.9 KB
Content
mfa-recovery-codes-generated.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Admin
Size
... ... @@ -1,1 +1,0 @@
1 -38.5 KB
Content
mfa-recovery-codes-not-generated.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Admin
Size
... ... @@ -1,1 +1,0 @@
1 -27.0 KB
Content
mfa-trusted-devices.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Admin
Size
... ... @@ -1,1 +1,0 @@
1 -59.1 KB
Content
mfa-user-profile-full.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Admin
Size
... ... @@ -1,1 +1,0 @@
1 -197.5 KB
Content
mfa-user-profile-overview.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Admin
Size
... ... @@ -1,1 +1,0 @@
1 -193.4 KB
Content
mfa-user-setup-qr.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Admin
Size
... ... @@ -1,1 +1,0 @@
1 -176.6 KB
Content
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