Changes for page XWiki Two-Factor Authentication
Last modified by Alex Cotiuga on 2026/07/13 06:59
From version 30.7
edited by Alex Cotiuga
on 2026/07/13 06:59
on 2026/07/13 06:59
Change comment:
There is no comment for this version
To version 1.15
edited by Alex Cotiuga
on 2026/05/22 03:46
on 2026/05/22 03:46
Change comment:
There is no comment for this version
Summary
-
Page properties (4 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 13 removed)
- 2fa-authenticator.png
- mfa-admin-configuration.png
- mfa-admin-full.png
- mfa-admin-overview.png
- mfa-admin-user-management.png
- mfa-login-verification-code.png
- mfa-login-verification-setup.png
- mfa-recovery-codes-generated.png
- mfa-recovery-codes-not-generated.png
- mfa-trusted-devices.png
- mfa-user-profile-full.png
- mfa-user-profile-overview.png
- mfa-user-setup-qr.png
-
Objects (0 modified, 0 added, 1 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - XWikiTwo-FactorAuthentication1 +xwiki-two-factor-authentication - Default language
-
... ... @@ -1,0 +1,1 @@ 1 +en - Hidden
-
... ... @@ -1,1 +1,1 @@ 1 - true1 +false - Content
-
... ... @@ -1,118 +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 withMFA rolloutsupport10 + 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 - <ul class="benefits"> 108 - <li><strong>Extension from €75/year</strong></li> 109 - <li><strong>Basic setup from €150</strong></li> 110 - <li>MFA rollout support available</li> 111 - </ul> 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> 112 112 113 113 <div class="hero-actions"> 114 114 <a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Ask about this extension</a> 115 - <a class="btn btn-secondary" href="$xwiki.getURL('pr icing.WebHome')#common-packages">ViewMFAsetupprice</a>26 + <a class="btn btn-secondary" href="$xwiki.getURL('products.WebHome')">View all products</a> 116 116 </div> 117 117 </div> 118 118 </section> ... ... @@ -121,19 +121,25 @@ 121 121 <div class="container"> 122 122 <div class="product-layout"> 123 123 <article class="product-summary-card"> 124 - <h2 id="overview-title"> Two-factorauthenticationbuilt into XWiki</h2>35 + <h2 id="overview-title">Stronger login protection for XWiki</h2> 125 125 126 126 <p> 127 - XWiki Two-Factor Authentication adds a n additional verificationstepto the standard128 - XWiki login flow.Users continuetosigninwiththeirnormalusernameand password,129 - then confirm access withatime-based code from an authenticatorapplication.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. 130 130 </p> 131 131 132 132 <p> 133 - The applicationhasevolvedbeyondasimplelogin-codescreen.Itsupportsglobal134 - enforcement,recoverycodes,trusteddevices,userself-service,administrator135 - resetactionsandan overviewformonitoringadoption.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. 136 136 </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> 137 137 </article> 138 138 139 139 <aside class="product-info-card" aria-labelledby="quick-facts-title"> ... ... @@ -140,12 +140,12 @@ 140 140 <h3 id="quick-facts-title">Quick facts</h3> 141 141 <ul> 142 142 <li>Works with the standard XWiki login flow</li> 143 - <li>Supports TOTPauthenticator applications</li>144 - <li> Can requireadditionalverificationfor all users</li>145 - <li> Includesone-timerecoverycodes</li>146 - <li>Can remember trusted browsers or devices</li> 147 - <li>Includes user self-service controls</li>148 - <li> Includesanadministrationoverview</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> 149 149 </ul> 150 150 </aside> 151 151 </div> ... ... @@ -152,330 +152,190 @@ 152 152 </div> 153 153 </section> 154 154 155 -<section aria-labelledby=" capabilities-title">72 +<section aria-labelledby="features-title"> 156 156 <div class="container"> 157 - <h2 id="capabilities-title">Main capabilities</h2> 158 - 74 + <h2 id="features-title">Main capabilities</h2> 159 159 <p class="section-intro"> 160 - Afocusedset ofauthenticationprotectionfeaturesforstronger XWikiaccount security161 - withoutreplacingthe familiarlogin experience.76 + The extension focuses on adding a practical second authentication step while keeping the standard XWiki login 77 + process and administration experience understandable. 162 162 </p> 163 163 164 164 <div class="product-feature-grid"> 165 - #foreach ($entry in $mainCapabilityItems) 166 - <article class="product-feature"> 167 - <div class="card-heading"> 168 - <div class="feature-icon"> 169 - <i class="fa fa-$entry.icon" aria-hidden="true"></i> 170 - </div> 171 - <h3>$entry.title</h3> 172 - </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> 173 173 174 - <p>$entry.content</p> 175 - </article> 176 - #end 177 - </div> 178 - </div> 179 -</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> 180 180 181 -<section class="product-section-muted" aria-labelledby="security-title"> 182 - <div class="container"> 183 - <div class="product-layout"> 184 - <article class="product-summary-card"> 185 - <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> 186 186 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> 187 187 <p> 188 - Many organizations use XWiki to store internal documentation, procedures, operational 189 - knowledge and business-critical information. Adding an additional authentication factor helps 190 - 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. 191 191 </p> 120 + </article> 192 192 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> 193 193 <p> 194 - The extension is especially useful for protecting administrator accounts, remote users, 195 - 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. 196 196 </p> 197 197 </article> 198 198 199 - <aside class="product-info-card" aria-labelledby="use-cases-title"> 200 - <h3 id="use-cases-title">Typical use cases</h3> 201 - <ul> 202 - <li>Administrator account protection</li> 203 - <li>Internal knowledge base security</li> 204 - <li>Private documentation platforms</li> 205 - <li>Remote user access protection</li> 206 - <li>Customer or partner portals</li> 207 - <li>Security review, MFA rollout and compliance readiness</li> 208 - </ul> 209 - </aside> 210 - </div> 211 - </div> 212 -</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> 213 213 214 -<section aria-labelledby="admin-experience-title"> 215 - <div class="container"> 216 - <h2 id="admin-experience-title">Administrator configuration and monitoring</h2> 217 - 218 - <p class="section-intro"> 219 - Administrators can configure the policy, define recovery options and monitor adoption 220 - from the XWiki Administration section. 221 - </p> 222 - 223 - <div class="product-feature-grid"> 224 - #foreach ($entry in $adminExperienceItems) 225 - <article class="product-feature"> 226 - <div class="card-heading"> 227 - <div class="feature-icon"> 228 - <i class="fa fa-$entry.icon" aria-hidden="true"></i> 229 - </div> 230 - <h3>$entry.title</h3> 231 - </div> 232 - 233 - <p>$entry.content</p> 234 - </article> 235 - #end 236 - </div> 237 - 238 -{{/html}} 239 - 240 -{{gallery}} 241 -[[image:mfa-admin-configuration.png]] 242 -[[image:mfa-admin-overview.png]] 243 -[[image:mfa-admin-full.png]] 244 -{{/gallery}} 245 - 246 -{{html clean="false"}} 247 - 248 - <p class="product-gallery-caption"> 249 - Administration screens for configuring the policy and reviewing adoption across users. 250 - </p> 251 - </div> 252 -</section> 253 - 254 -<section class="product-section-muted" aria-labelledby="user-experience-title"> 255 - <div class="container"> 256 - <h2 id="user-experience-title">User setup and login verification</h2> 257 - 258 - <p class="section-intro"> 259 - Users can configure the authenticator app from their profile or during the enforced setup flow, 260 - then verify future logins with a generated code. 261 - </p> 262 - 263 - <div class="product-feature-grid"> 264 - #foreach ($entry in $userExperienceItems) 265 - <article class="product-feature"> 266 - <div class="card-heading"> 267 - <div class="feature-icon"> 268 - <i class="fa fa-$entry.icon" aria-hidden="true"></i> 269 - </div> 270 - <h3>$entry.title</h3> 271 - </div> 272 - 273 - <p>$entry.content</p> 274 - </article> 275 - #end 276 - </div> 277 - 278 -{{/html}} 279 - 280 -{{gallery}} 281 -[[image:mfa-user-setup-qr.png]] 282 -[[image:mfa-login-verification-setup.png]] 283 -[[image:mfa-login-verification-code.png]] 284 -{{/gallery}} 285 - 286 -{{html clean="false"}} 287 - 288 - <p class="product-gallery-caption"> 289 - User setup, enforced configuration and login verification screens. 290 - </p> 291 - </div> 292 -</section> 293 - 294 -<section aria-labelledby="self-service-title"> 295 - <div class="container"> 296 - <h2 id="self-service-title">Recovery codes and trusted devices</h2> 297 - 298 - <p class="section-intro"> 299 - Recovery codes and trusted devices help balance stronger access protection with a smoother user experience. 300 - </p> 301 - 302 - <div class="product-feature-grid"> 303 - #foreach ($entry in $selfServiceItems) 304 - <article class="product-feature"> 305 - <div class="card-heading"> 306 - <div class="feature-icon"> 307 - <i class="fa fa-$entry.icon" aria-hidden="true"></i> 308 - </div> 309 - <h3>$entry.title</h3> 310 - </div> 311 - 312 - <p>$entry.content</p> 313 - </article> 314 - #end 315 - </div> 316 - 317 -{{/html}} 318 - 319 -{{gallery}} 320 -[[image:mfa-user-profile-overview.png]] 321 -[[image:mfa-recovery-codes-not-generated.png]] 322 -[[image:mfa-recovery-codes-generated.png]] 323 -[[image:mfa-trusted-devices.png]] 324 -[[image:mfa-user-profile-full.png]] 325 -{{/gallery}} 326 - 327 -{{html clean="false"}} 328 - 329 - <p class="product-gallery-caption"> 330 - User profile screens for recovery codes, trusted devices and self-service management. 331 - </p> 332 - </div> 333 -</section> 334 - 335 -<section class="product-section-muted" aria-labelledby="admin-support-title"> 336 - <div class="container"> 337 - <h2 id="admin-support-title">Administrator support and user recovery</h2> 338 - 339 - <p class="section-intro"> 340 - Administrators can help users recover from lost devices or restart setup when needed. 341 - </p> 342 - 343 - <div class="product-feature-grid"> 344 - #foreach ($entry in $adminSupportItems) 345 - <article class="product-feature"> 346 - <div class="card-heading"> 347 - <div class="feature-icon"> 348 - <i class="fa fa-$entry.icon" aria-hidden="true"></i> 349 - </div> 350 - <h3>$entry.title</h3> 351 - </div> 352 - 353 - <p>$entry.content</p> 354 - </article> 355 - #end 356 - </div> 357 - 358 -{{/html}} 359 - 360 -{{gallery}} 361 -[[image:mfa-admin-user-management.png]] 362 -{{/gallery}} 363 - 364 -{{html clean="false"}} 365 - 366 - <p class="product-gallery-caption"> 367 - Administrator view for checking and resetting a user setup. 368 - </p> 369 - </div> 370 -</section> 371 - 372 -<section aria-labelledby="faq-title"> 373 - <div class="container"> 374 - <h2 id="faq-title">Frequently asked questions</h2> 375 - 376 - <p class="section-intro"> 377 - Common questions about how the extension works, how users configure it and how administrators can manage rollout and recovery. 378 - </p> 379 - 380 - <div class="resource-content"> 381 - <details class="resource-faq-item"> 382 - <summary>Does this extension replace the standard XWiki login?</summary> 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> 383 383 <p> 384 - No. Users still sign in with their normal XWiki username and password. The extension adds 385 - an additional verification step after the standard login check. 148 + Administrators can configure MFA behavior, manage user activation, and reset user setup when required. 386 386 </p> 387 - </ details>150 + </article> 388 388 389 - <details class="resource-faq-item"> 390 - <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> 391 391 <p> 392 - Users verify access with time-based codes generated by an authenticator application. 393 - The setup page provides a QR code and a manual setup key. 158 + The extension adds user profile controls so the second-factor setup can be reviewed or reset from XWiki. 394 394 </p> 395 - </ details>160 + </article> 396 396 397 - <details class="resource-faq-item"> 398 - <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> 399 399 <p> 400 - Yes. Administrators can make the verification step optional or required for all users 401 - from the XWiki Administration section. 168 + The extension can fall back to standard XWiki authentication when the feature is not enabled or not configured. 402 402 </p> 403 - </ details>170 + </article> 404 404 405 - <details class="resource-faq-item"> 406 - <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> 407 407 <p> 408 - Recovery codes can provide backup access when enabled. Administrators can also reset 409 - the user setup so the configuration process can be restarted. 178 + The extension is designed to support XWiki environments using the main wiki and subwikis. 410 410 </p> 411 - </details> 180 + </article> 181 + </div> 182 + </div> 183 +</section> 412 412 413 - <details class="resource-faq-item"> 414 - <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 + 415 415 <p> 416 - Yes. Administratorscanconfigurehowlongtrusteddevicesremainvalid.Settingthe417 - trusted-deviceduration to0disablesthis 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. 418 418 </p> 419 - </details> 420 420 421 - <details class="resource-faq-item"> 422 - <summary>Is this only a basic 2FA login-code screen?</summary> 423 423 <p> 424 - No.The main loginmechanism is two-factorauthentication,butthe applicationalsoincludes425 - featuresneededforasaferorganization-wide rollout:enforcementpolicy,recoverycodes,426 - trusteddevices,userself-service, administratormonitoringand administratorresetactions.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. 427 427 </p> 428 - </details> 429 429 430 - <details class="resource-faq-item"> 431 - <summary>Is this enough for compliance on its own?</summary> 432 432 <p> 433 - No. This extension provides an important access-protection control, but it should be part 434 - of a broader security and compliance approach that includes permissions, upgrades, 435 - infrastructure, monitoring and operational procedures. 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. 436 436 </p> 437 - </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> 438 438 </div> 439 439 </div> 440 440 </section> 441 441 442 -<section class="product-section-muted" aria-labelledby=" rollout-title">222 +<section class="product-section-muted" aria-labelledby="compliance-title"> 443 443 <div class="container"> 444 444 <div class="product-layout"> 445 445 <article class="product-summary-card"> 446 - <h2 id=" rollout-title">Rolloutrecommendations</h2>226 + <h2 id="compliance-title">Useful for MFA adoption and NIS 2 readiness</h2> 447 447 448 448 <p> 449 - Forasmoothrollout, start withasmalladministratororpilotgroupbefore requiring450 - the additional verificationstepforeveryone. Thishelps validate theconfiguration,451 - prepareuser communicationand reducesupportissues.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. 452 452 </p> 453 453 454 - <ol class="process-list"> 455 - #foreach ($entry in $rolloutItems) 456 - <li> 457 - <strong>$entry.title</strong> 458 - $entry.content 459 - </li> 460 - #end 461 - </ol> 462 - </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> 463 463 464 - <asideclass="product-info-card"aria-labelledby="planning-title">465 - <h3id="planning-title">Usefulinformationbefore installation</h3>466 - 467 - <p class="product-card-note">468 - These detailshelp evaluatecompatibility,rolloutscopeandconfigurationoptions.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. 469 469 </p> 246 + </article> 470 470 248 + <aside class="product-info-card" aria-labelledby="mfa-readiness-title"> 249 + <h3 id="mfa-readiness-title">Security controls supported</h3> 471 471 <ul> 472 - <li>XWiki version</li> 473 - <li>Single wiki or wiki farm with subwikis</li> 474 - <li>Current authentication setup</li> 475 - <li>Optional or required rollout policy</li> 476 - <li>Trusted-device policy</li> 477 - <li>Recovery-code policy</li> 478 - <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> 479 479 </ul> 480 480 </aside> 481 481 </div> ... ... @@ -482,17 +482,32 @@ 482 482 </div> 483 483 </section> 484 484 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 +*# 485 485 <section class="cta-section" aria-labelledby="cta-title"> 486 486 <div class="container"> 487 487 <div class="cta-panel"> 488 488 <h2 id="cta-title">Interested in using this extension?</h2> 489 - 490 490 <p> 491 - 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. 492 492 </p> 493 - 494 494 <a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Contact Agnease</a> 495 - <a class="btn btn-secondary" href="$xwiki.getURL('pricing.WebHome')#common-packages">View MFA setup price</a> 496 496 </div> 497 497 </div> 498 498 </section>
- 2fa-authenticator.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Admin - Size
-
... ... @@ -1,1 +1,0 @@ 1 -1.1 MB - Content
- mfa-admin-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