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 6.11
edited by Alex Cotiuga
on 2026/06/23 07:33
Change comment: There is no comment for this version

Summary

Details

Page properties
Default language
... ... @@ -1,0 +1,1 @@
1 +en
Hidden
... ... @@ -1,1 +1,1 @@
1 -true
1 +false
Content
... ... @@ -1,91 +1,77 @@
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',
6 6   'icon': 'key',
7 - 'content': 'Add an additional verification screen after the normal XWiki username and password login.'
8 + 'content': 'After the normal username and password check, users complete an additional verification step before accessing XWiki.'
8 8  },{
9 9   'title': 'Authenticator app codes',
10 10   'icon': 'mobile',
11 - 'content': 'Let users verify access with time-based TOTP codes generated by authenticator applications.'
12 + 'content': 'Users can verify access with time-based TOTP codes generated by authenticator applications on mobile or desktop devices.'
12 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.'
14 + 'title': 'Email verification codes',
15 + 'icon': 'envelope-o',
16 + 'content': 'Users can receive one-time verification codes by email when an authenticator app is not available or preferred.'
16 16  }])
17 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 -}])
19 +#set ($useCaseItems = [
20 + 'Protecting administrator accounts',
21 + 'Improving access security for internal knowledge bases',
22 + 'Securing private documentation platforms and intranets',
23 + 'Supporting remote-user access policies',
24 + 'Strengthening customer or partner portals',
25 + 'Preparing for security reviews or broader compliance initiatives'
26 +])
31 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 -}])
28 +#set ($adminCapabilityItems = [
29 + 'Require MFA for all users',
30 + 'Define the issuer name displayed in authenticator applications',
31 + 'Configure trusted-device duration',
32 + 'Configure how many recovery codes are generated',
33 + 'Reset a user’s MFA setup when needed',
34 + 'Review MFA adoption from the administration overview'
35 +])
45 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 -}])
37 +#set ($overviewItems = [
38 + 'Number of users scanned',
39 + 'Users with MFA configured',
40 + 'Users without MFA configured',
41 + 'Users with trusted devices',
42 + 'Recovery-code status',
43 + 'Unused and total recovery-code count',
44 + 'Trusted-device count'
45 +])
59 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 -}])
47 +#set ($profileItems = [
48 + 'Configure MFA',
49 + 'Review MFA status',
50 + 'Generate or regenerate recovery codes',
51 + 'Review trusted devices',
52 + 'Remove individual trusted devices',
53 + 'Remove all trusted devices',
54 + 'Reset MFA setup'
55 +])
73 73  
74 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.'
58 + 'title': 'Install and configure the extension',
59 + 'content': 'Start by validating compatibility with the current XWiki version and authentication setup.'
77 77  },{
78 - 'title': 'Define the rollout policy',
79 - 'content': 'Decide whether additional verification should be optional at first or required for all users.'
61 + 'title': 'Define the MFA policy',
62 + 'content': 'Decide whether MFA should be optional, required for administrators, or required for all users.'
80 80  },{
81 - 'title': 'Configure recovery options',
82 - 'content': 'Choose the number of recovery codes and whether trusted devices should be allowed.'
64 + 'title': 'Configure recovery and trusted devices',
65 + 'content': 'Choose whether users can rely on recovery codes and whether trusted browsers or devices are allowed.'
83 83  },{
84 - 'title': 'Inform users',
85 - 'content': 'Explain how users configure the authenticator app, save recovery codes and manage trusted devices.'
67 + 'title': 'Test with a pilot group',
68 + 'content': 'Validate the setup and login flow with administrators or a small group before wider rollout.'
86 86  },{
70 + 'title': 'Communicate the user process',
71 + 'content': 'Explain how users should configure MFA, store recovery codes and manage trusted devices.'
72 +},{
87 87   'title': 'Monitor adoption',
88 - 'content': 'Use the administration overview to identify users who still need to configure protection.'
74 + 'content': 'Use the administration overview to identify users who still need to configure MFA.'
89 89  }])
90 90  
91 91  {{html clean="false"}}
... ... @@ -94,24 +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
83 + XWiki 2FA and MFA
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.
89 + Protect XWiki logins with a second verification step using authenticator app codes,
90 + email verification codes, or both.
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>
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>
95 + <a class="btn btn-secondary" href="$xwiki.getURL('products.WebHome')">View all products</a>
115 115   </div>
116 116   </div>
117 117  </section>
... ... @@ -123,16 +123,21 @@
123 123   <h2 id="overview-title">Two-factor authentication built into 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.
107 + XWiki Two-Factor Authentication adds MFA/2FA support to the standard XWiki login flow.
108 + Users continue to sign in with their normal username and password, then confirm access with
109 + an additional verification method.
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.
113 + The extension supports authenticator app codes, email-delivered verification codes, or a combined
114 + setup where both methods are required. It improves account protection without replacing the familiar
115 + XWiki authentication experience.
135 135   </p>
117 +
118 + <p>
119 + It is designed for organizations that use XWiki for internal knowledge bases, intranets,
120 + documentation platforms, customer portals, workflows or other business-critical applications.
121 + </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>
128 + <li>Supports authenticator app codes using TOTP</li>
129 + <li>Supports email-delivered one-time verification codes</li>
130 + <li>Can require app code and email code together</li>
131 + <li>Includes recovery codes for backup access</li>
145 145   <li>Can remember trusted browsers or devices</li>
146 - <li>Includes user self-service controls</li>
147 - <li>Includes an administration overview</li>
133 + <li>Includes administration and user setup controls</li>
148 148   </ul>
149 149   </aside>
150 150   </div>
... ... @@ -151,13 +151,13 @@
151 151   </div>
152 152  </section>
153 153  
154 -<section aria-labelledby="capabilities-title">
140 +<section aria-labelledby="features-title">
155 155   <div class="container">
156 - <h2 id="capabilities-title">Main capabilities</h2>
142 + <h2 id="features-title">Main capabilities</h2>
157 157  
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.
145 + A focused set of MFA/2FA features for stronger XWiki account protection without changing
146 + the standard login experience.
161 161   </p>
162 162  
163 163   <div class="product-feature-grid">
... ... @@ -181,29 +181,32 @@
181 181   <div class="container">
182 182   <div class="product-layout">
183 183   <article class="product-summary-card">
184 - <h2 id="security-title">Useful for XWiki security and access protection</h2>
170 + <h2 id="security-title">Useful for XWiki security and NIS 2 readiness</h2>
185 185  
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.
173 + Many organizations need multi-factor authentication for enterprise software, including internal
174 + knowledge bases, intranets, documentation platforms and systems containing operational procedures
175 + or sensitive business information.
190 190   </p>
191 191  
192 192   <p>
193 - The extension is especially useful for protecting administrator accounts, remote users,
194 - private knowledge bases and customer or partner portals.
179 + For organizations using XWiki, adding two-factor authentication directly to the standard login flow
180 + can help close a practical access-control gap. It can be useful for administrator accounts,
181 + remote users, private knowledge bases and broader security readiness initiatives such as NIS 2 preparation.
195 195   </p>
183 +
184 + <p>
185 + This extension is not a complete compliance solution on its own, but it provides an important
186 + technical control for protecting access to XWiki.
187 + </p>
196 196   </article>
197 197  
198 198   <aside class="product-info-card" aria-labelledby="use-cases-title">
199 199   <h3 id="use-cases-title">Typical use cases</h3>
200 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>
193 + #foreach ($item in $useCaseItems)
194 + <li>$item</li>
195 + #end
207 207   </ul>
208 208   </aside>
209 209   </div>
... ... @@ -210,268 +210,258 @@
210 210   </div>
211 211  </section>
212 212  
213 -<section aria-labelledby="admin-experience-title">
202 +<section aria-labelledby="admin-title">
214 214   <div class="container">
215 - <h2 id="admin-experience-title">Administrator configuration and monitoring</h2>
204 + <div class="product-layout">
205 + <article class="product-summary-card">
206 + <h2 id="admin-title">Administrator configuration</h2>
216 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>
208 + <p>
209 + Administrators configure MFA from the XWiki Administration section. The configuration is intentionally
210 + simple, so the rollout can be adapted to the organization’s security policy and user base.
211 + </p>
221 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>
213 + <p>
214 + MFA can be optional or required for all users. When MFA is required, users who have not configured it yet
215 + are guided through the setup flow from their profile or during login.
216 + </p>
231 231  
232 - <p>$entry.content</p>
233 - </article>
234 - #end
218 + <p>
219 + If trusted devices should not be allowed, the trusted-device duration can be set to 0.
220 + If recovery codes should not be available, the recovery-code number can be set to 0.
221 + </p>
222 + </article>
223 +
224 + <aside class="product-info-card" aria-labelledby="admin-capabilities-title">
225 + <h3 id="admin-capabilities-title">Administrators can</h3>
226 + <ul>
227 + #foreach ($item in $adminCapabilityItems)
228 + <li>$item</li>
229 + #end
230 + </ul>
231 + </aside>
235 235   </div>
233 + </div>
234 +</section>
236 236  
237 237  {{/html}}
238 238  
239 239  {{gallery}}
240 240  [[image:mfa-admin-configuration.png]]
241 -[[image:mfa-admin-overview.png]]
242 -[[image:mfa-admin-full.png]]
243 243  {{/gallery}}
244 244  
245 245  {{html clean="false"}}
246 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">
244 +<section aria-labelledby="admin-overview-title">
254 254   <div class="container">
255 - <h2 id="user-experience-title">User setup and login verification</h2>
246 + <div class="product-layout">
247 + <article class="product-summary-card">
248 + <h2 id="admin-overview-title">MFA overview for administrators</h2>
256 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>
250 + <p>
251 + The Administration section includes an MFA overview page that helps administrators understand adoption
252 + and usage across the wiki.
253 + </p>
261 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>
255 + <p>
256 + The overview displays summary indicators and a Live Data table with MFA-related information.
257 + The table is filterable and sortable, making it suitable for installations with many users.
258 + </p>
259 + </article>
271 271  
272 - <p>$entry.content</p>
273 - </article>
274 - #end
261 + <aside class="product-info-card" aria-labelledby="overview-data-title">
262 + <h3 id="overview-data-title">The overview can show</h3>
263 + <ul>
264 + #foreach ($item in $overviewItems)
265 + <li>$item</li>
266 + #end
267 + </ul>
268 + </aside>
275 275   </div>
270 + </div>
271 +</section>
276 276  
277 277  {{/html}}
278 278  
279 279  {{gallery}}
280 -[[image:mfa-user-setup-qr.png]]
281 -[[image:mfa-login-verification-setup.png]]
282 -[[image:mfa-login-verification-code.png]]
276 +[[image:mfa-admin-overview.png]]
283 283  {{/gallery}}
284 284  
285 285  {{html clean="false"}}
286 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">
281 +<section class="product-section-muted" aria-labelledby="user-setup-title">
294 294   <div class="container">
295 - <h2 id="self-service-title">Recovery codes and trusted devices</h2>
283 + <div class="product-layout">
284 + <article class="product-summary-card">
285 + <h2 id="user-setup-title">User setup experience</h2>
296 296  
297 - <p class="section-intro">
298 - Recovery codes and trusted devices help balance stronger access protection with a smoother user experience.
299 - </p>
287 + <p>
288 + Users can configure MFA from their profile page. During setup, the user scans a QR code with
289 + an authenticator application.
290 + </p>
300 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>
292 + <p>
293 + If scanning is not possible, the setup page also provides the account name and secret key that can be
294 + entered manually. After the generated verification code is entered successfully, MFA is activated for
295 + the user account.
296 + </p>
297 + </article>
310 310  
311 - <p>$entry.content</p>
312 - </article>
313 - #end
299 + <aside class="product-info-card" aria-labelledby="login-flow-title">
300 + <h3 id="login-flow-title">Login flow</h3>
301 + <ul>
302 + <li>User signs in with the normal XWiki credentials</li>
303 + <li>XWiki asks for the configured verification code</li>
304 + <li>The user enters the app code, email code, or both</li>
305 + <li>A recovery code can be used when enabled and available</li>
306 + <li>A trusted browser or device can be remembered when allowed</li>
307 + </ul>
308 + </aside>
314 314   </div>
310 + </div>
311 +</section>
315 315  
316 316  {{/html}}
317 317  
318 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]]
316 +[[image:mfa-user-setup-qr.png]]
317 +[[image:mfa-login-verification.png]]
324 324  {{/gallery}}
325 325  
326 326  {{html clean="false"}}
327 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">
322 +<section aria-labelledby="recovery-title">
335 335   <div class="container">
336 - <h2 id="admin-support-title">Administrator support and user recovery</h2>
324 + <div class="product-layout">
325 + <article class="product-summary-card">
326 + <h2 id="recovery-title">Recovery codes</h2>
337 337  
338 - <p class="section-intro">
339 - Administrators can help users recover from lost devices or restart setup when needed.
340 - </p>
328 + <p>
329 + Recovery codes provide a backup access method when a user loses access to the authenticator application
330 + or cannot complete the normal verification flow.
331 + </p>
341 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>
333 + <p>
334 + Recovery codes are generated for the user and displayed only once. Each code can be used one time.
335 + When new recovery codes are generated, previous recovery codes are invalidated.
336 + </p>
351 351  
352 - <p>$entry.content</p>
353 - </article>
354 - #end
338 + <p>
339 + Users should save their recovery codes in a secure location immediately after generation.
340 + Administrators can configure how many recovery codes are generated, and setting the number to 0 disables them.
341 + </p>
342 + </article>
343 +
344 + <aside class="product-info-card" aria-labelledby="trusted-devices-title">
345 + <h3 id="trusted-devices-title">Trusted devices</h3>
346 + <ul>
347 + <li>Reduce repeated MFA prompts on known browsers or devices</li>
348 + <li>Remain valid for the configured number of days</li>
349 + <li>Can be reviewed and removed from the user profile</li>
350 + <li>The current trusted browser is marked in the list</li>
351 + <li>Removed when a user’s MFA setup is reset</li>
352 + </ul>
353 + </aside>
355 355   </div>
355 + </div>
356 +</section>
356 356  
357 357  {{/html}}
358 358  
359 359  {{gallery}}
360 -[[image:mfa-admin-user-management.png]]
361 +[[image:mfa-recovery-codes.png]]
362 +[[image:mfa-trusted-devices.png]]
361 361  {{/gallery}}
362 362  
363 363  {{html clean="false"}}
364 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">
367 +<section class="product-section-muted" aria-labelledby="profile-title">
372 372   <div class="container">
373 - <h2 id="faq-title">Frequently asked questions</h2>
369 + <div class="product-layout">
370 + <article class="product-summary-card">
371 + <h2 id="profile-title">User and administrator management</h2>
374 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>
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.
374 + The user profile contains a dedicated MFA section. Users can configure MFA, review their status,
375 + manage recovery codes and manage trusted devices from this area.
385 385   </p>
386 - </details>
387 387  
388 - <details class="resource-faq-item">
389 - <summary>Which verification method is used?</summary>
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.
379 + Administrators can also open a user profile and access the MFA section for that user.
380 + This is useful when a user loses access to their authenticator application or needs to restart the setup process.
393 393   </p>
394 - </details>
395 395  
396 - <details class="resource-faq-item">
397 - <summary>Can the second verification step be required for all users?</summary>
398 398   <p>
399 - Yes. Administrators can make the verification step optional or required for all users
400 - from the XWiki Administration section.
384 + Resetting MFA removes the authenticator app setup, invalidates recovery codes and removes trusted devices.
385 + If MFA is required globally, the user will be asked to configure MFA again at the next login.
401 401   </p>
402 - </details>
387 + </article>
403 403  
404 - <details class="resource-faq-item">
405 - <summary>What happens if a user loses access to the authenticator app?</summary>
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.
409 - </p>
410 - </details>
389 + <aside class="product-info-card" aria-labelledby="profile-actions-title">
390 + <h3 id="profile-actions-title">Profile actions</h3>
391 + <ul>
392 + #foreach ($item in $profileItems)
393 + <li>$item</li>
394 + #end
395 + </ul>
396 + </aside>
397 + </div>
398 + </div>
399 +</section>
411 411  
412 - <details class="resource-faq-item">
413 - <summary>Can trusted browsers or devices be disabled?</summary>
414 - <p>
415 - Yes. Administrators can configure how long trusted devices remain valid. Setting the
416 - trusted-device duration to 0 disables this option.
417 - </p>
418 - </details>
401 +{{/html}}
419 419  
420 - <details class="resource-faq-item">
421 - <summary>Is this only a basic 2FA login-code screen?</summary>
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.
426 - </p>
427 - </details>
403 +{{gallery}}
404 +[[image:mfa-user-profile-overview.png]]
405 +[[image:mfa-admin-user-management.png]]
406 +{{/gallery}}
428 428  
429 - <details class="resource-faq-item">
430 - <summary>Is this enough for compliance on its own?</summary>
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.
435 - </p>
436 - </details>
437 - </div>
408 +{{html clean="false"}}
409 +
410 +<section aria-labelledby="rollout-title">
411 + <div class="container">
412 + <h2 id="rollout-title">Rollout recommendations</h2>
413 +
414 + <p class="section-intro">
415 + For a smooth rollout, start with a small administrator or pilot group before requiring MFA for everyone.
416 + A gradual rollout helps validate the configuration, prepare communication and reduce support issues.
417 + </p>
418 +
419 + <ol class="process-list">
420 + #foreach ($entry in $rolloutItems)
421 + <li>
422 + <strong>$entry.title</strong>
423 + $entry.content
424 + </li>
425 + #end
426 + </ol>
438 438   </div>
439 439  </section>
440 440  
441 -<section class="product-section-muted" aria-labelledby="rollout-title">
430 +<section class="product-section-muted" aria-labelledby="planning-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>
434 + <h2 id="planning-title">Planning installation</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.
437 + Before installing or rolling out MFA, it is useful to review the current XWiki version,
438 + authentication setup, user base and security expectations.
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>
441 + <p>
442 + This helps define whether MFA should be optional, required for selected users, or enforced globally.
443 + It also helps decide whether trusted devices and recovery codes should be enabled.
444 + </p>
461 461   </article>
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.
468 - </p>
469 -
447 + <aside class="product-info-card" aria-labelledby="planning-info-title">
448 + <h3 id="planning-info-title">Useful information before installation</h3>
470 470   <ul>
471 471   <li>XWiki version</li>
472 472   <li>Single wiki or wiki farm with subwikis</li>
473 473   <li>Current authentication setup</li>
474 - <li>Optional or required rollout policy</li>
453 + <li>Optional or globally required MFA policy</li>
475 475   <li>Trusted-device policy</li>
476 476   <li>Recovery-code policy</li>
477 477   <li>Rollout communication needs</li>
... ... @@ -487,11 +487,12 @@
487 487   <h2 id="cta-title">Interested in using this extension?</h2>
488 488  
489 489   <p>
490 - Send a short message with your XWiki version, current authentication setup and rollout goal.
469 + Send a short message with your XWiki version, authentication setup and whether you need
470 + authenticator app codes, email verification codes, combined verification, recovery codes
471 + or trusted-device remembering.
491 491   </p>
492 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