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, 1 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - xwiki-two-factor-authentication1 +XWiki Two-Factor Authentication - Content
-
... ... @@ -3,24 +3,20 @@ 3 3 #set ($discard = $xwiki.ssx.use('products.WebHome')) 4 4 {{html clean="false"}} 5 5 6 -<section class="hero hero-centered product-hero" aria-labelledby="product-title">6 +<section class="hero hero-centered" aria-labelledby="hero-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 securityextension10 + 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. 16 + Protect XWiki logins with a second verification step using authenticator app codes, 17 + email verification codes, or both. 17 17 </p> 18 18 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 - 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,23 +32,22 @@ 32 32 <div class="container"> 33 33 <div class="product-layout"> 34 34 <article class="product-summary-card"> 35 - <h2 id="overview-title"> Strongerlogin protectionforXWiki</h2>31 + <h2 id="overview-title">Two-factor authentication built into XWiki</h2> 36 36 37 37 <p> 38 - TheXWiki Two-Factor Authenticationextensionadds an additional verification screen after the standard39 - username and password login. Users confirmtheir identitywitha time-basedone-timecode generated byan40 - a uthenticatorapp, or withaverificationcode delivered by email.34 + XWiki Two-Factor Authentication adds an additional verification screen after the standard 35 + XWiki username and password login. It improves account protection without replacing the 36 + familiar XWiki authentication flow. 41 41 </p> 42 42 43 43 <p> 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. 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. 47 47 </p> 48 48 49 49 <p> 50 - It can beusefulforinternalknowledgebases,intranets,documentation platforms, SOP systems, or other51 - XWikienvironments whereaccesstocontentand administrationshouldbebetterprotected.45 + Trusted browsers or devices can be remembered for a configured period, reducing repeated 46 + verification prompts on known clients while still requiring verification from new or untrusted ones. 52 52 </p> 53 53 </article> 54 54 ... ... @@ -56,13 +56,11 @@ 56 56 <h3 id="quick-facts-title">Quick facts</h3> 57 57 <ul> 58 58 <li>Works with the standard XWiki login flow</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> 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> 66 66 </ul> 67 67 </aside> 68 68 </div> ... ... @@ -72,138 +72,88 @@ 72 72 <section aria-labelledby="features-title"> 73 73 <div class="container"> 74 74 <h2 id="features-title">Main capabilities</h2> 68 + 75 75 <p class="section-intro"> 76 - The extension focuses on adding a practical second authentication step while keeping the standard XWiki login 77 - process and administration experience understandable. 70 + A focused set of MFA/2FA features for stronger XWiki account protection without changing the standard login experience. 78 78 </p> 79 79 80 80 <div class="product-feature-grid"> 81 81 <article class="product-feature"> 82 - <div class="feature-icon"> 83 - <i class="fa fa-key" aria-hidden="true"></i> 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> 84 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> 91 91 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 97 <p> 98 - Users can verify access with codes generated by authenticator applications, such as mobile TOTP apps. 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. 99 99 </p> 100 100 </article> 101 101 102 102 <article class="product-feature"> 103 - <div class="feature-icon"> 104 - <i class="fa fa-envelope-o" aria-hidden="true"></i> 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> 105 105 </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> 111 111 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> 117 117 <p> 118 - Users can configure theirverificationcodesetupduringloginorfromtheirXWikiprofilewhenneeded.97 + Users can verify access with TOTP codes generated by authenticator applications on mobile or desktop devices. 119 119 </p> 120 120 </article> 121 121 122 122 <article class="product-feature"> 123 - <div class="feature-icon"> 124 - <i class="fa fa-clock-o" aria-hidden="true"></i> 102 + <div class="feature-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> 125 125 </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> 132 132 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> 138 138 <p> 139 - Administrators can enable thefeatureglobally,manageuser-level activation,andreset ausersetupwhenrequired.110 + Users can receive one-time verification codes by email when an authenticator app is not available or preferred. 140 140 </p> 141 141 </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> 172 172 </div> 173 173 </div> 174 174 </section> 175 175 176 -<section aria-labelledby=" use-cases-title">117 +<section class="product-section-muted" aria-labelledby="security-title"> 177 177 <div class="container"> 178 178 <div class="product-layout"> 179 179 <article class="product-summary-card"> 180 - <h2 id=" use-cases-title">Whenthisextensionisuseful</h2>121 + <h2 id="security-title">Useful for XWiki security and NIS 2 readiness</h2> 181 181 182 182 <p> 183 - Two-factor authentication is especially relevant when XWiki contains internal documentation, procedures, 184 - customer information, project knowledge, administrative pages, or business-critical content. 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. 185 185 </p> 186 186 187 187 <p> 188 - It can alsosupportorganizationsthatneedMFAaspartof theircybersecuritycontrols,includingcompanies189 - workingtowardNIS 2readiness.NIS 2 focusesonstrongercybersecurityriskmanagement acrossessentialand190 - importantentitiesin theEU,andMFA isoftenexpected as partofenterpriseaccess protectionprograms.130 + For organizations using XWiki, adding two-factor authentication directly to the standard login flow 131 + can help close a practical access-control gap. It can be useful for administrator accounts, remote users, 132 + private knowledge bases and broader security readiness initiatives such as NIS 2 preparation. 191 191 </p> 192 192 193 193 <p> 194 - Itisalsousefulwhenmanyusers accessthewiki remotely, when administratoraccounts needstrongerprotection,195 - or whentheorganizationwantsto reducethe riskofcompromised passwords.136 + This extension is not a complete compliance solution on its own, but it can provide an important 137 + technical control for protecting access to XWiki. 196 196 </p> 197 197 </article> 198 198 199 - <aside class="product-info-card" aria-labelledby=" good-fit-title">200 - <h3 id=" good-fit-title">Goodfitfor</h3>141 + <aside class="product-info-card" aria-labelledby="security-controls-title"> 142 + <h3 id="security-controls-title">Useful for</h3> 201 201 <ul> 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> 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> 207 207 </ul> 208 208 </aside> 209 209 </div> ... ... @@ -210,66 +210,13 @@ 210 210 </div> 211 211 </section> 212 212 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 -*# 266 266 <section class="cta-section" aria-labelledby="cta-title"> 267 267 <div class="container"> 268 268 <div class="cta-panel"> 269 269 <h2 id="cta-title">Interested in using this extension?</h2> 270 270 <p> 271 - Send a short message with your XWiki version, authentication setup, and whether you use a singlewiki272 - or a mai nwikiwithsubwikis.161 + Send a short message with your XWiki version, authentication setup, and whether you need 162 + authenticator app codes, email verification codes, combined verification, or trusted-device remembering. 273 273 </p> 274 274 <a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Contact Agnease</a> 275 275 </div>
- 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