Skip to Content
Last modified by Agnease on 2026/05/23 18:56
From version 1.13
edited by Agnease
on 2026/05/22 03:37
Change comment: There is no comment for this version
To version 4.1
edited by Agnease
on 2026/05/22 06:14
Change comment: There is no comment for this version

Summary

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 security extension
10 + XWiki 2FA and MFA
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 - 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.
20 + Protect XWiki accounts with authenticator app codes, email verification codes,
21 + or a combined setup requiring both.
22 22   </p>
23 23  
24 24   <div class="hero-actions">
... ... @@ -32,24 +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">Stronger login protection for XWiki</h2>
35 + <h2 id="overview-title">Two-factor authentication built into XWiki</h2>
36 36  
37 37   <p>
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.
38 + XWiki Two-Factor Authentication adds an additional verification screen after the standard
39 + XWiki username and password login. It improves account protection without replacing the
40 + familiar XWiki authentication flow.
41 41   </p>
42 42  
43 43   <p>
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.
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.
47 47   </p>
48 48  
49 49   <p>
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.
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.
53 53   </p>
54 54   </article>
55 55  
... ... @@ -57,13 +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>
66 - <li>Can be used on the main wiki and subwikis</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>
67 67   </ul>
68 68   </aside>
69 69   </div>
... ... @@ -73,9 +73,10 @@
73 73  <section aria-labelledby="features-title">
74 74   <div class="container">
75 75   <h2 id="features-title">Main capabilities</h2>
72 +
76 76   <p class="section-intro">
77 - The extension focuses on adding a practical second authentication step while keeping the standard XWiki login
78 - process and administration experience understandable.
74 + A focused set of MFA/2FA features for organizations that want stronger XWiki account protection
75 + without changing the standard login experience.
79 79   </p>
80 80  
81 81   <div class="product-feature-grid">
... ... @@ -85,8 +85,7 @@
85 85   </div>
86 86   <h3>Second login step</h3>
87 87   <p>
88 - After the username and password are verified, users are asked to enter an additional verification code
89 - before accessing the wiki.
85 + After username and password verification, users must complete an additional verification step before accessing XWiki.
90 90   </p>
91 91   </article>
92 92  
... ... @@ -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, such as mobile TOTP apps.
95 + Users can verify access with TOTP codes generated by authenticator applications on mobile or desktop devices.
100 100   </p>
101 101   </article>
102 102  
... ... @@ -106,105 +106,56 @@
106 106   </div>
107 107   <h3>Email verification codes</h3>
108 108   <p>
109 - Users can also receive a verification code by email, useful when an authenticator app is not available.
105 + Users can receive one-time verification codes by email 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">
115 - <i class="fa fa-qrcode" aria-hidden="true"></i>
111 + <i class="fa fa-plus-circle" aria-hidden="true"></i>
116 116   </div>
117 - <h3>User setup screen</h3>
113 + <h3>Combined verification</h3>
118 118   <p>
119 - Users can configure their verification code setup during login or from their XWiki profile when needed.
115 + The login flow can require both an authenticator app code and an email code when stricter verification is needed.
120 120   </p>
121 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>
173 173   </div>
174 174   </div>
175 175  </section>
176 176  
177 -<section aria-labelledby="use-cases-title">
122 +<section class="product-section-muted" aria-labelledby="security-title">
178 178   <div class="container">
179 179   <div class="product-layout">
180 180   <article class="product-summary-card">
181 - <h2 id="use-cases-title">When this extension is useful</h2>
126 + <h2 id="security-title">Useful for XWiki security and NIS 2 readiness</h2>
182 182  
183 183   <p>
184 - Two-factor authentication is especially relevant when XWiki contains internal documentation, procedures,
185 - customer information, project knowledge, administrative pages, or business-critical content.
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.
186 186   </p>
187 187  
188 188   <p>
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.
135 + For organizations using XWiki, adding two-factor authentication directly to the standard login flow
136 + can help close a practical access-control gap. It can be useful for administrator accounts, remote users,
137 + private knowledge bases and broader security readiness initiatives such as NIS 2 preparation.
192 192   </p>
193 193  
194 194   <p>
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.
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.
197 197   </p>
198 198   </article>
199 199  
200 - <aside class="product-info-card" aria-labelledby="good-fit-title">
201 - <h3 id="good-fit-title">Good fit for</h3>
146 + <aside class="product-info-card" aria-labelledby="security-controls-title">
147 + <h3 id="security-controls-title">Useful for</h3>
202 202   <ul>
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>
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>
208 208   </ul>
209 209   </aside>
210 210   </div>
... ... @@ -211,66 +211,13 @@
211 211   </div>
212 212  </section>
213 213  
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 -*#
267 267  <section class="cta-section" aria-labelledby="cta-title">
268 268   <div class="container">
269 269   <div class="cta-panel">
270 270   <h2 id="cta-title">Interested in using this extension?</h2>
271 271   <p>
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.
166 + Send a short message with your XWiki version, authentication setup, and whether you need
167 + authenticator app codes, email verification codes, combined verification, or trusted-device remembering.
274 274   </p>
275 275   <a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Contact Agnease</a>
276 276   </div>
Agnease.Code.SEODetailsClass[0]
metaDescription
... ... @@ -1,0 +1,1 @@
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,0 +1,1 @@
1 +XWiki Two-Factor Authentication | 2FA and MFA for XWiki