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-FactorAuthentication| 2FA and MFA for XWiki1 +xwiki-two-factor-authentication - Content
-
... ... @@ -7,7 +7,7 @@ 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> ... ... @@ -17,8 +17,8 @@ 17 17 </p> 18 18 19 19 <p class="hero-support"> 20 - ProtectXWikiaccountswithauthenticatorapp codes,email verificationcodes,21 - or a combined setup requiring both. 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 22 </p> 23 23 24 24 <div class="hero-actions"> ... ... @@ -32,22 +32,24 @@ 32 32 <div class="container"> 33 33 <div class="product-layout"> 34 34 <article class="product-summary-card"> 35 - <h2 id="overview-title"> Two-factorauthenticationbuilt into XWiki</h2>35 + <h2 id="overview-title">Stronger login protection for XWiki</h2> 36 36 37 37 <p> 38 - XWiki Two-Factor Authentication adds a n additional verificationscreenafter the standard39 - XWiki username and password login. It improves account protection without replacing the40 - familiarXWiki authentication flow.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. 41 41 </p> 42 42 43 43 <p> 44 - Users can verify access with TOTP codes generated by an authenticator app, with one-time 45 - codes delivered by email, or with a combined setup requiring both methods. 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. 46 46 </p> 47 47 48 48 <p> 49 - Trusted browsers or devices can be remembered for a configured period, reducing repeated 50 - verification prompts on known clients while still requiring verification from new or untrusted ones. 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. 51 51 </p> 52 52 </article> 53 53 ... ... @@ -57,9 +57,10 @@ 57 57 <li>Works with the standard XWiki login flow</li> 58 58 <li>Supports authenticator app codes using TOTP</li> 59 59 <li>Supports email-delivered one-time verification codes</li> 60 - <li>Can require app code and email code together</li> 61 - <li>Can remember trusted browsers or devices</li> 62 - <li>Includes administration and user setup controls</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> 63 63 </ul> 64 64 </aside> 65 65 </div> ... ... @@ -69,10 +69,9 @@ 69 69 <section aria-labelledby="features-title"> 70 70 <div class="container"> 71 71 <h2 id="features-title">Main capabilities</h2> 72 - 73 73 <p class="section-intro"> 74 - AfocusedsetofMFA/2FAfeaturesfor organizationsthatwant stronger XWikiaccount protection75 - withoutchanging thestandardlogin experience.76 + The extension focuses on adding a practical second authentication step while keeping the standard XWiki login 77 + process and administration experience understandable. 76 76 </p> 77 77 78 78 <div class="product-feature-grid"> ... ... @@ -82,7 +82,8 @@ 82 82 </div> 83 83 <h3>Second login step</h3> 84 84 <p> 85 - After username and password verification, users must complete an additional verification step before accessing XWiki. 87 + After the username and password are verified, users are asked to enter an additional verification code 88 + before accessing the wiki. 86 86 </p> 87 87 </article> 88 88 ... ... @@ -92,7 +92,7 @@ 92 92 </div> 93 93 <h3>Authenticator app codes</h3> 94 94 <p> 95 - Users can verify access with TOTP codes generated by authenticator applications on mobile or desktop devices.98 + Users can verify access with TOTP codes generated by authenticator applications on a mobile device or desktop. 96 96 </p> 97 97 </article> 98 98 ... ... @@ -102,7 +102,7 @@ 102 102 </div> 103 103 <h3>Email verification codes</h3> 104 104 <p> 105 - Users can receive one-time verification codes by email when an authenticator app is not available or preferred. 108 + Users can receive one-time verification codes by email, useful when an authenticator app is not available or preferred. 106 106 </p> 107 107 </article> 108 108 ... ... @@ -112,46 +112,144 @@ 112 112 </div> 113 113 <h3>Combined verification</h3> 114 114 <p> 115 - The loginflowcan require both an authenticator app code and an email codewhenstricter verificationis needed.118 + The extension can also require both an authenticator app code and an email code for stricter multi-factor verification. 116 116 </p> 117 117 </article> 121 + 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> 127 + <p> 128 + Users can configure their verification code setup during login or from their XWiki profile when needed. 129 + </p> 130 + </article> 131 + 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> 141 + 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> 151 + 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> 161 + 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> 171 + 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> 118 118 </div> 119 119 </div> 120 120 </section> 121 121 122 -<section class="product-section-muted"aria-labelledby="security-title">185 +<section aria-labelledby="use-cases-title"> 123 123 <div class="container"> 124 124 <div class="product-layout"> 125 125 <article class="product-summary-card"> 126 - <h2 id="sec urity-title">Usefulfor XWikisecurity and NIS 2 readiness</h2>189 + <h2 id="use-cases-title">When this extension is useful</h2> 127 127 128 128 <p> 129 - Many organizations need multi-factor authentication for enterprise software, including internal 130 - knowledge bases, intranets, documentation platforms and systems containing operational procedures 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> 195 + 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> 201 + 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> 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> 218 + </div> 219 + </div> 220 +</section> 221 + 222 +<section class="product-section-muted" aria-labelledby="compliance-title"> 223 + <div class="container"> 224 + <div class="product-layout"> 225 + <article class="product-summary-card"> 226 + <h2 id="compliance-title">Useful for MFA adoption and NIS 2 readiness</h2> 227 + 228 + <p> 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 131 131 or sensitive business information. 132 132 </p> 133 133 134 134 <p> 135 - For organizations using XWiki, adding two-factorauthenticationdirectly to the standard login flow136 - can helpclose a practical access-control gap.It canbe usefulforadministrator accounts,remoteusers,137 - privateknowledgebasesandbroadersecurity readiness initiativessuchasNIS 2 preparation.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. 138 138 </p> 139 139 140 140 <p> 141 - This extension is not a complete compliance solution on its own, but it can provide an important 142 - technical control for protecting access to XWiki. 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. 143 143 </p> 144 144 </article> 145 145 146 - <aside class="product-info-card" aria-labelledby=" security-controls-title">147 - <h3 id="security -controls-title">Useful for</h3>248 + <aside class="product-info-card" aria-labelledby="mfa-readiness-title"> 249 + <h3 id="mfa-readiness-title">Security controls supported</h3> 148 148 <ul> 149 - <li>XWiki 2FA rollout</li> 150 - <li>XWiki MFA adoption</li> 151 - <li>Administrator account protection</li> 152 - <li>Remote user access protection</li> 153 - <li>Private knowledge base security</li> 154 - <li>NIS 2 readiness initiatives</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> 155 155 </ul> 156 156 </aside> 157 157 </div> ... ... @@ -158,13 +158,30 @@ 158 158 </div> 159 159 </section> 160 160 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 +*# 161 161 <section class="cta-section" aria-labelledby="cta-title"> 162 162 <div class="container"> 163 163 <div class="cta-panel"> 164 164 <h2 id="cta-title">Interested in using this extension?</h2> 165 165 <p> 166 - Send a short message with your XWiki version, authentication setup, and whether you ne ed167 - authenticator appcodes, emailverificationcodes, combined verification,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. 168 168 </p> 169 169 <a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Contact Agnease</a> 170 170 </div>
- Agnease.Code.SEODetailsClass[0]
-
- metaDescription
-
... ... @@ -1,1 +1,0 @@ 1 -Add two-factor authentication to the standard XWiki login flow with authenticator app codes, email verification codes, combined verification, and trusted-device remembering. - metaTitle
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki Two-Factor Authentication | 2FA and MFA for XWiki