Changes for page XWiki Two-Factor Authentication
Last modified by Agnease on 2026/06/29 13:22
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 12 added, 0 removed)
- 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, 1 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - xwiki-two-factor-authentication1 +XWiki Two-Factor Authentication - Content
-
... ... @@ -1,26 +1,141 @@ 1 1 {{velocity}} 2 2 #set ($discard = $xwiki.ssx.use('PublicWebSite.WebHome')) 3 3 #set ($discard = $xwiki.ssx.use('products.WebHome')) 4 + 5 +#set ($businessValueItems = [{ 6 + 'title': 'Reduce account compromise risk', 7 + 'icon': 'shield', 8 + 'content': 'Add a second verification step after password login to better protect private XWiki content and administrator accounts.' 9 +},{ 10 + 'title': 'Keep the standard XWiki experience', 11 + 'icon': 'sign-in', 12 + 'content': 'Extend the familiar XWiki login flow instead of replacing it with a completely different authentication experience.' 13 +},{ 14 + 'title': 'Support a controlled rollout', 15 + 'icon': 'tasks', 16 + 'content': 'Start with optional MFA, then require MFA for all users when the organization is ready.' 17 +}]) 18 + 19 +#set ($adminControlItems = [{ 20 + 'title': 'Global MFA policy', 21 + 'icon': 'cog', 22 + 'content': 'Administrators can decide whether MFA is optional or required for all users.' 23 +},{ 24 + 'title': 'Recovery policy', 25 + 'icon': 'life-ring', 26 + 'content': 'Configure how many one-time recovery codes are generated for each user, or disable recovery codes if needed.' 27 +},{ 28 + 'title': 'Trusted-device policy', 29 + 'icon': 'desktop', 30 + 'content': 'Configure how long a trusted browser remains valid, or disable trusted devices for stricter environments.' 31 +}]) 32 + 33 +#set ($adminVisibilityItems = [{ 34 + 'title': 'MFA adoption overview', 35 + 'icon': 'bar-chart', 36 + 'content': 'Review how many users are scanned, how many have MFA configured, and how many still need attention.' 37 +},{ 38 + 'title': 'Filterable user table', 39 + 'icon': 'table', 40 + 'content': 'Use the Live Data table to review configured users, recovery-code status and trusted-device usage.' 41 +},{ 42 + 'title': 'Operational monitoring', 43 + 'icon': 'search', 44 + 'content': 'Identify accounts with missing recovery codes or trusted devices from the administration area.' 45 +}]) 46 + 47 +#set ($userAdoptionItems = [{ 48 + 'title': 'Self-service setup', 49 + 'icon': 'qrcode', 50 + 'content': 'Users can configure MFA by scanning a QR code with their authenticator application.' 51 +},{ 52 + 'title': 'Manual setup details', 53 + 'icon': 'keyboard-o', 54 + 'content': 'Users can also enter the account name and secret key manually if they cannot scan the QR code.' 55 +},{ 56 + 'title': 'Enforced setup flow', 57 + 'icon': 'lock', 58 + 'content': 'When MFA is required, users are guided to complete setup before continuing.' 59 +}]) 60 + 61 +#set ($loginProtectionItems = [{ 62 + 'title': 'Second login step', 63 + 'icon': 'key', 64 + 'content': 'After the normal username and password login, users enter the verification code from their authenticator app.' 65 +},{ 66 + 'title': 'Backup login option', 67 + 'icon': 'unlock-alt', 68 + 'content': 'If recovery codes are enabled, users can use a recovery code when they lose access to the authenticator app.' 69 +},{ 70 + 'title': 'Trusted browser option', 71 + 'icon': 'desktop', 72 + 'content': 'Users can trust the current browser for the configured duration after successful verification.' 73 +}]) 74 + 75 +#set ($continuityItems = [{ 76 + 'title': 'One-time recovery codes', 77 + 'icon': 'life-ring', 78 + 'content': 'Recovery codes help users regain access if they lose their authenticator device.' 79 +},{ 80 + 'icon': 'life-ring', 81 + 'content': 'Recovery codes help users regain access if they lose their authenticator device.' 82 +},{ 83 + 'title': 'Codes shown once', 84 + 'icon': 'eye-slash', 85 + 'content': 'Recovery codes are displayed only once and each code can be used a single time.' 86 +},{ 87 + 'title': 'Trusted-device management', 88 + 'icon': 'desktop', 89 + 'content': 'Users can review trusted devices, identify the current browser and remove devices they no longer use.' 90 +}]) 91 + 92 +#set ($adminSupportItems = [{ 93 + 'title': 'User MFA status', 94 + 'icon': 'user', 95 + 'content': 'Administrators can open a user profile and check whether MFA is configured for that account.' 96 +},{ 97 + 'title': 'Helpdesk recovery', 98 + 'icon': 'refresh', 99 + 'content': 'Administrators can reset MFA when a user loses access to the authenticator app or needs to restart setup.' 100 +},{ 101 + 'title': 'Clean reset', 102 + 'icon': 'trash', 103 + 'content': 'Resetting MFA removes the authenticator setup, recovery codes and trusted devices for that user.' 104 +}]) 105 + 106 +#set ($rolloutItems = [{ 107 + 'title': 'Start with a pilot group', 108 + 'content': 'Test the extension with administrators or a small user group before enabling it widely.' 109 +},{ 110 + 'title': 'Define the MFA policy', 111 + 'content': 'Decide whether MFA should be optional at first or required for all users.' 112 +},{ 113 + 'title': 'Configure recovery options', 114 + 'content': 'Choose the number of recovery codes and whether trusted devices should be allowed.' 115 +},{ 116 + 'title': 'Prepare user communication', 117 + 'content': 'Explain how users configure MFA, save recovery codes and manage trusted devices.' 118 +},{ 119 + 'title': 'Monitor adoption', 120 + 'content': 'Use the administration overview to identify users who still need to configure MFA.' 121 +}]) 122 + 4 4 {{html clean="false"}} 5 5 6 -<section class="hero hero-centered product-hero" aria-labelledby="product-title">125 +<section class="hero hero-centered" aria-labelledby="product-title"> 7 7 <div class="container hero-inner"> 8 8 <div class="hero-kicker"> 9 9 <i class="fa fa-lock" aria-hidden="true"></i> 10 - XWiki securityextension129 + XWiki 2FA and MFA 11 11 </div> 12 12 13 13 <h1 id="product-title">XWiki Two-Factor Authentication</h1> 14 14 15 15 <p class="lead"> 16 - Add a second verification step to the standard XWiki login flow. 135 + Protect XWiki logins with authenticator app verification, recovery codes, trusted devices 136 + and administrator visibility. 17 17 </p> 18 18 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> 23 - 24 24 <div class="hero-actions"> 25 25 <a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Ask about this extension</a> 26 26 <a class="btn btn-secondary" href="$xwiki.getURL('products.WebHome')">View all products</a> ... ... @@ -32,25 +32,19 @@ 32 32 <div class="container"> 33 33 <div class="product-layout"> 34 34 <article class="product-summary-card"> 35 - <h2 id="overview-title"> Strongerloginprotection for XWiki</h2>150 + <h2 id="overview-title">MFA protection built for XWiki</h2> 36 36 37 37 <p> 38 - TheXWikiMFA /Two-Factor Authenticationextensionadds additionalverificationafterthe standard39 - XWiki username and passwordlogin. Itstrengthensaccount protectionwithoutreplacing the familiar40 - XWikiauthenticationflow.153 + XWiki Two-Factor Authentication adds a second verification step to the standard XWiki login flow. 154 + Users continue to sign in with their normal username and password, then confirm access with a 155 + time-based code generated by an authenticator application. 41 41 </p> 42 42 43 43 <p> 44 - The extension s upportsauthenticatorappcodesusingTOTP,email-deliveredone-timeverificationcodes,45 - and stricter configurations where both verificationmethodsarerequired.Thisallows organizationsto46 - choose between asimpler2FA setupor a strongermulti-stepMFA policy.159 + The extension is designed for organizations that use XWiki to manage internal documentation, 160 + procedures, knowledge bases, customer portals or other private collaboration spaces where 161 + stronger account protection is needed. 47 47 </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> 54 54 </article> 55 55 56 56 <aside class="product-info-card" aria-labelledby="quick-facts-title"> ... ... @@ -57,13 +57,12 @@ 57 57 <h3 id="quick-facts-title">Quick facts</h3> 58 58 <ul> 59 59 <li>Works with the standard XWiki login flow</li> 60 - <li>Supports authenticator app verification codes</li> 61 - <li>Supports email-delivered verification codes</li> 62 - <li>Can remember trusted clients beyond the current session</li> 63 - <li>Configuration available from wiki administration</li> 64 - <li>User setup available during login or from the user profile</li> 65 - <li>Administrators can enable, disable or reset MFA for users</li> 66 - <li>Can be used on the main wiki and subwikis</li> 169 + <li>Uses TOTP authenticator applications</li> 170 + <li>Can require MFA for all users</li> 171 + <li>Includes one-time recovery codes</li> 172 + <li>Supports trusted browsers or devices</li> 173 + <li>Includes user self-service controls</li> 174 + <li>Includes administration monitoring</li> 67 67 </ul> 68 68 </aside> 69 69 </div> ... ... @@ -70,177 +70,295 @@ 70 70 </div> 71 71 </section> 72 72 73 -<section aria-labelledby=" features-title">181 +<section class="product-section-muted" aria-labelledby="business-value-title"> 74 74 <div class="container"> 75 - <h2 id="features-title">Main capabilities</h2> 183 + <h2 id="business-value-title">Business value</h2> 184 + 76 76 <p class="section-intro"> 77 - The extension focuses on adding a practical second authentication step while keeping the standard XWiki login 78 - process and administration experience understandable. 186 + The extension helps organizations strengthen XWiki access protection without making login and account recovery unnecessarily complex. 79 79 </p> 80 80 81 81 <div class="product-feature-grid"> 82 - <article class="product-feature"> 83 - <div class="feature-icon"> 84 - <i class="fa fa-key" aria-hidden="true"></i> 85 - </div> 86 - <h3>Second login step</h3> 87 - <p> 88 - After the username and password are verified, users are asked to enter an additional verification code 89 - before accessing the wiki. 90 - </p> 91 - </article> 190 + #foreach ($entry in $businessValueItems) 191 + <article class="product-feature"> 192 + <div class="card-heading"> 193 + <div class="feature-icon"> 194 + <i class="fa fa-$entry.icon" aria-hidden="true"></i> 195 + </div> 196 + <h3>$entry.title</h3> 197 + </div> 92 92 93 - <article class="product-feature"> 94 - <div class="feature-icon"> 95 - <i class="fa fa-mobile" aria-hidden="true"></i> 96 - </div> 97 - <h3>Authenticator app codes</h3> 98 - <p> 99 - Users can verify access with codes generated by authenticator applications, such as mobile TOTP apps. 100 - </p> 101 - </article> 199 + <p>$entry.content</p> 200 + </article> 201 + #end 202 + </div> 203 + </div> 204 +</section> 102 102 103 - <article class="product-feature"> 104 - <div class="feature-icon"> 105 - <i class="fa fa-envelope-o" aria-hidden="true"></i> 106 - </div> 107 - <h3>Email verification codes</h3> 108 - <p> 109 - Users can also receive a verification code by email, useful when an authenticator app is not available. 110 - </p> 111 - </article> 206 +<section aria-labelledby="admin-control-title"> 207 + <div class="container"> 208 + <h2 id="admin-control-title">Administrator control</h2> 112 112 113 - <article class="product-feature"> 114 - <div class="feature-icon"> 115 - <i class="fa fa-qrcode" aria-hidden="true"></i> 116 - </div> 117 - <h3>User setup screen</h3> 118 - <p> 119 - Users can configure their verification code setup during login or from their XWiki profile when needed. 120 - </p> 121 - </article> 210 + <p class="section-intro"> 211 + Administrators configure the MFA policy directly from the XWiki Administration section, without editing configuration files for day-to-day policy changes. 212 + </p> 122 122 123 - <article class="product-feature"> 124 - <div class="feature-icon"> 125 - <i class="fa fa-clock-o" aria-hidden="true"></i> 126 - </div> 127 - <h3>Remember trusted clients</h3> 128 - <p> 129 - Trusted browsers can be remembered beyond the current session, reducing repeated MFA prompts while keeping 130 - the second factor active for new or untrusted clients. 131 - </p> 132 - </article> 214 + <div class="product-feature-grid"> 215 + #foreach ($entry in $adminControlItems) 216 + <article class="product-feature"> 217 + <div class="card-heading"> 218 + <div class="feature-icon"> 219 + <i class="fa fa-$entry.icon" aria-hidden="true"></i> 220 + </div> 221 + <h3>$entry.title</h3> 222 + </div> 133 133 134 - <article class="product-feature"> 135 - <div class="feature-icon"> 136 - <i class="fa fa-sliders" aria-hidden="true"></i> 137 - </div> 138 - <h3>Administration controls</h3> 139 - <p> 140 - Administrators can enable the feature globally, manage user-level activation, and reset a user setup when required. 141 - </p> 142 - </article> 224 + <p>$entry.content</p> 225 + </article> 226 + #end 227 + </div> 143 143 144 - <article class="product-feature"> 145 - <div class="feature-icon"> 146 - <i class="fa fa-user" aria-hidden="true"></i> 147 - </div> 148 - <h3>Profile integration</h3> 149 - <p> 150 - The extension adds user profile controls so the second-factor setup can be reviewed or reset from XWiki. 151 - </p> 152 - </article> 229 +{{/html}} 153 153 154 - <article class="product-feature"> 155 - <div class="feature-icon"> 156 - <i class="fa fa-random" aria-hidden="true"></i> 157 - </div> 158 - <h3>Fallback behavior</h3> 159 - <p> 160 - The extension can fall back to standard XWiki authentication when the feature is not enabled or not configured. 161 - </p> 162 - </article> 231 +{{gallery}} 232 +[[image:mfa-admin-configuration.png]] 233 +{{/gallery}} 163 163 164 - <article class="product-feature"> 165 - <div class="feature-icon"> 166 - <i class="fa fa-sitemap" aria-hidden="true"></i> 167 - </div> 168 - <h3>Main wiki and subwikis</h3> 169 - <p> 170 - The extension is designed to support XWiki environments using the main wiki and subwikis. 171 - </p> 172 - </article> 235 +{{html clean="false"}} 236 + 237 + <p class="product-gallery-caption"> 238 + Administration configuration for requiring MFA, setting the authenticator issuer name, recovery-code count and trusted-device duration. 239 + </p> 240 + </div> 241 +</section> 242 + 243 +<section class="product-section-muted" aria-labelledby="admin-visibility-title"> 244 + <div class="container"> 245 + <h2 id="admin-visibility-title">Administration overview and monitoring</h2> 246 + 247 + <p class="section-intro"> 248 + The administration overview helps teams understand MFA adoption and identify users who still need to complete setup or maintain recovery options. 249 + </p> 250 + 251 + <div class="product-feature-grid"> 252 + #foreach ($entry in $adminVisibilityItems) 253 + <article class="product-feature"> 254 + <div class="card-heading"> 255 + <div class="feature-icon"> 256 + <i class="fa fa-$entry.icon" aria-hidden="true"></i> 257 + </div> 258 + <h3>$entry.title</h3> 259 + </div> 260 + 261 + <p>$entry.content</p> 262 + </article> 263 + #end 173 173 </div> 265 + 266 +{{/html}} 267 + 268 +{{gallery}} 269 +[[image:mfa-admin-overview.png]] 270 +[[image:mfa-admin-full.png]] 271 +{{/gallery}} 272 + 273 +{{html clean="false"}} 274 + 275 + <p class="product-gallery-caption"> 276 + MFA adoption indicators and a filterable user overview for administrators. 277 + </p> 174 174 </div> 175 175 </section> 176 176 177 -<section aria-labelledby="use- cases-title">281 +<section aria-labelledby="user-adoption-title"> 178 178 <div class="container"> 179 - <div class="product-layout"> 180 - <article class="product-summary-card"> 181 - <h2 id="use-cases-title">When this extension is useful</h2> 283 + <h2 id="user-adoption-title">User setup and adoption</h2> 182 182 183 - <p> 184 - Two-factor authentication is especially relevant when XWiki contains internal documentation, procedures, 185 - customer information, project knowledge, administrative pages, or business-critical content. 186 - </p> 285 + <p class="section-intro"> 286 + Users can configure MFA themselves by scanning a QR code or entering the setup information manually in their authenticator application. 287 + </p> 187 187 188 - <p> 189 - It can also support organizations that need MFA as part of their cybersecurity controls, including companies 190 - working toward NIS 2 readiness. NIS 2 focuses on stronger cybersecurity risk management across essential and 191 - important entities in the EU, and MFA is often expected as part of enterprise access protection programs. 192 - </p> 289 + <div class="product-feature-grid"> 290 + #foreach ($entry in $userAdoptionItems) 291 + <article class="product-feature"> 292 + <div class="card-heading"> 293 + <div class="feature-icon"> 294 + <i class="fa fa-$entry.icon" aria-hidden="true"></i> 295 + </div> 296 + <h3>$entry.title</h3> 297 + </div> 193 193 194 - <p> 195 - It is also useful when many users access the wiki remotely, when administrator accounts need stronger protection, 196 - or when the organization wants to reduce the risk of compromised passwords. 197 - </p> 198 - </article> 299 + <p>$entry.content</p> 300 + </article> 301 + #end 302 + </div> 199 199 200 - <aside class="product-info-card" aria-labelledby="good-fit-title"> 201 - <h3 id="good-fit-title">Good fit for</h3> 202 - <ul> 203 - <li>Private XWiki knowledge bases</li> 204 - <li>Company intranets</li> 205 - <li>SOP and controlled-document platforms</li> 206 - <li>Documentation portals with sensitive content</li> 207 - <li>Wikis with several administrators or remote users</li> 208 - </ul> 209 - </aside> 304 +{{/html}} 305 + 306 +{{gallery}} 307 +[[image:mfa-user-setup-qr.png]] 308 +[[image:mfa-login-verification-setup.png]] 309 +{{/gallery}} 310 + 311 +{{html clean="false"}} 312 + 313 + <p class="product-gallery-caption"> 314 + Profile-based setup and enforced setup during login when MFA is required. 315 + </p> 316 + </div> 317 +</section> 318 + 319 +<section class="product-section-muted" aria-labelledby="login-protection-title"> 320 + <div class="container"> 321 + <h2 id="login-protection-title">Login protection</h2> 322 + 323 + <p class="section-intro"> 324 + After MFA is configured, XWiki asks for a verification code after the normal username and password step. 325 + </p> 326 + 327 + <div class="product-feature-grid"> 328 + #foreach ($entry in $loginProtectionItems) 329 + <article class="product-feature"> 330 + <div class="card-heading"> 331 + <div class="feature-icon"> 332 + <i class="fa fa-$entry.icon" aria-hidden="true"></i> 333 + </div> 334 + <h3>$entry.title</h3> 335 + </div> 336 + 337 + <p>$entry.content</p> 338 + </article> 339 + #end 210 210 </div> 341 + 342 +{{/html}} 343 + 344 +{{gallery}} 345 +[[image:mfa-login-verification-code.png]] 346 +{{/gallery}} 347 + 348 +{{html clean="false"}} 349 + 350 + <p class="product-gallery-caption"> 351 + Verification screen displayed after the standard XWiki username and password login. 352 + </p> 211 211 </div> 212 212 </section> 213 213 214 -<section class="product-section-muted"aria-labelledby="compliance-title">356 +<section aria-labelledby="continuity-title"> 215 215 <div class="container"> 358 + <h2 id="continuity-title">Recovery codes and trusted devices</h2> 359 + 360 + <p class="section-intro"> 361 + Recovery codes and trusted devices help balance stronger access protection with practical day-to-day usability. 362 + </p> 363 + 364 + <div class="product-feature-grid"> 365 + #foreach ($entry in $continuityItems) 366 + <article class="product-feature"> 367 + <div class="card-heading"> 368 + <div class="feature-icon"> 369 + <i class="fa fa-$entry.icon" aria-hidden="true"></i> 370 + </div> 371 + <h3>$entry.title</h3> 372 + </div> 373 + 374 + <p>$entry.content</p> 375 + </article> 376 + #end 377 + </div> 378 + 379 +{{/html}} 380 + 381 +{{gallery}} 382 +[[image:mfa-recovery-codes-not-generated.png]] 383 +[[image:mfa-recovery-codes-generated.png]] 384 +[[image:mfa-trusted-devices.png]] 385 +[[image:mfa-user-profile-overview.png]] 386 +[[image:mfa-user-profile-full.png]] 387 +{{/gallery}} 388 + 389 +{{html clean="false"}} 390 + 391 + <p class="product-gallery-caption"> 392 + User profile screens for recovery-code generation, trusted-device review and MFA self-service management. 393 + </p> 394 + </div> 395 +</section> 396 + 397 +<section class="product-section-muted" aria-labelledby="admin-support-title"> 398 + <div class="container"> 399 + <h2 id="admin-support-title">Administrator support and user recovery</h2> 400 + 401 + <p class="section-intro"> 402 + Administrators can help users recover from lost devices or restart MFA setup when needed. 403 + </p> 404 + 405 + <div class="product-feature-grid"> 406 + #foreach ($entry in $adminSupportItems) 407 + <article class="product-feature"> 408 + <div class="card-heading"> 409 + <div class="feature-icon"> 410 + <i class="fa fa-$entry.icon" aria-hidden="true"></i> 411 + </div> 412 + <h3>$entry.title</h3> 413 + </div> 414 + 415 + <p>$entry.content</p> 416 + </article> 417 + #end 418 + </div> 419 + 420 +{{/html}} 421 + 422 +{{gallery}} 423 +[[image:mfa-admin-user-management.png]] 424 +{{/gallery}} 425 + 426 +{{html clean="false"}} 427 + 428 + <p class="product-gallery-caption"> 429 + Administrator view for checking and resetting a user MFA setup. 430 + </p> 431 + </div> 432 +</section> 433 + 434 +<section aria-labelledby="rollout-title"> 435 + <div class="container"> 216 216 <div class="product-layout"> 217 217 <article class="product-summary-card"> 218 - <h2 id=" compliance-title">Usefulfor MFA adoptionand NIS 2readiness</h2>438 + <h2 id="rollout-title">Rollout recommendations</h2> 219 219 220 220 <p> 221 - Manyorganizationsnowneedmulti-factorauthenticationfor enterprisesoftware,especiallywhenthe222 - plat formcontains internal documentation, procedures,operationalknowledge or sensitive business data.441 + For a smooth rollout, start with a small administrator or pilot group before requiring MFA for everyone. 442 + This helps validate the configuration, prepare user communication and reduce support issues. 223 223 </p> 224 224 225 - <p> 226 - For organizations using XWiki as a knowledge platform, having MFA embedded in the standard XWiki login 227 - experience helps close a practical security gap without requiring a full replacement of the authentication flow. 228 - </p> 445 + <ol class="process-list"> 446 + #foreach ($entry in $rolloutItems) 447 + <li> 448 + <strong>$entry.title</strong> 449 + $entry.content 450 + </li> 451 + #end 452 + </ol> 453 + </article> 229 229 230 - <p> 231 - This can be relevant for companies preparing for NIS 2 requirements, where MFA is part of a broader 232 - cybersecurity risk management and access protection strategy. 455 + <aside class="product-info-card" aria-labelledby="planning-title"> 456 + <h3 id="planning-title">Useful information before installation</h3> 457 + 458 + <p class="product-card-note"> 459 + These details help evaluate compatibility, rollout scope and configuration options. 233 233 </p> 234 - </article> 235 235 236 - <aside class="product-info-card" aria-labelledby="mfa-readiness-title"> 237 - <h3 id="mfa-readiness-title">Security controls supported</h3> 238 238 <ul> 239 - <li>Second-factor verification after password login</li> 240 - <li>Authenticator app or email-based verification codes</li> 241 - <li>Reduced repeated prompts for trusted clients</li> 242 - <li>Administration controls for user-level MFA management</li> 243 - <li>Better protection for administrator and remote-access accounts</li> 463 + <li>XWiki version</li> 464 + <li>Single wiki or wiki farm with subwikis</li> 465 + <li>Current authentication setup</li> 466 + <li>Optional or globally required MFA policy</li> 467 + <li>Trusted-device policy</li> 468 + <li>Recovery-code policy</li> 469 + <li>Rollout communication needs</li> 244 244 </ul> 245 245 </aside> 246 246 </div> ... ... @@ -247,31 +247,15 @@ 247 247 </div> 248 248 </section> 249 249 250 -#* 251 -<section aria-labelledby="gallery-title"> 252 - <div class="container"> 253 - <div class="product-gallery-panel"> 254 - <h2 id="gallery-title">Screenshots</h2> 255 - <p class="gallery-note"> 256 - Use this area to show the login verification screen, first-time setup, user profile controls, 257 - and administration configuration. 258 - </p> 259 - 260 - <div class="product-gallery-placeholder"> 261 - Replace this placeholder with the XWiki gallery macro and 3-5 screenshots from the application. 262 - </div> 263 - </div> 264 - </div> 265 -</section> 266 -*# 267 267 <section class="cta-section" aria-labelledby="cta-title"> 268 268 <div class="container"> 269 269 <div class="cta-panel"> 270 270 <h2 id="cta-title">Interested in using this extension?</h2> 480 + 271 271 <p> 272 - Send a short message with your XWiki version, authentication setup, and whether you use a single wiki 273 - or a main wiki with subwikis. 482 + Send a short message with your XWiki version, current authentication setup and MFA rollout goal. 274 274 </p> 484 + 275 275 <a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Contact Agnease</a> 276 276 </div> 277 277 </div>
- 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 +26.9 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
- Agnease.Code.SEODetailsClass[0]
-
- metaDescription
-
... ... @@ -1,0 +1,1 @@ 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,0 +1,1 @@ 1 +XWiki Two-Factor Authentication with 2FA and MFA Support | Agnease