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)
-
Objects (0 modified, 0 added, 1 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - XWikiTwo-FactorAuthentication1 +xwiki-two-factor-authentication - Content
-
... ... @@ -1,98 +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': 'Simple MFA policy', 21 - 'icon': 'cog', 22 - 'content': 'Administrators can 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 -<div class="product-doc-page product-mfa-page"> 81 - 82 -<section class="hero hero-centered" aria-labelledby="product-title"> 6 +<section class="hero hero-centered product-hero" aria-labelledby="product-title"> 83 83 <div class="container hero-inner"> 84 84 <div class="hero-kicker"> 85 85 <i class="fa fa-lock" aria-hidden="true"></i> 86 - XWiki 2FAand MFA10 + XWiki security extension 87 87 </div> 88 88 89 89 <h1 id="product-title">XWiki Two-Factor Authentication</h1> 90 90 91 91 <p class="lead"> 92 - Protect XWiki logins with a second verification step using authenticator app codes, 93 - email verification codes, or both. 16 + Add a second verification step to the standard XWiki login flow. 94 94 </p> 95 95 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 + 96 96 <div class="hero-actions"> 97 97 <a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Ask about this extension</a> 98 98 <a class="btn btn-secondary" href="$xwiki.getURL('products.WebHome')">View all products</a> ... ... @@ -104,19 +104,25 @@ 104 104 <div class="container"> 105 105 <div class="product-layout"> 106 106 <article class="product-summary-card"> 107 - <h2 id="overview-title"> Two-factorauthenticationbuilt into XWiki</h2>35 + <h2 id="overview-title">Stronger login protection for XWiki</h2> 108 108 109 109 <p> 110 - XWiki Two-Factor Authentication adds MFA/2FA support tothe standardXWiki login flow.111 - Users continue to signin with their normalusername and password,then confirmaccesswith112 - 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. 113 113 </p> 114 114 115 115 <p> 116 - The extension supports authenticator app codes, email-delivered verification codes, or a combined117 - s etupwhere both methods are required.Itisdesignedtoimproveaccountprotectionwithout replacing118 - thefamiliarXWikiauthenticationexperience.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. 119 119 </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> 120 120 </article> 121 121 122 122 <aside class="product-info-card" aria-labelledby="quick-facts-title"> ... ... @@ -123,12 +123,12 @@ 123 123 <h3 id="quick-facts-title">Quick facts</h3> 124 124 <ul> 125 125 <li>Works with the standard XWiki login flow</li> 126 - <li>Supports TOTPauthenticator applications</li>127 - <li>Supports email-delivered one-time codes</li> 128 - <li>Can require app and email verificationtogether</li>129 - <li> Includesrecoverycodesforbackupaccess</li>130 - <li> Canremembertrustedbrowsersordevices</li>131 - <li> Includesadministrationand user controls</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> 132 132 </ul> 133 133 </aside> 134 134 </div> ... ... @@ -135,210 +135,190 @@ 135 135 </div> 136 136 </section> 137 137 138 -<section aria-labelledby=" capabilities-title">72 +<section aria-labelledby="features-title"> 139 139 <div class="container"> 140 - <h2 id="capabilities-title">Main capabilities</h2> 141 - 74 + <h2 id="features-title">Main capabilities</h2> 142 142 <p class="section-intro"> 143 - A focused set of MFA/2FA features for stronger XWiki account protection without changing the standard login experience. 76 + The extension focuses on adding a practical second authentication step while keeping the standard XWiki login 77 + process and administration experience understandable. 144 144 </p> 145 145 146 146 <div class="product-feature-grid"> 147 - #foreach ($entry in $mainCapabilityItems) 148 - <article class="product-feature"> 149 - <div class="card-heading"> 150 - <div class="feature-icon"> 151 - <i class="fa fa-$entry.icon" aria-hidden="true"></i> 152 - </div> 153 - <h3>$entry.title</h3> 154 - </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> 155 155 156 - <p>$entry.content</p> 157 - </article> 158 - #end 159 - </div> 160 - </div> 161 -</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> 162 162 163 -<section class="product-section-muted" aria-labelledby="security-title"> 164 - <div class="container"> 165 - <div class="product-layout"> 166 - <article class="product-summary-card"> 167 - <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> 168 168 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> 169 169 <p> 170 - Many organizations need multi-factor authentication for internal tools, knowledge bases, 171 - intranets, documentation platforms and systems containing operational or sensitive information. 118 + The extension can also require both an authenticator app code and an email code for stricter multi-factor verification. 172 172 </p> 120 + </article> 173 173 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> 174 174 <p> 175 - For XWiki, adding two-factor authentication directly to the standard login flow helps protect 176 - administrator accounts, remote users, 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. 177 177 </p> 178 178 </article> 179 179 180 - <aside class="product-info-card" aria-labelledby="use-cases-title"> 181 - <h3 id="use-cases-title">Typical use cases</h3> 182 - <ul> 183 - <li>Administrator account protection</li> 184 - <li>Internal knowledge base security</li> 185 - <li>Private documentation platforms</li> 186 - <li>Remote user access protection</li> 187 - <li>Customer or partner portals</li> 188 - <li>Security review and NIS 2 readiness initiatives</li> 189 - </ul> 190 - </aside> 191 - </div> 192 - </div> 193 -</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> 194 194 195 -<section aria-labelledby="admin-experience-title"> 196 - <div class="container"> 197 - <h2 id="admin-experience-title">Administrator experience</h2> 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> 147 + <p> 148 + Administrators can configure MFA behavior, manage user activation, and reset user setup when required. 149 + </p> 150 + </article> 198 198 199 - <p class="section-intro"> 200 - Administrators can configure the MFA policy, monitor adoption and reset user MFA setups when needed. 201 - </p> 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> 157 + <p> 158 + The extension adds user profile controls so the second-factor setup can be reviewed or reset from XWiki. 159 + </p> 160 + </article> 202 202 203 - < divclass="product-feature-grid">204 - #foreach($entryin$adminExperienceItems)205 - < articleclass="product-feature">206 - <divclass="card-heading">207 - <div class="feature-icon">208 - <i class="fa fa-$entry.icon" aria-hidden="true"></i>209 - </div>210 - <h3>$entry.title</h3>211 - </div>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> 167 + <p> 168 + The extension can fall back to standard XWiki authentication when the feature is not enabled or not configured. 169 + </p> 170 + </article> 212 212 213 - <p>$entry.content</p> 214 - </article> 215 - #end 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> 177 + <p> 178 + The extension is designed to support XWiki environments using the main wiki and subwikis. 179 + </p> 180 + </article> 216 216 </div> 217 - 218 - <p class="product-gallery-caption"> 219 - Administration screens for configuring MFA and reviewing MFA adoption across users. 220 - </p> 221 221 </div> 222 222 </section> 223 223 224 -{{/html}} 225 - 226 -{{gallery}} 227 -[[image:mfa-admin-configuration.png]] 228 -[[image:mfa-admin-overview.png]] 229 -{{/gallery}} 230 - 231 -{{html clean="false"}} 232 - 233 -<section class="product-section-muted" aria-labelledby="user-experience-title"> 185 +<section aria-labelledby="use-cases-title"> 234 234 <div class="container"> 235 - <h2 id="user-experience-title">User experience</h2> 187 + <div class="product-layout"> 188 + <article class="product-summary-card"> 189 + <h2 id="use-cases-title">When this extension is useful</h2> 236 236 237 - <p class="section-intro"> 238 - Users can configure MFA from their profile and complete the second verification step during login. 239 - </p> 191 + <p> 192 + Two-factor authentication is especially relevant when XWiki contains internal documentation, procedures, 193 + customer information, project knowledge, administrative pages, or business-critical content. 194 + </p> 240 240 241 - <div class="product-feature-grid"> 242 - #foreach ($entry in $userExperienceItems) 243 - <article class="product-feature"> 244 - <div class="card-heading"> 245 - <div class="feature-icon"> 246 - <i class="fa fa-$entry.icon" aria-hidden="true"></i> 247 - </div> 248 - <h3>$entry.title</h3> 249 - </div> 196 + <p> 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. 200 + </p> 250 250 251 - <p>$entry.content</p> 252 - </article> 253 - #end 254 - </div> 202 + <p> 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. 205 + </p> 206 + </article> 255 255 256 - <p class="product-gallery-caption"> 257 - User setup and login verification screens. 258 - </p> 259 - </div> 260 -</section> 261 - 262 -{{/html}} 263 - 264 -{{gallery}} 265 -[[image:mfa-user-setup-qr.png]] 266 -[[image:mfa-login-verification.png]] 267 -{{/gallery}} 268 - 269 -{{html clean="false"}} 270 - 271 -<section aria-labelledby="recovery-title"> 272 - <div class="container"> 273 - <h2 id="recovery-title">Recovery codes and trusted devices</h2> 274 - 275 - <p class="section-intro"> 276 - Recovery codes and trusted devices help balance stronger access protection with a smoother user experience. 277 - </p> 278 - 279 - <div class="product-feature-grid"> 280 - #foreach ($entry in $recoveryItems) 281 - <article class="product-feature"> 282 - <div class="card-heading"> 283 - <div class="feature-icon"> 284 - <i class="fa fa-$entry.icon" aria-hidden="true"></i> 285 - </div> 286 - <h3>$entry.title</h3> 287 - </div> 288 - 289 - <p>$entry.content</p> 290 - </article> 291 - #end 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> 292 292 </div> 293 - 294 - <p class="product-gallery-caption"> 295 - Recovery codes, trusted devices and user profile management. 296 - </p> 297 297 </div> 298 298 </section> 299 299 300 -{{/html}} 301 - 302 -{{gallery}} 303 -[[image:mfa-recovery-codes.png]] 304 -[[image:mfa-trusted-devices.png]] 305 -[[image:mfa-user-profile-overview.png]] 306 -[[image:mfa-admin-user-management.png]] 307 -{{/gallery}} 308 - 309 -{{html clean="false"}} 310 - 311 -<section class="product-section-muted" aria-labelledby="rollout-title"> 222 +<section class="product-section-muted" aria-labelledby="compliance-title"> 312 312 <div class="container"> 313 313 <div class="product-layout"> 314 314 <article class="product-summary-card"> 315 - <h2 id=" rollout-title">Rolloutrecommendations</h2>226 + <h2 id="compliance-title">Useful for MFA adoption and NIS 2 readiness</h2> 316 316 317 317 <p> 318 - For a smooth rollout, start with a small administrator or pilot group before requiring MFA for everyone. 319 - This helps validate the configuration, prepare user communication and reduce support issues. 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. 320 320 </p> 321 321 322 - <ol class="process-list"> 323 - #foreach ($entry in $rolloutItems) 324 - <li> 325 - <strong>$entry.title</strong> 326 - $entry.content 327 - </li> 328 - #end 329 - </ol> 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> 239 + 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. 245 + </p> 330 330 </article> 331 331 332 - <aside class="product-info-card" aria-labelledby=" planning-title">333 - <h3 id=" planning-title">Useful informationbefore installation</h3>248 + <aside class="product-info-card" aria-labelledby="mfa-readiness-title"> 249 + <h3 id="mfa-readiness-title">Security controls supported</h3> 334 334 <ul> 335 - <li>XWiki version</li> 336 - <li>Single wiki or wiki farm with subwikis</li> 337 - <li>Current authentication setup</li> 338 - <li>Optional or globally required MFA policy</li> 339 - <li>Trusted-device policy</li> 340 - <li>Recovery-code policy</li> 341 - <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> 342 342 </ul> 343 343 </aside> 344 344 </div> ... ... @@ -345,23 +345,35 @@ 345 345 </div> 346 346 </section> 347 347 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 +*# 348 348 <section class="cta-section" aria-labelledby="cta-title"> 349 349 <div class="container"> 350 350 <div class="cta-panel"> 351 351 <h2 id="cta-title">Interested in using this extension?</h2> 352 - 353 353 <p> 354 - Send a short message with your XWiki version, authentication setup and whether you need 355 - authenticator app codes, email verification codes, combined verification, recovery codes 356 - or trusted-device remembering. 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. 357 357 </p> 358 - 359 359 <a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Contact Agnease</a> 360 360 </div> 361 361 </div> 362 362 </section> 363 363 364 -</div> 365 - 366 366 {{/html}} 367 367 {{/velocity}}
- 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