Changes for page XWiki Two-Factor Authentication
Last modified by Agnease on 2026/06/24 16:39
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 1 removed)
-
Objects (0 modified, 0 added, 1 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - XWikiTwo-FactorAuthentication1 +xwiki-two-factor-authentication - Content
-
... ... @@ -1,96 +1,26 @@ 1 1 {{velocity}} 2 2 #set ($discard = $xwiki.ssx.use('PublicWebSite.WebHome')) 3 3 #set ($discard = $xwiki.ssx.use('products.WebHome')) 4 - 5 -#set ($mainCapabilityItems = [{ 6 - 'title': 'Second verification step', 7 - 'icon': 'key', 8 - 'content': 'Add an additional verification screen after the normal XWiki username and password login.' 9 -},{ 10 - 'title': 'Authenticator app codes', 11 - 'icon': 'mobile', 12 - 'content': 'Let users verify access with time-based TOTP codes generated by authenticator applications.' 13 -},{ 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.' 17 -}]) 18 - 19 -#set ($adminExperienceItems = [{ 20 - 'title': 'MFA policy', 21 - 'icon': 'cog', 22 - 'content': 'Make MFA optional or required for all users from the XWiki Administration section.' 23 -},{ 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.' 27 -},{ 28 - 'title': 'Administration overview', 29 - 'icon': 'table', 30 - 'content': 'Review MFA adoption across users with summary indicators and a filterable Live Data table.' 31 -}]) 32 - 33 -#set ($userExperienceItems = [{ 34 - 'title': 'Self-service setup', 35 - 'icon': 'qrcode', 36 - 'content': 'Users configure MFA from their profile by scanning a QR code or entering the setup key manually.' 37 -},{ 38 - 'title': 'Familiar login flow', 39 - 'icon': 'sign-in', 40 - 'content': 'After the normal login, users enter the configured verification code before accessing XWiki.' 41 -},{ 42 - 'title': 'Profile management', 43 - 'icon': 'user', 44 - 'content': 'Users can review MFA status, manage recovery codes and remove trusted devices from their profile.' 45 -}]) 46 - 47 -#set ($recoveryItems = [{ 48 - 'title': 'Recovery codes', 49 - 'icon': 'life-ring', 50 - 'content': 'Recovery codes provide backup access when a user loses access to the authenticator application.' 51 -},{ 52 - 'title': 'Trusted devices', 53 - 'icon': 'desktop', 54 - 'content': 'Trusted browsers or devices can skip repeated MFA prompts for a configured period.' 55 -},{ 56 - 'title': 'Administrator reset', 57 - 'icon': 'refresh', 58 - 'content': 'Administrators can reset a user MFA setup when the user needs to restart the configuration process.' 59 -}]) 60 - 61 -#set ($rolloutItems = [{ 62 - 'title': 'Start with a pilot group', 63 - 'content': 'Test the extension with administrators or a small user group before enabling it widely.' 64 -},{ 65 - 'title': 'Define the MFA policy', 66 - 'content': 'Decide whether MFA should be optional, required for administrators, or required for all users.' 67 -},{ 68 - 'title': 'Configure recovery options', 69 - 'content': 'Choose whether recovery codes and trusted devices should be enabled.' 70 -},{ 71 - 'title': 'Inform users', 72 - 'content': 'Explain how users configure MFA, save recovery codes and manage trusted devices.' 73 -},{ 74 - 'title': 'Monitor adoption', 75 - 'content': 'Use the administration overview to identify users who still need to configure MFA.' 76 -}]) 77 - 78 78 {{html clean="false"}} 79 79 80 -<section class="hero hero-centered" aria-labelledby="product-title"> 6 +<section class="hero hero-centered product-hero" aria-labelledby="product-title"> 81 81 <div class="container hero-inner"> 82 82 <div class="hero-kicker"> 83 83 <i class="fa fa-lock" aria-hidden="true"></i> 84 - XWiki 2FAand MFA10 + XWiki security extension 85 85 </div> 86 86 87 87 <h1 id="product-title">XWiki Two-Factor Authentication</h1> 88 88 89 89 <p class="lead"> 90 - Protect XWiki logins with a second verification step using authenticator app codes, 91 - email verification codes, or both. 16 + Add a second verification step to the standard XWiki login flow. 92 92 </p> 93 93 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 + 94 94 <div class="hero-actions"> 95 95 <a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Ask about this extension</a> 96 96 <a class="btn btn-secondary" href="$xwiki.getURL('products.WebHome')">View all products</a> ... ... @@ -102,19 +102,25 @@ 102 102 <div class="container"> 103 103 <div class="product-layout"> 104 104 <article class="product-summary-card"> 105 - <h2 id="overview-title"> Two-factorauthenticationbuilt into XWiki</h2>35 + <h2 id="overview-title">Stronger login protection for XWiki</h2> 106 106 107 107 <p> 108 - XWiki Two-Factor Authentication adds MFA/2FA support tothe standardXWiki login flow.109 - Users continue to signin with their normalusername and password,then confirmaccesswith110 - an additionalverificationmethod.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. 111 111 </p> 112 112 113 113 <p> 114 - The extension supports authenticator app codes, email-delivered verification codes, or a combined115 - s etupwhere both methods are required.Itimproves accountprotectionwithout replacingthe familiar116 - XWikiauthenticationexperience.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. 117 117 </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> 118 118 </article> 119 119 120 120 <aside class="product-info-card" aria-labelledby="quick-facts-title"> ... ... @@ -121,12 +121,13 @@ 121 121 <h3 id="quick-facts-title">Quick facts</h3> 122 122 <ul> 123 123 <li>Works with the standard XWiki login flow</li> 124 - <li>Supports TOTP authenticator applications</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> 128 - <li>Can remember trusted browsers or devices</li> 129 - <li>Includes administration and user controls</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> 130 130 </ul> 131 131 </aside> 132 132 </div> ... ... @@ -133,210 +133,177 @@ 133 133 </div> 134 134 </section> 135 135 136 -<section aria-labelledby=" capabilities-title">73 +<section aria-labelledby="features-title"> 137 137 <div class="container"> 138 - <h2 id="capabilities-title">Main capabilities</h2> 139 - 75 + <h2 id="features-title">Main capabilities</h2> 140 140 <p class="section-intro"> 141 - A focused set of MFA/2FA features for stronger XWiki account protection without changing the standard login experience. 77 + The extension focuses on adding a practical second authentication step while keeping the standard XWiki login 78 + process and administration experience understandable. 142 142 </p> 143 143 144 144 <div class="product-feature-grid"> 145 - #foreach ($entry in $mainCapabilityItems) 146 - <article class="product-feature"> 147 - <div class="card-heading"> 148 - <div class="feature-icon"> 149 - <i class="fa fa-$entry.icon" aria-hidden="true"></i> 150 - </div> 151 - <h3>$entry.title</h3> 152 - </div> 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> 153 153 154 - <p>$entry.content</p> 155 - </article> 156 - #end 157 - </div> 158 - </div> 159 -</section> 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> 160 160 161 -<section class="product-section-muted" aria-labelledby="security-title"> 162 - <div class="container"> 163 - <div class="product-layout"> 164 - <article class="product-summary-card"> 165 - <h2 id="security-title">Useful for XWiki security and access protection</h2> 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> 166 166 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> 167 167 <p> 168 - Many organizations need multi-factor authentication for internal tools, knowledge bases, 169 - intranets, documentation platforms and systems containing operational or sensitive information. 119 + Users can configure their verification code setup during login or from their XWiki profile when needed. 170 170 </p> 121 + </article> 171 171 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> 172 172 <p> 173 - ForXWiki, addingtwo-factorauthenticationdirectlyto thestandardloginflow helpsprotect174 - administratoraccounts,remote users,privateknowledgebases and customerorpartnerportals.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. 175 175 </p> 176 176 </article> 177 177 178 - <aside class="product-info-card" aria-labelledby="use-cases-title"> 179 - <h3 id="use-cases-title">Typical use cases</h3> 180 - <ul> 181 - <li>Administrator account protection</li> 182 - <li>Internal knowledge base security</li> 183 - <li>Private documentation platforms</li> 184 - <li>Remote user access protection</li> 185 - <li>Customer or partner portals</li> 186 - <li>Security review and NIS 2 readiness initiatives</li> 187 - </ul> 188 - </aside> 189 - </div> 190 - </div> 191 -</section> 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> 192 192 193 -<section aria-labelledby="admin-experience-title"> 194 - <div class="container"> 195 - <h2 id="admin-experience-title">Administrator experience</h2> 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> 196 196 197 - <p class="section-intro"> 198 - Administrators can configure the MFA policy, monitor adoption and reset user MFA setups when needed. 199 - </p> 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> 200 200 201 - <div class="product-feature-grid"> 202 - #foreach ($entry in $adminExperienceItems) 203 - <article class="product-feature"> 204 - <div class="card-heading"> 205 - <div class="feature-icon"> 206 - <i class="fa fa-$entry.icon" aria-hidden="true"></i> 207 - </div> 208 - <h3>$entry.title</h3> 209 - </div> 210 - 211 - <p>$entry.content</p> 212 - </article> 213 - #end 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> 214 214 </div> 215 - 216 - <p class="product-gallery-caption"> 217 - Administration screens for configuring MFA and reviewing MFA adoption across users. 218 - </p> 219 219 </div> 220 220 </section> 221 221 222 -{{/html}} 223 - 224 -{{gallery}} 225 -[[image:mfa-admin-configuration.png]] 226 -[[image:mfa-admin-overview.png]] 227 -{{/gallery}} 228 - 229 -{{html clean="false"}} 230 - 231 -<section class="product-section-muted" aria-labelledby="user-experience-title"> 177 +<section aria-labelledby="use-cases-title"> 232 232 <div class="container"> 233 - <h2 id="user-experience-title">User experience</h2> 179 + <div class="product-layout"> 180 + <article class="product-summary-card"> 181 + <h2 id="use-cases-title">When this extension is useful</h2> 234 234 235 - <p class="section-intro"> 236 - Users can configure MFA from their profile and complete the second verification step during login. 237 - </p> 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> 238 238 239 - <div class="product-feature-grid"> 240 - #foreach ($entry in $userExperienceItems) 241 - <article class="product-feature"> 242 - <div class="card-heading"> 243 - <div class="feature-icon"> 244 - <i class="fa fa-$entry.icon" aria-hidden="true"></i> 245 - </div> 246 - <h3>$entry.title</h3> 247 - </div> 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> 248 248 249 - <p>$entry.content</p> 250 - </article> 251 - #end 252 - </div> 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> 253 253 254 - <p class="product-gallery-caption"> 255 - User setup and login verification screens. 256 - </p> 257 - </div> 258 -</section> 259 - 260 -{{/html}} 261 - 262 -{{gallery}} 263 -[[image:mfa-user-setup-qr.png]] 264 -[[image:mfa-login-verification.png]] 265 -{{/gallery}} 266 - 267 -{{html clean="false"}} 268 - 269 -<section aria-labelledby="recovery-title"> 270 - <div class="container"> 271 - <h2 id="recovery-title">Recovery codes and trusted devices</h2> 272 - 273 - <p class="section-intro"> 274 - Recovery codes and trusted devices help balance stronger access protection with a smoother user experience. 275 - </p> 276 - 277 - <div class="product-feature-grid"> 278 - #foreach ($entry in $recoveryItems) 279 - <article class="product-feature"> 280 - <div class="card-heading"> 281 - <div class="feature-icon"> 282 - <i class="fa fa-$entry.icon" aria-hidden="true"></i> 283 - </div> 284 - <h3>$entry.title</h3> 285 - </div> 286 - 287 - <p>$entry.content</p> 288 - </article> 289 - #end 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> 290 290 </div> 291 - 292 - <p class="product-gallery-caption"> 293 - Recovery codes, trusted devices and user profile management. 294 - </p> 295 295 </div> 296 296 </section> 297 297 298 -{{/html}} 299 - 300 -{{gallery}} 301 -[[image:mfa-recovery-codes.png]] 302 -[[image:mfa-trusted-devices.png]] 303 -[[image:mfa-user-profile-overview.png]] 304 -[[image:mfa-admin-user-management.png]] 305 -{{/gallery}} 306 - 307 -{{html clean="false"}} 308 - 309 -<section class="product-section-muted" aria-labelledby="rollout-title"> 214 +<section class="product-section-muted" aria-labelledby="compliance-title"> 310 310 <div class="container"> 311 311 <div class="product-layout"> 312 312 <article class="product-summary-card"> 313 - <h2 id=" rollout-title">Rolloutrecommendations</h2>218 + <h2 id="compliance-title">Useful for MFA adoption and NIS 2 readiness</h2> 314 314 315 315 <p> 316 - Forasmoothrollout, start withasmall administratoror pilotgroupbeforerequiringMFA for everyone.317 - This helps validatetheconfiguration, prepareusercommunicationandreducesupportissues.221 + Many organizations now need multi-factor authentication for enterprise software, especially when the 222 + platform contains internal documentation, procedures, operational knowledge or sensitive business data. 318 318 </p> 319 319 320 - <ol class="process-list"> 321 - #foreach ($entry in $rolloutItems) 322 - <li> 323 - <strong>$entry.title</strong> 324 - $entry.content 325 - </li> 326 - #end 327 - </ol> 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> 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. 233 + </p> 328 328 </article> 329 329 330 - <aside class="product-info-card" aria-labelledby=" planning-title">331 - <h3 id=" planning-title">Useful informationbefore installation</h3>236 + <aside class="product-info-card" aria-labelledby="mfa-readiness-title"> 237 + <h3 id="mfa-readiness-title">Security controls supported</h3> 332 332 <ul> 333 - <li>XWiki version</li> 334 - <li>Single wiki or wiki farm with subwikis</li> 335 - <li>Current authentication setup</li> 336 - <li>Optional or globally required MFA policy</li> 337 - <li>Trusted-device policy</li> 338 - <li>Recovery-code policy</li> 339 - <li>Rollout communication needs</li> 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> 340 340 </ul> 341 341 </aside> 342 342 </div> ... ... @@ -343,17 +343,31 @@ 343 343 </div> 344 344 </section> 345 345 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 +*# 346 346 <section class="cta-section" aria-labelledby="cta-title"> 347 347 <div class="container"> 348 348 <div class="cta-panel"> 349 349 <h2 id="cta-title">Interested in using this extension?</h2> 350 - 351 351 <p> 352 - Send a short message with your XWiki version, authentication setup and whether you need 353 - authenticator app codes, email verification codes, combined verification, recovery codes 354 - or trusted-device remembering. 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. 355 355 </p> 356 - 357 357 <a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Contact Agnease</a> 358 358 </div> 359 359 </div>
- mfa-admin-configuration.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Admin - Size
-
... ... @@ -1,1 +1,0 @@ 1 -123.2 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