Changes for page XWiki Two-Factor Authentication
Last modified by Agnease on 2026/06/24 16:39
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,5 +1,6 @@ 1 1 {{velocity}} 2 2 #set ($discard = $xwiki.ssx.use('PublicWebSite.WebHome')) 3 +#set ($discard = $xwiki.ssx.use('products.WebHome')) 3 3 4 4 #set ($mainCapabilityItems = [{ 5 5 'title': 'Second verification step', ... ... @@ -10,40 +10,40 @@ 10 10 'icon': 'mobile', 11 11 'content': 'Let users verify access with time-based TOTP codes generated by authenticator applications.' 12 12 },{ 13 - 'title': ' Recoveryandtrusteddevices',14 - 'icon': ' shield',15 - 'content': ' Providebackup access with recoverycodes andreducerepeatedpromptsontrustedbrowsers.'14 + 'title': 'Email verification codes', 15 + 'icon': 'envelope-o', 16 + 'content': 'Send one-time verification codes by email when this method is enabled or combined with app codes.' 16 16 }]) 17 17 18 18 #set ($adminExperienceItems = [{ 19 - 'title': ' Rolloutpolicy',20 + 'title': 'MFA policy', 20 20 'icon': 'cog', 21 - 'content': 'Make additionalverification optionalat firstor required for all users from the XWiki Administration section.'22 + 'content': 'Make MFA optional or required for all users from the XWiki Administration section.' 22 22 },{ 23 - 'title': ' Configurationoptions',24 - 'icon': 's liders',25 - 'content': ' Set the authenticator issuername,recovery-code count and trusted-device duration.'24 + 'title': 'Recovery and trusted devices', 25 + 'icon': 'shield', 26 + 'content': 'Configure recovery-code count and trusted-device duration according to the organization security policy.' 26 26 },{ 27 27 'title': 'Administration overview', 28 28 'icon': 'table', 29 - 'content': 'Review adoption with summary indicators and a filterable Live Data table.' 30 + 'content': 'Review MFA adoption across users with summary indicators and a filterable Live Data table.' 30 30 }]) 31 31 32 32 #set ($userExperienceItems = [{ 33 33 'title': 'Self-service setup', 34 34 'icon': 'qrcode', 35 - 'content': 'Users configure thesecond verification step from their profile by scanning a QR code or entering the setup key manually.'36 + 'content': 'Users configure MFA from their profile by scanning a QR code or entering the setup key manually.' 36 36 },{ 37 - 'title': ' Loginverification',38 + 'title': 'Familiar login flow', 38 38 'icon': 'sign-in', 39 - 'content': 'After the normal login, users enter the verification code generatedby theirauthenticatorapp.'40 + 'content': 'After the normal login, users enter the configured verification code before accessing XWiki.' 40 40 },{ 41 - 'title': ' Trusted browseroption',42 - 'icon': ' desktop',43 - 'content': 'Users can trustthe currentbrowserfor theconfigureddurationaftersuccessfulverification.'42 + 'title': 'Profile management', 43 + 'icon': 'user', 44 + 'content': 'Users can review MFA status, manage recovery codes and remove trusted devices from their profile.' 44 44 }]) 45 45 46 -#set ($ selfServiceItems = [{47 +#set ($recoveryItems = [{ 47 47 'title': 'Recovery codes', 48 48 'icon': 'life-ring', 49 49 'content': 'Recovery codes provide backup access when a user loses access to the authenticator application.' ... ... @@ -50,25 +50,11 @@ 50 50 },{ 51 51 'title': 'Trusted devices', 52 52 'icon': 'desktop', 53 - 'content': 'Trusted devices can bereviewedandremovedfromtheuser profile.'54 + 'content': 'Trusted browsers or devices can skip repeated MFA prompts for a configured period.' 54 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', 56 + 'title': 'Administrator reset', 66 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.' 58 + 'content': 'Administrators can reset a user MFA setup when the user needs to restart the configuration process.' 72 72 }]) 73 73 74 74 #set ($rolloutItems = [{ ... ... @@ -75,17 +75,17 @@ 75 75 'title': 'Start with a pilot group', 76 76 'content': 'Test the extension with administrators or a small user group before enabling it widely.' 77 77 },{ 78 - 'title': 'Define the rolloutpolicy',79 - 'content': 'Decide whether additionalverificationshould be optionalatfirst or required for all users.'65 + 'title': 'Define the MFA policy', 66 + 'content': 'Decide whether MFA should be optional, required for administrators, or required for all users.' 80 80 },{ 81 81 'title': 'Configure recovery options', 82 - 'content': 'Choose the numberofrecovery codes andwhethertrusted devices should be allowed.'69 + 'content': 'Choose whether recovery codes and trusted devices should be enabled.' 83 83 },{ 84 84 'title': 'Inform users', 85 - 'content': 'Explain how users configure the authenticator app, save recovery codes and manage trusted devices.'72 + 'content': 'Explain how users configure MFA, save recovery codes and manage trusted devices.' 86 86 },{ 87 87 'title': 'Monitor adoption', 88 - 'content': 'Use the administration overview to identify users who still need to configure protection.'75 + 'content': 'Use the administration overview to identify users who still need to configure MFA.' 89 89 }]) 90 90 91 91 {{html clean="false"}} ... ... @@ -94,14 +94,14 @@ 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 withMFArollout support84 + 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 a uthenticatorappverification,recoverycodes,104 - trusteddevices and administration controlsfora safer rollout.90 + Protect XWiki logins with a second verification step using authenticator app codes, 91 + email verification codes, or both. 105 105 </p> 106 106 107 107 <div class="hero-actions"> ... ... @@ -118,15 +118,15 @@ 118 118 <h2 id="overview-title">Two-factor authentication built into XWiki</h2> 119 119 120 120 <p> 121 - XWiki Two-Factor Authentication adds anadditional verificationstep to the standard122 - XWiki login flow.Users continue to sign in with their normal username and password,123 - thenconfirmaccess with a time-based code from anauthenticatorapplication.108 + XWiki Two-Factor Authentication adds MFA/2FA support to the standard XWiki login flow. 109 + Users continue to sign in with their normal username and password, then confirm access with 110 + an additional verification method. 124 124 </p> 125 125 126 126 <p> 127 - The applicationhas evolved beyond asimple login-codescreen.It supportsglobal128 - e nforcement,recoverycodes,trusted devices,userself-service,administrator129 - resetactionsand an overview for monitoring adoption.114 + The extension supports authenticator app codes, email-delivered verification codes, or a combined 115 + setup where both methods are required. It improves account protection without replacing the familiar 116 + XWiki authentication experience. 130 130 </p> 131 131 </article> 132 132 ... ... @@ -135,11 +135,11 @@ 135 135 <ul> 136 136 <li>Works with the standard XWiki login flow</li> 137 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> 125 + <li>Supports email-delivered one-time codes</li> 126 + <li>Can require app and email verification together</li> 127 + <li>Includes recovery codes for backup access</li> 140 140 <li>Can remember trusted browsers or devices</li> 141 - <li>Includes user self-service controls</li> 142 - <li>Includes an administration overview</li> 129 + <li>Includes administration and user controls</li> 143 143 </ul> 144 144 </aside> 145 145 </div> ... ... @@ -151,8 +151,7 @@ 151 151 <h2 id="capabilities-title">Main capabilities</h2> 152 152 153 153 <p class="section-intro"> 154 - A focused set of authentication protection features for stronger XWiki account security 155 - without replacing the familiar login experience. 141 + A focused set of MFA/2FA features for stronger XWiki account protection without changing the standard login experience. 156 156 </p> 157 157 158 158 <div class="product-feature-grid"> ... ... @@ -179,14 +179,13 @@ 179 179 <h2 id="security-title">Useful for XWiki security and access protection</h2> 180 180 181 181 <p> 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. 168 + Many organizations need multi-factor authentication for internal tools, knowledge bases, 169 + intranets, documentation platforms and systems containing operational or sensitive information. 185 185 </p> 186 186 187 187 <p> 188 - The extensionis especiallyuseful forprotectingadministratoraccounts,remoteusers,189 - private knowledge bases and customer or partner portals. 173 + For XWiki, adding two-factor authentication directly to the standard login flow helps protect 174 + administrator accounts, remote users, private knowledge bases and customer or partner portals. 190 190 </p> 191 191 </article> 192 192 ... ... @@ -198,7 +198,7 @@ 198 198 <li>Private documentation platforms</li> 199 199 <li>Remote user access protection</li> 200 200 <li>Customer or partner portals</li> 201 - <li>Security review ,MFA rolloutandcompliancereadiness</li>186 + <li>Security review and NIS 2 readiness initiatives</li> 202 202 </ul> 203 203 </aside> 204 204 </div> ... ... @@ -207,11 +207,10 @@ 207 207 208 208 <section aria-labelledby="admin-experience-title"> 209 209 <div class="container"> 210 - <h2 id="admin-experience-title">Administrator configurationand monitoring</h2>195 + <h2 id="admin-experience-title">Administrator experience</h2> 211 211 212 212 <p class="section-intro"> 213 - Administrators can configure the policy, define recovery options and monitor adoption 214 - from the XWiki Administration section. 198 + Administrators can configure the MFA policy, monitor adoption and reset user MFA setups when needed. 215 215 </p> 216 216 217 217 <div class="product-feature-grid"> ... ... @@ -240,7 +240,7 @@ 240 240 {{html clean="false"}} 241 241 242 242 <p class="product-gallery-caption"> 243 - Administration screens for configuring thepolicyand reviewing adoption across users.227 + Administration screens for configuring MFA and reviewing MFA adoption across users. 244 244 </p> 245 245 </div> 246 246 </section> ... ... @@ -247,11 +247,10 @@ 247 247 248 248 <section class="product-section-muted" aria-labelledby="user-experience-title"> 249 249 <div class="container"> 250 - <h2 id="user-experience-title">User setupand login verification</h2>234 + <h2 id="user-experience-title">User experience</h2> 251 251 252 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. 237 + Users can configure MFA from their profile and complete the second verification step during login. 255 255 </p> 256 256 257 257 <div class="product-feature-grid"> ... ... @@ -280,14 +280,14 @@ 280 280 {{html clean="false"}} 281 281 282 282 <p class="product-gallery-caption"> 283 - User setup ,enforced configurationand login verification screens.266 + User setup and login verification screens. 284 284 </p> 285 285 </div> 286 286 </section> 287 287 288 -<section aria-labelledby=" self-service-title">271 +<section aria-labelledby="recovery-title"> 289 289 <div class="container"> 290 - <h2 id=" self-service-title">Recovery codes and trusted devices</h2>273 + <h2 id="recovery-title">Recovery codes and trusted devices</h2> 291 291 292 292 <p class="section-intro"> 293 293 Recovery codes and trusted devices help balance stronger access protection with a smoother user experience. ... ... @@ -294,7 +294,7 @@ 294 294 </p> 295 295 296 296 <div class="product-feature-grid"> 297 - #foreach ($entry in $ selfServiceItems)280 + #foreach ($entry in $recoveryItems) 298 298 <article class="product-feature"> 299 299 <div class="card-heading"> 300 300 <div class="feature-icon"> ... ... @@ -311,10 +311,10 @@ 311 311 {{/html}} 312 312 313 313 {{gallery}} 314 -[[image:mfa-user-profile-overview.png]] 315 315 [[image:mfa-recovery-codes-not-generated.png]] 316 316 [[image:mfa-recovery-codes-generated.png]] 317 317 [[image:mfa-trusted-devices.png]] 300 +[[image:mfa-admin-user-management.png]] 318 318 [[image:mfa-user-profile-full.png]] 319 319 {{/gallery}} 320 320 ... ... @@ -321,118 +321,11 @@ 321 321 {{html clean="false"}} 322 322 323 323 <p class="product-gallery-caption"> 324 - User profile screens for recovery codes, trusted devices and self-service management.307 + Recovery codes, trusted devices and user profile management. 325 325 </p> 326 326 </div> 327 327 </section> 328 328 329 -<section class="product-section-muted" aria-labelledby="admin-support-title"> 330 - <div class="container"> 331 - <h2 id="admin-support-title">Administrator support and user recovery</h2> 332 - 333 - <p class="section-intro"> 334 - Administrators can help users recover from lost devices or restart setup when needed. 335 - </p> 336 - 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> 346 - 347 - <p>$entry.content</p> 348 - </article> 349 - #end 350 - </div> 351 - 352 -{{/html}} 353 - 354 -{{gallery}} 355 -[[image:mfa-admin-user-management.png]] 356 -{{/gallery}} 357 - 358 -{{html clean="false"}} 359 - 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"> 367 - <div class="container"> 368 - <h2 id="faq-title">Frequently asked questions</h2> 369 - 370 - <p class="section-intro"> 371 - Common questions about how the extension works, how users configure it and how administrators can manage rollout and recovery. 372 - </p> 373 - 374 - <div class="resource-content"> 375 - <details class="resource-faq-item"> 376 - <summary>Does this extension replace the standard XWiki login?</summary> 377 - <p> 378 - No. Users still sign in with their normal XWiki username and password. The extension adds 379 - an additional verification step after the standard login check. 380 - </p> 381 - </details> 382 - 383 - <details class="resource-faq-item"> 384 - <summary>Which verification method is used?</summary> 385 - <p> 386 - Users verify access with time-based codes generated by an authenticator application. 387 - The setup page provides a QR code and a manual setup key. 388 - </p> 389 - </details> 390 - 391 - <details class="resource-faq-item"> 392 - <summary>Can the second verification step be required for all users?</summary> 393 - <p> 394 - Yes. Administrators can make the verification step optional or required for all users 395 - from the XWiki Administration section. 396 - </p> 397 - </details> 398 - 399 - <details class="resource-faq-item"> 400 - <summary>What happens if a user loses access to the authenticator app?</summary> 401 - <p> 402 - Recovery codes can provide backup access when enabled. Administrators can also reset 403 - the user setup so the configuration process can be restarted. 404 - </p> 405 - </details> 406 - 407 - <details class="resource-faq-item"> 408 - <summary>Can trusted browsers or devices be disabled?</summary> 409 - <p> 410 - Yes. Administrators can configure how long trusted devices remain valid. Setting the 411 - trusted-device duration to 0 disables this option. 412 - </p> 413 - </details> 414 - 415 - <details class="resource-faq-item"> 416 - <summary>Is this only a basic 2FA login-code screen?</summary> 417 - <p> 418 - No. The main login mechanism is two-factor authentication, but the application also includes 419 - features needed for a safer organization-wide rollout: enforcement policy, recovery codes, 420 - trusted devices, user self-service, administrator monitoring and administrator reset actions. 421 - </p> 422 - </details> 423 - 424 - <details class="resource-faq-item"> 425 - <summary>Is this enough for compliance on its own?</summary> 426 - <p> 427 - No. This extension provides an important access-protection control, but it should be part 428 - of a broader security and compliance approach that includes permissions, upgrades, 429 - infrastructure, monitoring and operational procedures. 430 - </p> 431 - </details> 432 - </div> 433 - </div> 434 -</section> 435 - 436 436 <section class="product-section-muted" aria-labelledby="rollout-title"> 437 437 <div class="container"> 438 438 <div class="product-layout"> ... ... @@ -440,9 +440,8 @@ 440 440 <h2 id="rollout-title">Rollout recommendations</h2> 441 441 442 442 <p> 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. 319 + For a smooth rollout, start with a small administrator or pilot group before requiring MFA for everyone. 320 + This helps validate the configuration, prepare user communication and reduce support issues. 446 446 </p> 447 447 448 448 <ol class="process-list"> ... ... @@ -466,7 +466,7 @@ 466 466 <li>XWiki version</li> 467 467 <li>Single wiki or wiki farm with subwikis</li> 468 468 <li>Current authentication setup</li> 469 - <li>Optional or required rolloutpolicy</li>344 + <li>Optional or globally required MFA policy</li> 470 470 <li>Trusted-device policy</li> 471 471 <li>Recovery-code policy</li> 472 472 <li>Rollout communication needs</li> ... ... @@ -482,7 +482,7 @@ 482 482 <h2 id="cta-title">Interested in using this extension?</h2> 483 483 484 484 <p> 485 - Send a short message with your XWiki version, current authentication setup and rollout goal. 360 + Send a short message with your XWiki version, current authentication setup and MFA rollout goal. 486 486 </p> 487 487 488 488 <a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Contact Agnease</a>
- mfa-admin-user-management.png
-
- Size
-
... ... @@ -1,1 +1,1 @@ 1 - 90.8KB1 +26.9 KB - Content