Changes for page XWiki Two-Factor Authentication
Last modified by Agnease on 2026/05/23 18:56
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -57,12 +57,11 @@ 57 57 <h3 id="quick-facts-title">Quick facts</h3> 58 58 <ul> 59 59 <li>Works with the standard XWiki login flow</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> 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> 66 66 <li>Can be used on the main wiki and subwikis</li> 67 67 </ul> 68 68 </aside> ... ... @@ -96,7 +96,7 @@ 96 96 </div> 97 97 <h3>Authenticator app codes</h3> 98 98 <p> 99 - Users can verify access with codes generated by authenticator applications ,suchasmobileTOTPapps.98 + Users can verify access with TOTP codes generated by authenticator applications on a mobile device or desktop. 100 100 </p> 101 101 </article> 102 102 ... ... @@ -106,12 +106,22 @@ 106 106 </div> 107 107 <h3>Email verification codes</h3> 108 108 <p> 109 - Users can alsoreceiveaverification code by email, useful when an authenticator app is not available.108 + Users can receive one-time verification codes by email, useful when an authenticator app is not available or preferred. 110 110 </p> 111 111 </article> 112 112 113 113 <article class="product-feature"> 114 114 <div class="feature-icon"> 114 + <i class="fa fa-plus-circle" aria-hidden="true"></i> 115 + </div> 116 + <h3>Combined verification</h3> 117 + <p> 118 + The extension can also require both an authenticator app code and an email code for stricter multi-factor verification. 119 + </p> 120 + </article> 121 + 122 + <article class="product-feature"> 123 + <div class="feature-icon"> 115 115 <i class="fa fa-qrcode" aria-hidden="true"></i> 116 116 </div> 117 117 <h3>User setup screen</h3> ... ... @@ -122,22 +122,21 @@ 122 122 123 123 <article class="product-feature"> 124 124 <div class="feature-icon"> 125 - <i class="fa fa- clock-o" aria-hidden="true"></i>134 + <i class="fa fa-laptop" aria-hidden="true"></i> 126 126 </div> 127 127 <h3>Remember trusted clients</h3> 128 128 <p> 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. 138 + Known browsers or devices can be remembered for a configured period, reducing repeated MFA prompts from trusted clients. 131 131 </p> 132 132 </article> 133 133 134 - <article class="product-feature">142 + article class="product-feature"> 135 135 <div class="feature-icon"> 136 136 <i class="fa fa-sliders" aria-hidden="true"></i> 137 137 </div> 138 138 <h3>Administration controls</h3> 139 139 <p> 140 - Administrators can enable thefeatureglobally, manage user-levelactivation, and resetauser setup when required.148 + Administrators can configure MFA behavior, manage user activation, and reset user setup when required. 141 141 </p> 142 142 </article> 143 143 ... ... @@ -218,18 +218,22 @@ 218 218 <h2 id="compliance-title">Useful for MFA adoption and NIS 2 readiness</h2> 219 219 220 220 <p> 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. 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. 223 223 </p> 224 224 225 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. 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. 228 228 </p> 229 229 230 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. 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. 233 233 </p> 234 234 </article> 235 235