Changes for page XWiki Two-Factor Authentication
Last modified by Agnease on 2026/05/23 18:56
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
-
... ... @@ -3,20 +3,24 @@ 3 3 #set ($discard = $xwiki.ssx.use('products.WebHome')) 4 4 {{html clean="false"}} 5 5 6 -<section class="hero hero-centered" aria-labelledby=" hero-title">6 +<section class="hero hero-centered product-hero" 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 2FAand MFA10 + XWiki security extension 11 11 </div> 12 12 13 13 <h1 id="product-title">XWiki Two-Factor Authentication</h1> 14 14 15 15 <p class="lead"> 16 - Protect XWiki logins with a second verification step using authenticator app codes, 17 - email verification codes, or both. 16 + Add a second verification step to the standard XWiki login flow. 18 18 </p> 19 19 19 + <p class="hero-support"> 20 + This extension protects XWiki accounts with an additional verification step after the standard username and password login. 21 + Users can verify access with an authenticator app code or an email-delivered code, while XWiki keeps its familiar login experience. 22 + </p> 23 + 20 20 <div class="hero-actions"> 21 21 <a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Ask about this extension</a> 22 22 <a class="btn btn-secondary" href="$xwiki.getURL('products.WebHome')">View all products</a> ... ... @@ -28,22 +28,23 @@ 28 28 <div class="container"> 29 29 <div class="product-layout"> 30 30 <article class="product-summary-card"> 31 - <h2 id="overview-title"> Two-factorauthenticationbuilt into XWiki</h2>35 + <h2 id="overview-title">Stronger login protection for XWiki</h2> 32 32 33 33 <p> 34 - XWiki Two-Factor Authentication adds an additional verification screen after the standard 35 - XWikiusername and password login.It improvesaccount protection withoutreplacingthe36 - familiarXWikiauthenticationflow.38 + The XWiki Two-Factor Authentication extension adds an additional verification screen after the standard 39 + username and password login. Users confirm their identity with a time-based one-time code generated by an 40 + authenticator app, or with a verification code delivered by email. 37 37 </p> 38 38 39 39 <p> 40 - Users can verify access with TOTP codes generated by an authenticator app, with one-time 41 - codes delivered by email, or with a combined setup requiring both methods. 44 + The extension is designed for organizations that want to improve account security while keeping authentication 45 + close to the standard XWiki login experience. It also supports remembering trusted clients beyond the current 46 + session, so users are not forced to enter a second factor again on every login from the same trusted browser. 42 42 </p> 43 43 44 44 <p> 45 - Trustedbrowsers or devices can berememberedfor aconfiguredperiod, reducingrepeated46 - verificationprompts onknown clients while stillrequiringverificationfromnewor untrustedones.50 + It can be useful for internal knowledge bases, intranets, documentation platforms, SOP systems, or other 51 + XWiki environments where access to content and administration should be better protected. 47 47 </p> 48 48 </article> 49 49 ... ... @@ -51,11 +51,13 @@ 51 51 <h3 id="quick-facts-title">Quick facts</h3> 52 52 <ul> 53 53 <li>Works with the standard XWiki login flow</li> 54 - <li>Supports authenticator app codes using TOTP</li> 55 - <li>Supports email-delivered one-time verification codes</li> 56 - <li>Can require app code and email code together</li> 57 - <li>Can remember trusted browsers or devices</li> 58 - <li>Includes administration and user setup controls</li> 59 + <li>Supports authenticator app verification codes</li> 60 + <li>Supports email-delivered verification codes</li> 61 + <li>Can remember trusted clients beyond the current session</li> 62 + <li>Configuration available from wiki administration</li> 63 + <li>User setup available during login or from the user profile</li> 64 + <li>Administrators can enable, disable or reset MFA for users</li> 65 + <li>Can be used on the main wiki and subwikis</li> 59 59 </ul> 60 60 </aside> 61 61 </div> ... ... @@ -65,88 +65,138 @@ 65 65 <section aria-labelledby="features-title"> 66 66 <div class="container"> 67 67 <h2 id="features-title">Main capabilities</h2> 68 - 69 69 <p class="section-intro"> 70 - 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. 71 71 </p> 72 72 73 73 <div class="product-feature-grid"> 74 74 <article class="product-feature"> 75 - <div class="card-heading"> 76 - <div class="feature-icon"> 77 - <i class="fa fa-key" aria-hidden="true"></i> 78 - </div> 79 - <h3>Second verification step</h3> 82 + <div class="feature-icon"> 83 + <i class="fa fa-key" aria-hidden="true"></i> 80 80 </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> 81 81 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> 82 82 <p> 83 - After username and password verification, users complete an additional step before accessing XWiki. 84 - The flow can require one verification method or both app and email codes. 98 + Users can verify access with codes generated by authenticator applications, such as mobile TOTP apps. 85 85 </p> 86 86 </article> 87 87 88 88 <article class="product-feature"> 89 - <div class="card-heading"> 90 - <div class="feature-icon"> 91 - <i class="fa fa-mobile" aria-hidden="true"></i> 92 - </div> 93 - <h3>Authenticator app codes</h3> 103 + <div class="feature-icon"> 104 + <i class="fa fa-envelope-o" aria-hidden="true"></i> 94 94 </div> 106 + <h3>Email verification codes</h3> 107 + <p> 108 + Users can also receive a verification code by email, useful when an authenticator app is not available. 109 + </p> 110 + </article> 95 95 112 + <article class="product-feature"> 113 + <div class="feature-icon"> 114 + <i class="fa fa-qrcode" aria-hidden="true"></i> 115 + </div> 116 + <h3>User setup screen</h3> 96 96 <p> 97 - Users can verif y access withTOTPcodes generatedbyauthenticatorapplicationson mobileor desktopdevices.118 + Users can configure their verification code setup during login or from their XWiki profile when needed. 98 98 </p> 99 99 </article> 100 100 101 101 <article class="product-feature"> 102 - <div class="card-heading"> 103 - <div class="feature-icon"> 104 - <i class="fa fa-envelope-o" aria-hidden="true"></i> 105 - </div> 106 - <h3>Email verification codes</h3> 123 + <div class="feature-icon"> 124 + <i class="fa fa-clock-o" aria-hidden="true"></i> 107 107 </div> 126 + <h3>Remember trusted clients</h3> 127 + <p> 128 + Trusted browsers can be remembered beyond the current session, reducing repeated MFA prompts while keeping 129 + the second factor active for new or untrusted clients. 130 + </p> 131 + </article> 108 108 133 + <article class="product-feature"> 134 + <div class="feature-icon"> 135 + <i class="fa fa-sliders" aria-hidden="true"></i> 136 + </div> 137 + <h3>Administration controls</h3> 109 109 <p> 110 - Users canreceive one-timeverification codesbyemail whenanauthenticatorappisnot availableor preferred.139 + Administrators can enable the feature globally, manage user-level activation, and reset a user setup when required. 111 111 </p> 112 112 </article> 142 + 143 + <article class="product-feature"> 144 + <div class="feature-icon"> 145 + <i class="fa fa-user" aria-hidden="true"></i> 146 + </div> 147 + <h3>Profile integration</h3> 148 + <p> 149 + The extension adds user profile controls so the second-factor setup can be reviewed or reset from XWiki. 150 + </p> 151 + </article> 152 + 153 + <article class="product-feature"> 154 + <div class="feature-icon"> 155 + <i class="fa fa-random" aria-hidden="true"></i> 156 + </div> 157 + <h3>Fallback behavior</h3> 158 + <p> 159 + The extension can fall back to standard XWiki authentication when the feature is not enabled or not configured. 160 + </p> 161 + </article> 162 + 163 + <article class="product-feature"> 164 + <div class="feature-icon"> 165 + <i class="fa fa-sitemap" aria-hidden="true"></i> 166 + </div> 167 + <h3>Main wiki and subwikis</h3> 168 + <p> 169 + The extension is designed to support XWiki environments using the main wiki and subwikis. 170 + </p> 171 + </article> 113 113 </div> 114 114 </div> 115 115 </section> 116 116 117 -<section class="product-section-muted"aria-labelledby="security-title">176 +<section aria-labelledby="use-cases-title"> 118 118 <div class="container"> 119 119 <div class="product-layout"> 120 120 <article class="product-summary-card"> 121 - <h2 id="sec urity-title">Usefulfor XWikisecurity and NIS 2 readiness</h2>180 + <h2 id="use-cases-title">When this extension is useful</h2> 122 122 123 123 <p> 124 - Many organizations need multi-factor authentication for enterprise software, including internal 125 - knowledge bases, intranets, documentation platforms and systems containing operational procedures 126 - or sensitive business information. 183 + Two-factor authentication is especially relevant when XWiki contains internal documentation, procedures, 184 + customer information, project knowledge, administrative pages, or business-critical content. 127 127 </p> 128 128 129 129 <p> 130 - For organizationsusingXWiki,addingtwo-factorauthenticationdirectlytothe standardloginflow131 - canhelp closeapractical access-control gap. Itcanbeusefulfor administratoraccounts,remoteusers,132 - pr ivateknowledge basesandbroadersecurity readinessinitiativessuchas NIS 2preparation.188 + It can also support organizations that need MFA as part of their cybersecurity controls, including companies 189 + working toward NIS 2 readiness. NIS 2 focuses on stronger cybersecurity risk management across essential and 190 + important entities in the EU, and MFA is often expected as part of enterprise access protection programs. 133 133 </p> 134 134 135 135 <p> 136 - Thisextensionis nota completecompliance solutiononitsown,butit can provideanimportant137 - technical controlforprotectingaccesstoXWiki.194 + It is also useful when many users access the wiki remotely, when administrator accounts need stronger protection, 195 + or when the organization wants to reduce the risk of compromised passwords. 138 138 </p> 139 139 </article> 140 140 141 - <aside class="product-info-card" aria-labelledby=" security-controls-title">142 - <h3 id=" security-controls-title">Usefulfor</h3>199 + <aside class="product-info-card" aria-labelledby="good-fit-title"> 200 + <h3 id="good-fit-title">Good fit for</h3> 143 143 <ul> 144 - <li>XWiki 2FA rollout</li> 145 - <li>XWiki MFA adoption</li> 146 - <li>Administrator account protection</li> 147 - <li>Remote user access protection</li> 148 - <li>Private knowledge base security</li> 149 - <li>NIS 2 readiness initiatives</li> 202 + <li>Private XWiki knowledge bases</li> 203 + <li>Company intranets</li> 204 + <li>SOP and controlled-document platforms</li> 205 + <li>Documentation portals with sensitive content</li> 206 + <li>Wikis with several administrators or remote users</li> 150 150 </ul> 151 151 </aside> 152 152 </div> ... ... @@ -153,13 +153,66 @@ 153 153 </div> 154 154 </section> 155 155 213 +<section class="product-section-muted" aria-labelledby="compliance-title"> 214 + <div class="container"> 215 + <div class="product-layout"> 216 + <article class="product-summary-card"> 217 + <h2 id="compliance-title">Useful for MFA adoption and NIS 2 readiness</h2> 218 + 219 + <p> 220 + Many organizations now need multi-factor authentication for enterprise software, especially when the 221 + platform contains internal documentation, procedures, operational knowledge or sensitive business data. 222 + </p> 223 + 224 + <p> 225 + For organizations using XWiki as a knowledge platform, having MFA embedded in the standard XWiki login 226 + experience helps close a practical security gap without requiring a full replacement of the authentication flow. 227 + </p> 228 + 229 + <p> 230 + This can be relevant for companies preparing for NIS 2 requirements, where MFA is part of a broader 231 + cybersecurity risk management and access protection strategy. 232 + </p> 233 + </article> 234 + 235 + <aside class="product-info-card" aria-labelledby="mfa-readiness-title"> 236 + <h3 id="mfa-readiness-title">Security controls supported</h3> 237 + <ul> 238 + <li>Second-factor verification after password login</li> 239 + <li>Authenticator app or email-based verification codes</li> 240 + <li>Reduced repeated prompts for trusted clients</li> 241 + <li>Administration controls for user-level MFA management</li> 242 + <li>Better protection for administrator and remote-access accounts</li> 243 + </ul> 244 + </aside> 245 + </div> 246 + </div> 247 +</section> 248 + 249 +#* 250 +<section aria-labelledby="gallery-title"> 251 + <div class="container"> 252 + <div class="product-gallery-panel"> 253 + <h2 id="gallery-title">Screenshots</h2> 254 + <p class="gallery-note"> 255 + Use this area to show the login verification screen, first-time setup, user profile controls, 256 + and administration configuration. 257 + </p> 258 + 259 + <div class="product-gallery-placeholder"> 260 + Replace this placeholder with the XWiki gallery macro and 3-5 screenshots from the application. 261 + </div> 262 + </div> 263 + </div> 264 +</section> 265 +*# 156 156 <section class="cta-section" aria-labelledby="cta-title"> 157 157 <div class="container"> 158 158 <div class="cta-panel"> 159 159 <h2 id="cta-title">Interested in using this extension?</h2> 160 160 <p> 161 - Send a short message with your XWiki version, authentication setup, and whether you ne ed162 - authenticator appcodes, emailverificationcodes, combined verification,or trusted-device remembering.271 + Send a short message with your XWiki version, authentication setup, and whether you use a single wiki 272 + or a main wiki with subwikis. 163 163 </p> 164 164 <a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Contact Agnease</a> 165 165 </div>
- 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