Skip to Content
Last modified by Agnease on 2026/06/24 16:39
From version 8.1
edited by Agnease
on 2026/06/23 12:05
Change comment: Rollback to version 6.11
To version 27.1
edited by Agnease
on 2026/06/24 16:39
Change comment: Upload new image "1-linkedin-2fa-authenticator.png", version 1.1

Summary

Details

Page properties
Content
... ... @@ -1,77 +1,91 @@
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',
7 7   'icon': 'key',
8 - 'content': 'After the normal username and password check, users complete an additional verification step before accessing XWiki.'
7 + 'content': 'Add an additional verification screen after the normal XWiki username and password login.'
9 9  },{
10 10   'title': 'Authenticator app codes',
11 11   'icon': 'mobile',
12 - 'content': 'Users can verify access with time-based TOTP codes generated by authenticator applications on mobile or desktop devices.'
11 + 'content': 'Let users verify access with time-based TOTP codes generated by authenticator applications.'
13 13  },{
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.'
13 + 'title': 'Recovery and trusted devices',
14 + 'icon': 'shield',
15 + 'content': 'Provide backup access with recovery codes and reduce repeated prompts on trusted browsers.'
17 17  }])
18 18  
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 -])
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 +}])
27 27  
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 -])
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 +}])
36 36  
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 -])
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 +}])
46 46  
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 -])
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 +}])
56 56  
57 57  #set ($rolloutItems = [{
58 - 'title': 'Install and configure the extension',
59 - 'content': 'Start by validating compatibility with the current XWiki version and authentication setup.'
75 + 'title': 'Start with a pilot group',
76 + 'content': 'Test the extension with administrators or a small user group before enabling it widely.'
60 60  },{
61 - 'title': 'Define the MFA policy',
62 - 'content': 'Decide whether MFA should be optional, required for administrators, 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.'
63 63  },{
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.'
81 + 'title': 'Configure recovery options',
82 + 'content': 'Choose the number of recovery codes and whether trusted devices should be allowed.'
66 66  },{
67 - 'title': 'Test with a pilot group',
68 - 'content': 'Validate the setup and login flow with administrators or a small group before wider rollout.'
84 + 'title': 'Inform users',
85 + 'content': 'Explain how users configure the authenticator app, save recovery codes and manage trusted devices.'
69 69  },{
70 - 'title': 'Communicate the user process',
71 - 'content': 'Explain how users should configure MFA, store recovery codes and manage trusted devices.'
72 -},{
73 73   'title': 'Monitor adoption',
74 - '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.'
75 75  }])
76 76  
77 77  {{html clean="false"}}
... ... @@ -80,14 +80,14 @@
80 80   <div class="container hero-inner">
81 81   <div class="hero-kicker">
82 82   <i class="fa fa-lock" aria-hidden="true"></i>
83 - XWiki 2FA and MFA
97 + XWiki 2FA with MFA rollout support
84 84   </div>
85 85  
86 86   <h1 id="product-title">XWiki Two-Factor Authentication</h1>
87 87  
88 88   <p class="lead">
89 - Protect XWiki logins with a second verification step using authenticator app codes,
90 - email verification codes, or both.
103 + Protect XWiki logins with authenticator app verification, recovery codes,
104 + trusted devices and administration controls for a safer rollout.
91 91   </p>
92 92  
93 93   <div class="hero-actions">
... ... @@ -104,21 +104,16 @@
104 104   <h2 id="overview-title">Two-factor authentication built into XWiki</h2>
105 105  
106 106   <p>
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.
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.
110 110   </p>
111 111  
112 112   <p>
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.
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.
116 116   </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>
122 122   </article>
123 123  
124 124   <aside class="product-info-card" aria-labelledby="quick-facts-title">
... ... @@ -125,12 +125,12 @@
125 125   <h3 id="quick-facts-title">Quick facts</h3>
126 126   <ul>
127 127   <li>Works with the standard XWiki login flow</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>
137 + <li>Supports TOTP authenticator applications</li>
138 + <li>Can require additional verification for all users</li>
139 + <li>Includes one-time recovery codes</li>
132 132   <li>Can remember trusted browsers or devices</li>
133 - <li>Includes administration and user setup controls</li>
141 + <li>Includes user self-service controls</li>
142 + <li>Includes an administration overview</li>
134 134   </ul>
135 135   </aside>
136 136   </div>
... ... @@ -137,13 +137,13 @@
137 137   </div>
138 138  </section>
139 139  
140 -<section aria-labelledby="features-title">
149 +<section aria-labelledby="capabilities-title">
141 141   <div class="container">
142 - <h2 id="features-title">Main capabilities</h2>
151 + <h2 id="capabilities-title">Main capabilities</h2>
143 143  
144 144   <p class="section-intro">
145 - A focused set of MFA/2FA features for stronger XWiki account protection without changing
146 - the standard login experience.
154 + A focused set of authentication protection features for stronger XWiki account security
155 + without replacing the familiar login experience.
147 147   </p>
148 148  
149 149   <div class="product-feature-grid">
... ... @@ -167,32 +167,29 @@
167 167   <div class="container">
168 168   <div class="product-layout">
169 169   <article class="product-summary-card">
170 - <h2 id="security-title">Useful for XWiki security and NIS 2 readiness</h2>
179 + <h2 id="security-title">Useful for XWiki security and access protection</h2>
171 171  
172 172   <p>
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.
182 + Many organizations use XWiki to store internal documentation, procedures, operational
183 + knowledge and business-critical information. Adding an additional authentication factor helps
184 + reduce the risk of account compromise when a password is exposed or reused.
176 176   </p>
177 177  
178 178   <p>
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.
188 + The extension is especially useful for protecting administrator accounts, remote users,
189 + private knowledge bases and customer or partner portals.
182 182   </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>
188 188   </article>
189 189  
190 190   <aside class="product-info-card" aria-labelledby="use-cases-title">
191 191   <h3 id="use-cases-title">Typical use cases</h3>
192 192   <ul>
193 - #foreach ($item in $useCaseItems)
194 - <li>$item</li>
195 - #end
196 + <li>Administrator account protection</li>
197 + <li>Internal knowledge base security</li>
198 + <li>Private documentation platforms</li>
199 + <li>Remote user access protection</li>
200 + <li>Customer or partner portals</li>
201 + <li>Security review, MFA rollout and compliance readiness</li>
196 196   </ul>
197 197   </aside>
198 198   </div>
... ... @@ -199,258 +199,268 @@
199 199   </div>
200 200  </section>
201 201  
202 -<section aria-labelledby="admin-title">
208 +<section aria-labelledby="admin-experience-title">
203 203   <div class="container">
204 - <div class="product-layout">
205 - <article class="product-summary-card">
206 - <h2 id="admin-title">Administrator configuration</h2>
210 + <h2 id="admin-experience-title">Administrator configuration and monitoring</h2>
207 207  
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>
212 + <p class="section-intro">
213 + Administrators can configure the policy, define recovery options and monitor adoption
214 + from the XWiki Administration section.
215 + </p>
212 212  
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>
217 + <div class="product-feature-grid">
218 + #foreach ($entry in $adminExperienceItems)
219 + <article class="product-feature">
220 + <div class="card-heading">
221 + <div class="feature-icon">
222 + <i class="fa fa-$entry.icon" aria-hidden="true"></i>
223 + </div>
224 + <h3>$entry.title</h3>
225 + </div>
217 217  
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>
227 + <p>$entry.content</p>
228 + </article>
229 + #end
232 232   </div>
233 - </div>
234 -</section>
235 235  
236 236  {{/html}}
237 237  
238 238  {{gallery}}
239 239  [[image:mfa-admin-configuration.png]]
236 +[[image:mfa-admin-overview.png]]
237 +[[image:mfa-admin-full.png]]
240 240  {{/gallery}}
241 241  
242 242  {{html clean="false"}}
243 243  
244 -<section aria-labelledby="admin-overview-title">
242 + <p class="product-gallery-caption">
243 + Administration screens for configuring the policy and reviewing adoption across users.
244 + </p>
245 + </div>
246 +</section>
247 +
248 +<section class="product-section-muted" aria-labelledby="user-experience-title">
245 245   <div class="container">
246 - <div class="product-layout">
247 - <article class="product-summary-card">
248 - <h2 id="admin-overview-title">MFA overview for administrators</h2>
250 + <h2 id="user-experience-title">User setup and login verification</h2>
249 249  
250 - <p>
251 - The Administration section includes an MFA overview page that helps administrators understand adoption
252 - and usage across the wiki.
253 - </p>
252 + <p class="section-intro">
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.
255 + </p>
254 254  
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>
257 + <div class="product-feature-grid">
258 + #foreach ($entry in $userExperienceItems)
259 + <article class="product-feature">
260 + <div class="card-heading">
261 + <div class="feature-icon">
262 + <i class="fa fa-$entry.icon" aria-hidden="true"></i>
263 + </div>
264 + <h3>$entry.title</h3>
265 + </div>
260 260  
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>
267 + <p>$entry.content</p>
268 + </article>
269 + #end
269 269   </div>
270 - </div>
271 -</section>
272 272  
273 273  {{/html}}
274 274  
275 275  {{gallery}}
276 -[[image:mfa-admin-overview.png]]
275 +[[image:mfa-user-setup-qr.png]]
276 +[[image:mfa-login-verification-setup.png]]
277 +[[image:mfa-login-verification-code.png]]
277 277  {{/gallery}}
278 278  
279 279  {{html clean="false"}}
280 280  
281 -<section class="product-section-muted" aria-labelledby="user-setup-title">
282 + <p class="product-gallery-caption">
283 + User setup, enforced configuration and login verification screens.
284 + </p>
285 + </div>
286 +</section>
287 +
288 +<section aria-labelledby="self-service-title">
282 282   <div class="container">
283 - <div class="product-layout">
284 - <article class="product-summary-card">
285 - <h2 id="user-setup-title">User setup experience</h2>
290 + <h2 id="self-service-title">Recovery codes and trusted devices</h2>
286 286  
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>
292 + <p class="section-intro">
293 + Recovery codes and trusted devices help balance stronger access protection with a smoother user experience.
294 + </p>
291 291  
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>
296 + <div class="product-feature-grid">
297 + #foreach ($entry in $selfServiceItems)
298 + <article class="product-feature">
299 + <div class="card-heading">
300 + <div class="feature-icon">
301 + <i class="fa fa-$entry.icon" aria-hidden="true"></i>
302 + </div>
303 + <h3>$entry.title</h3>
304 + </div>
298 298  
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>
306 + <p>$entry.content</p>
307 + </article>
308 + #end
309 309   </div>
310 - </div>
311 -</section>
312 312  
313 313  {{/html}}
314 314  
315 315  {{gallery}}
316 -[[image:mfa-user-setup-qr.png]]
317 -[[image:mfa-login-verification.png]]
314 +[[image:mfa-user-profile-overview.png]]
315 +[[image:mfa-recovery-codes-not-generated.png]]
316 +[[image:mfa-recovery-codes-generated.png]]
317 +[[image:mfa-trusted-devices.png]]
318 +[[image:mfa-user-profile-full.png]]
318 318  {{/gallery}}
319 319  
320 320  {{html clean="false"}}
321 321  
322 -<section aria-labelledby="recovery-title">
323 + <p class="product-gallery-caption">
324 + User profile screens for recovery codes, trusted devices and self-service management.
325 + </p>
326 + </div>
327 +</section>
328 +
329 +<section class="product-section-muted" aria-labelledby="admin-support-title">
323 323   <div class="container">
324 - <div class="product-layout">
325 - <article class="product-summary-card">
326 - <h2 id="recovery-title">Recovery codes</h2>
331 + <h2 id="admin-support-title">Administrator support and user recovery</h2>
327 327  
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>
333 + <p class="section-intro">
334 + Administrators can help users recover from lost devices or restart setup when needed.
335 + </p>
332 332  
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>
337 + <div class="product-feature-grid">
338 + #foreach ($entry in $adminSupportItems)
339 + <article class="product-feature">
340 + <div class="card-heading">
341 + <div class="feature-icon">
342 + <i class="fa fa-$entry.icon" aria-hidden="true"></i>
343 + </div>
344 + <h3>$entry.title</h3>
345 + </div>
337 337  
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>
347 + <p>$entry.content</p>
348 + </article>
349 + #end
354 354   </div>
355 - </div>
356 -</section>
357 357  
358 358  {{/html}}
359 359  
360 360  {{gallery}}
361 -[[image:mfa-recovery-codes.png]]
362 -[[image:mfa-trusted-devices.png]]
355 +[[image:mfa-admin-user-management.png]]
363 363  {{/gallery}}
364 364  
365 365  {{html clean="false"}}
366 366  
367 -<section class="product-section-muted" aria-labelledby="profile-title">
360 + <p class="product-gallery-caption">
361 + Administrator view for checking and resetting a user setup.
362 + </p>
363 + </div>
364 +</section>
365 +
366 +<section aria-labelledby="faq-title">
368 368   <div class="container">
369 - <div class="product-layout">
370 - <article class="product-summary-card">
371 - <h2 id="profile-title">User and administrator management</h2>
368 + <h2 id="faq-title">Frequently asked questions</h2>
372 372  
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>
373 373   <p>
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.
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.
376 376   </p>
381 + </details>
377 377  
383 + <details class="resource-faq-item">
384 + <summary>Which verification method is used?</summary>
378 378   <p>
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.
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.
381 381   </p>
389 + </details>
382 382  
391 + <details class="resource-faq-item">
392 + <summary>Can the second verification step be required for all users?</summary>
383 383   <p>
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.
394 + Yes. Administrators can make the verification step optional or required for all users
395 + from the XWiki Administration section.
386 386   </p>
387 - </article>
397 + </details>
388 388  
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>
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>
400 400  
401 -{{/html}}
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>
402 402  
403 -{{gallery}}
404 -[[image:mfa-user-profile-overview.png]]
405 -[[image:mfa-admin-user-management.png]]
406 -{{/gallery}}
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>
407 407  
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>
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>
427 427   </div>
428 428  </section>
429 429  
430 -<section class="product-section-muted" aria-labelledby="planning-title">
436 +<section class="product-section-muted" aria-labelledby="rollout-title">
431 431   <div class="container">
432 432   <div class="product-layout">
433 433   <article class="product-summary-card">
434 - <h2 id="planning-title">Planning installation</h2>
440 + <h2 id="rollout-title">Rollout recommendations</h2>
435 435  
436 436   <p>
437 - Before installing or rolling out MFA, it is useful to review the current XWiki version,
438 - authentication setup, user base and security expectations.
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.
439 439   </p>
440 440  
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>
448 + <ol class="process-list">
449 + #foreach ($entry in $rolloutItems)
450 + <li>
451 + <strong>$entry.title</strong>
452 + $entry.content
453 + </li>
454 + #end
455 + </ol>
445 445   </article>
446 446  
447 - <aside class="product-info-card" aria-labelledby="planning-info-title">
448 - <h3 id="planning-info-title">Useful information before installation</h3>
458 + <aside class="product-info-card" aria-labelledby="planning-title">
459 + <h3 id="planning-title">Useful information before installation</h3>
460 +
461 + <p class="product-card-note">
462 + These details help evaluate compatibility, rollout scope and configuration options.
463 + </p>
464 +
449 449   <ul>
450 450   <li>XWiki version</li>
451 451   <li>Single wiki or wiki farm with subwikis</li>
452 452   <li>Current authentication setup</li>
453 - <li>Optional or globally required MFA policy</li>
469 + <li>Optional or required rollout policy</li>
454 454   <li>Trusted-device policy</li>
455 455   <li>Recovery-code policy</li>
456 456   <li>Rollout communication needs</li>
... ... @@ -466,9 +466,7 @@
466 466   <h2 id="cta-title">Interested in using this extension?</h2>
467 467  
468 468   <p>
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.
485 + Send a short message with your XWiki version, current authentication setup and rollout goal.
472 472   </p>
473 473  
474 474   <a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Contact Agnease</a>
1-linkedin-2fa-authenticator.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Admin
Size
... ... @@ -1,0 +1,1 @@
1 +1.1 MB
Content
mfa-admin-configuration.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Admin
Size
... ... @@ -1,0 +1,1 @@
1 +125.3 KB
Content
mfa-admin-full.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Admin
Size
... ... @@ -1,0 +1,1 @@
1 +184.3 KB
Content
mfa-admin-overview.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Admin
Size
... ... @@ -1,0 +1,1 @@
1 +64.7 KB
Content
mfa-admin-user-management.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Admin
Size
... ... @@ -1,0 +1,1 @@
1 +90.8 KB
Content
mfa-login-verification-code.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Admin
Size
... ... @@ -1,0 +1,1 @@
1 +23.6 KB
Content
mfa-login-verification-setup.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Admin
Size
... ... @@ -1,0 +1,1 @@
1 +115.9 KB
Content
mfa-recovery-codes-generated.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Admin
Size
... ... @@ -1,0 +1,1 @@
1 +38.5 KB
Content
mfa-recovery-codes-not-generated.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Admin
Size
... ... @@ -1,0 +1,1 @@
1 +27.0 KB
Content
mfa-trusted-devices.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Admin
Size
... ... @@ -1,0 +1,1 @@
1 +59.1 KB
Content
mfa-user-profile-full.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Admin
Size
... ... @@ -1,0 +1,1 @@
1 +197.5 KB
Content
mfa-user-profile-overview.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Admin
Size
... ... @@ -1,0 +1,1 @@
1 +193.4 KB
Content
mfa-user-setup-qr.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Admin
Size
... ... @@ -1,0 +1,1 @@
1 +176.6 KB
Content