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)
-
Objects (0 modified, 0 added, 1 removed)
Details
- Page properties
-
- 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,23 @@ 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 an additional verification screen after the standard 39 - XWikiusername and password login.It improvesaccount protection withoutreplacingthe40 - 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. 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 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. 46 46 </p> 47 47 48 48 <p> 49 - Trustedbrowsers or devices can berememberedfor aconfiguredperiod, reducingrepeated50 - 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. 51 51 </p> 52 52 </article> 53 53 ... ... @@ -55,11 +55,13 @@ 55 55 <h3 id="quick-facts-title">Quick facts</h3> 56 56 <ul> 57 57 <li>Works with the standard XWiki login flow</li> 58 - <li>Supports authenticator app codes using TOTP</li> 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> 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> 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 TOTPcodes generated by authenticator applicationsonmobileordesktopdevices.98 + Users can verify access with codes generated by authenticator applications, such as mobile TOTP apps. 96 96 </p> 97 97 </article> 98 98 ... ... @@ -102,56 +102,105 @@ 102 102 </div> 103 103 <h3>Email verification codes</h3> 104 104 <p> 105 - Users can receive one-timeverification codesby email when an authenticator app is not availableor preferred.108 + Users can also receive a verification code by email, useful when an authenticator app is not available. 106 106 </p> 107 107 </article> 108 108 109 109 <article class="product-feature"> 110 110 <div class="feature-icon"> 111 - <i class="fa fa- plus-circle" aria-hidden="true"></i>114 + <i class="fa fa-qrcode" aria-hidden="true"></i> 112 112 </div> 113 - <h3> Combinedverification</h3>116 + <h3>User setup screen</h3> 114 114 <p> 115 - Thelogin flowcanrequirebothan authenticatorappcodeandanemailcode whenstricterverificationisneeded.118 + Users can configure their verification code setup during login or from their XWiki profile when needed. 116 116 </p> 117 117 </article> 121 + 122 + <article class="product-feature"> 123 + <div class="feature-icon"> 124 + <i class="fa fa-clock-o" aria-hidden="true"></i> 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 + 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 + <p> 139 + Administrators can enable the feature globally, manage user-level activation, and reset a user setup when required. 140 + </p> 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> 118 118 </div> 119 119 </div> 120 120 </section> 121 121 122 -<section class="product-section-muted"aria-labelledby="security-title">176 +<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>180 + <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 131 - 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. 132 132 </p> 133 133 134 134 <p> 135 - For organizationsusingXWiki,addingtwo-factorauthenticationdirectlytothe standardloginflow136 - canhelp closeapractical access-control gap. Itcanbeusefulfor administratoraccounts,remoteusers,137 - 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. 138 138 </p> 139 139 140 140 <p> 141 - Thisextensionis nota completecompliance solutiononitsown,butit can provideanimportant142 - 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. 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">Usefulfor</h3>199 + <aside class="product-info-card" aria-labelledby="good-fit-title"> 200 + <h3 id="good-fit-title">Good fit for</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> 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> 155 155 </ul> 156 156 </aside> 157 157 </div> ... ... @@ -158,13 +158,66 @@ 158 158 </div> 159 159 </section> 160 160 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 +*# 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.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. 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 -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