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="product-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 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 + </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,24 @@ 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 a n additional verificationscreenafter the standard35 - XWiki username and password login. It improves account protection without replacing the36 - 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. 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 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. 42 42 </p> 43 43 44 44 <p> 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. 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. 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> 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> 66 + <li>Can be used on the main wiki and subwikis</li> 59 59 </ul> 60 60 </aside> 61 61 </div> ... ... @@ -65,9 +65,9 @@ 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. 77 + The extension focuses on adding a practical second authentication step while keeping the standard XWiki login 78 + process and administration experience understandable. 71 71 </p> 72 72 73 73 <div class="product-feature-grid"> ... ... @@ -75,10 +75,10 @@ 75 75 <div class="feature-icon"> 76 76 <i class="fa fa-key" aria-hidden="true"></i> 77 77 </div> 78 - <h3>Second verification step</h3>86 + <h3>Second login step</h3> 79 79 <p> 80 - After username and password verifi cation, userscomplete an additionalstep before accessingXWiki.81 - Theflow canrequireoneverificationmethod or both app andemailcodes.88 + After the username and password are verified, users are asked to enter an additional verification code 89 + before accessing the wiki. 82 82 </p> 83 83 </article> 84 84 ... ... @@ -88,7 +88,7 @@ 88 88 </div> 89 89 <h3>Authenticator app codes</h3> 90 90 <p> 91 - Users can verify access with TOTPcodes generated by authenticator applicationsonmobileordesktopdevices.99 + Users can verify access with codes generated by authenticator applications, such as mobile TOTP apps. 92 92 </p> 93 93 </article> 94 94 ... ... @@ -98,46 +98,105 @@ 98 98 </div> 99 99 <h3>Email verification codes</h3> 100 100 <p> 101 - Users can receive one-timeverification codesby email when an authenticator app is not availableor preferred.109 + Users can also receive a verification code by email, useful when an authenticator app is not available. 102 102 </p> 103 103 </article> 112 + 113 + <article class="product-feature"> 114 + <div class="feature-icon"> 115 + <i class="fa fa-qrcode" aria-hidden="true"></i> 116 + </div> 117 + <h3>User setup screen</h3> 118 + <p> 119 + Users can configure their verification code setup during login or from their XWiki profile when needed. 120 + </p> 121 + </article> 122 + 123 + <article class="product-feature"> 124 + <div class="feature-icon"> 125 + <i class="fa fa-clock-o" aria-hidden="true"></i> 126 + </div> 127 + <h3>Remember trusted clients</h3> 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. 131 + </p> 132 + </article> 133 + 134 + <article class="product-feature"> 135 + <div class="feature-icon"> 136 + <i class="fa fa-sliders" aria-hidden="true"></i> 137 + </div> 138 + <h3>Administration controls</h3> 139 + <p> 140 + Administrators can enable the feature globally, manage user-level activation, and reset a user setup when required. 141 + </p> 142 + </article> 143 + 144 + <article class="product-feature"> 145 + <div class="feature-icon"> 146 + <i class="fa fa-user" aria-hidden="true"></i> 147 + </div> 148 + <h3>Profile integration</h3> 149 + <p> 150 + The extension adds user profile controls so the second-factor setup can be reviewed or reset from XWiki. 151 + </p> 152 + </article> 153 + 154 + <article class="product-feature"> 155 + <div class="feature-icon"> 156 + <i class="fa fa-random" aria-hidden="true"></i> 157 + </div> 158 + <h3>Fallback behavior</h3> 159 + <p> 160 + The extension can fall back to standard XWiki authentication when the feature is not enabled or not configured. 161 + </p> 162 + </article> 163 + 164 + <article class="product-feature"> 165 + <div class="feature-icon"> 166 + <i class="fa fa-sitemap" aria-hidden="true"></i> 167 + </div> 168 + <h3>Main wiki and subwikis</h3> 169 + <p> 170 + The extension is designed to support XWiki environments using the main wiki and subwikis. 171 + </p> 172 + </article> 104 104 </div> 105 105 </div> 106 106 </section> 107 107 108 -<section class="product-section-muted"aria-labelledby="security-title">177 +<section aria-labelledby="use-cases-title"> 109 109 <div class="container"> 110 110 <div class="product-layout"> 111 111 <article class="product-summary-card"> 112 - <h2 id="sec urity-title">Usefulfor XWikisecurity and NIS 2 readiness</h2>181 + <h2 id="use-cases-title">When this extension is useful</h2> 113 113 114 114 <p> 115 - Many organizations need multi-factor authentication for enterprise software, including internal 116 - knowledge bases, intranets, documentation platforms and systems containing operational procedures 117 - or sensitive business information. 184 + Two-factor authentication is especially relevant when XWiki contains internal documentation, procedures, 185 + customer information, project knowledge, administrative pages, or business-critical content. 118 118 </p> 119 119 120 120 <p> 121 - For organizationsusingXWiki,addingtwo-factorauthenticationdirectlytothe standardloginflow122 - canhelp closeapractical access-control gap. Itcanbeusefulfor administratoraccounts,remoteusers,123 - pr ivateknowledge basesandbroadersecurity readinessinitiativessuchas NIS 2preparation.189 + It can also support organizations that need MFA as part of their cybersecurity controls, including companies 190 + working toward NIS 2 readiness. NIS 2 focuses on stronger cybersecurity risk management across essential and 191 + important entities in the EU, and MFA is often expected as part of enterprise access protection programs. 124 124 </p> 125 125 126 126 <p> 127 - Thisextensionis nota completecompliance solutiononitsown,butit can provideanimportant128 - technical controlforprotectingaccesstoXWiki.195 + It is also useful when many users access the wiki remotely, when administrator accounts need stronger protection, 196 + or when the organization wants to reduce the risk of compromised passwords. 129 129 </p> 130 130 </article> 131 131 132 - <aside class="product-info-card" aria-labelledby=" security-controls-title">133 - <h3 id=" security-controls-title">Usefulfor</h3>200 + <aside class="product-info-card" aria-labelledby="good-fit-title"> 201 + <h3 id="good-fit-title">Good fit for</h3> 134 134 <ul> 135 - <li>XWiki 2FA rollout</li> 136 - <li>XWiki MFA adoption</li> 137 - <li>Administrator account protection</li> 138 - <li>Remote user access protection</li> 139 - <li>Private knowledge base security</li> 140 - <li>NIS 2 readiness initiatives</li> 203 + <li>Private XWiki knowledge bases</li> 204 + <li>Company intranets</li> 205 + <li>SOP and controlled-document platforms</li> 206 + <li>Documentation portals with sensitive content</li> 207 + <li>Wikis with several administrators or remote users</li> 141 141 </ul> 142 142 </aside> 143 143 </div> ... ... @@ -144,13 +144,66 @@ 144 144 </div> 145 145 </section> 146 146 214 +<section class="product-section-muted" aria-labelledby="compliance-title"> 215 + <div class="container"> 216 + <div class="product-layout"> 217 + <article class="product-summary-card"> 218 + <h2 id="compliance-title">Useful for MFA adoption and NIS 2 readiness</h2> 219 + 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. 223 + </p> 224 + 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. 228 + </p> 229 + 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. 233 + </p> 234 + </article> 235 + 236 + <aside class="product-info-card" aria-labelledby="mfa-readiness-title"> 237 + <h3 id="mfa-readiness-title">Security controls supported</h3> 238 + <ul> 239 + <li>Second-factor verification after password login</li> 240 + <li>Authenticator app or email-based verification codes</li> 241 + <li>Reduced repeated prompts for trusted clients</li> 242 + <li>Administration controls for user-level MFA management</li> 243 + <li>Better protection for administrator and remote-access accounts</li> 244 + </ul> 245 + </aside> 246 + </div> 247 + </div> 248 +</section> 249 + 250 +#* 251 +<section aria-labelledby="gallery-title"> 252 + <div class="container"> 253 + <div class="product-gallery-panel"> 254 + <h2 id="gallery-title">Screenshots</h2> 255 + <p class="gallery-note"> 256 + Use this area to show the login verification screen, first-time setup, user profile controls, 257 + and administration configuration. 258 + </p> 259 + 260 + <div class="product-gallery-placeholder"> 261 + Replace this placeholder with the XWiki gallery macro and 3-5 screenshots from the application. 262 + </div> 263 + </div> 264 + </div> 265 +</section> 266 +*# 147 147 <section class="cta-section" aria-labelledby="cta-title"> 148 148 <div class="container"> 149 149 <div class="cta-panel"> 150 150 <h2 id="cta-title">Interested in using this extension?</h2> 151 151 <p> 152 - Send a short message with your XWiki version, authentication setup, and whether you ne ed153 - authenticator appcodes, emailverificationcodes, combined verification,or trusted-device remembering.272 + Send a short message with your XWiki version, authentication setup, and whether you use a single wiki 273 + or a main wiki with subwikis. 154 154 </p> 155 155 <a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Contact Agnease</a> 156 156 </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