Version 6.3 by Agnease on 2026/05/22 08:52

Show last authors
1 {{velocity}}
2 #set ($discard = $xwiki.ssx.use('PublicWebSite.WebHome'))
3 #set ($discard = $xwiki.ssx.use('products.WebHome'))
4 {{html clean="false"}}
5
6 <section class="hero hero-centered product-hero" aria-labelledby="product-title">
7 <div class="container hero-inner">
8 <div class="hero-kicker">
9 <i class="fa fa-lock" aria-hidden="true"></i>
10 XWiki 2FA and MFA
11 </div>
12
13 <h1 id="product-title">XWiki Two-Factor Authentication</h1>
14
15 <p class="lead">
16 Protect XWiki logins with a second verification step using authenticator app codes,
17 email verification codes, or both.
18 </p>
19
20 <div class="hero-actions">
21 <a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Ask about this extension</a>
22 <a class="btn btn-secondary" href="$xwiki.getURL('products.WebHome')">View all products</a>
23 </div>
24 </div>
25 </section>
26
27 <section aria-labelledby="overview-title">
28 <div class="container">
29 <div class="product-layout">
30 <article class="product-summary-card">
31 <h2 id="overview-title">Two-factor authentication built into XWiki</h2>
32
33 <p>
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.
37 </p>
38
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.
42 </p>
43
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.
47 </p>
48 </article>
49
50 <aside class="product-info-card" aria-labelledby="quick-facts-title">
51 <h3 id="quick-facts-title">Quick facts</h3>
52 <ul>
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>
59 </ul>
60 </aside>
61 </div>
62 </div>
63 </section>
64
65 <section aria-labelledby="features-title">
66 <div class="container">
67 <h2 id="features-title">Main capabilities</h2>
68
69 <p class="section-intro">
70 A focused set of MFA/2FA features for stronger XWiki account protection without changing the standard login experience.
71 </p>
72
73 <div class="product-feature-grid">
74 <article class="product-feature">
75 <div class="feature-icon">
76 <i class="fa fa-key" aria-hidden="true"></i>
77 </div>
78 <h3>Second verification step</h3>
79 <p>
80 After username and password verification, users complete an additional step before accessing XWiki.
81 The flow can require one verification method or both app and email codes.
82 </p>
83 </article>
84
85 <article class="product-feature">
86 <div class="feature-icon">
87 <i class="fa fa-mobile" aria-hidden="true"></i>
88 </div>
89 <h3>Authenticator app codes</h3>
90 <p>
91 Users can verify access with TOTP codes generated by authenticator applications on mobile or desktop devices.
92 </p>
93 </article>
94
95 <article class="product-feature">
96 <div class="feature-icon">
97 <i class="fa fa-envelope-o" aria-hidden="true"></i>
98 </div>
99 <h3>Email verification codes</h3>
100 <p>
101 Users can receive one-time verification codes by email when an authenticator app is not available or preferred.
102 </p>
103 </article>
104 </div>
105 </div>
106 </section>
107
108 <section class="product-section-muted" aria-labelledby="security-title">
109 <div class="container">
110 <div class="product-layout">
111 <article class="product-summary-card">
112 <h2 id="security-title">Useful for XWiki security and NIS 2 readiness</h2>
113
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.
118 </p>
119
120 <p>
121 For organizations using XWiki, adding two-factor authentication directly to the standard login flow
122 can help close a practical access-control gap. It can be useful for administrator accounts, remote users,
123 private knowledge bases and broader security readiness initiatives such as NIS 2 preparation.
124 </p>
125
126 <p>
127 This extension is not a complete compliance solution on its own, but it can provide an important
128 technical control for protecting access to XWiki.
129 </p>
130 </article>
131
132 <aside class="product-info-card" aria-labelledby="security-controls-title">
133 <h3 id="security-controls-title">Useful for</h3>
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>
141 </ul>
142 </aside>
143 </div>
144 </div>
145 </section>
146
147 <section class="cta-section" aria-labelledby="cta-title">
148 <div class="container">
149 <div class="cta-panel">
150 <h2 id="cta-title">Interested in using this extension?</h2>
151 <p>
152 Send a short message with your XWiki version, authentication setup, and whether you need
153 authenticator app codes, email verification codes, combined verification, or trusted-device remembering.
154 </p>
155 <a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Contact Agnease</a>
156 </div>
157 </div>
158 </section>
159
160 {{/html}}
161 {{/velocity}}