Changes for page XWiki Two-Factor Authentication

Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -1,5 +1,6 @@
1	1	{{velocity}}
2	2	#set ($discard = $xwiki.ssx.use('PublicWebSite.WebHome'))
	3	+#set ($discard = $xwiki.ssx.use('products.WebHome'))
3	3
4	4	#set ($mainCapabilityItems = [{
5	5	'title': 'Second verification step',
...	...	@@ -16,9 +16,9 @@
16	16	}])
17	17
18	18	#set ($adminExperienceItems = [{
19		- 'title': 'Rollout policy',
	20	+ 'title': 'MFA policy',
20	20	'icon': 'cog',
21		- 'content': 'Make additional verification optional at first or required for all users from the XWiki Administration section.'
	22	+ 'content': 'Make MFA optional or required for all users from the XWiki Administration section.'
22	22	},{
23	23	'title': 'Configuration options',
24	24	'icon': 'sliders',
...	...	@@ -26,17 +26,17 @@
26	26	},{
27	27	'title': 'Administration overview',
28	28	'icon': 'table',
29		- 'content': 'Review adoption with summary indicators and a filterable Live Data table.'
	30	+ 'content': 'Review MFA adoption with summary indicators and a filterable Live Data table.'
30	30	}])
31	31
32	32	#set ($userExperienceItems = [{
33	33	'title': 'Self-service setup',
34	34	'icon': 'qrcode',
35		- 'content': 'Users configure the second verification step from their profile by scanning a QR code or entering the setup key manually.'
	36	+ 'content': 'Users configure MFA from their profile by scanning a QR code or entering the setup key manually.'
36	36	},{
37	37	'title': 'Login verification',
38	38	'icon': 'sign-in',
39		- 'content': 'After the normal login, users enter the verification code generated by their authenticator app.'
	40	+ 'content': 'After the normal login, users enter the code generated by their authenticator app.'
40	40	},{
41	41	'title': 'Trusted browser option',
42	42	'icon': 'desktop',
...	...	@@ -54,21 +54,21 @@
54	54	},{
55	55	'title': 'Profile management',
56	56	'icon': 'user',
57		- 'content': 'Users can review status, generate recovery codes, manage trusted devices and reset their setup.'
	58	+ 'content': 'Users can review MFA status, generate recovery codes, manage trusted devices and reset MFA.'
58	58	}])
59	59
60	60	#set ($adminSupportItems = [{
61		- 'title': 'User status',
	62	+ 'title': 'User MFA status',
62	62	'icon': 'user',
63		- 'content': 'Administrators can open a user profile and check the verification status for that account.'
	64	+ 'content': 'Administrators can open a user profile and check the MFA status for that account.'
64	64	},{
65		- 'title': 'Setup reset',
	66	+ 'title': 'MFA reset',
66	66	'icon': 'refresh',
67		- 'content': 'Administrators can reset the setup when a user needs to restart the configuration process.'
	68	+ 'content': 'Administrators can reset MFA when a user needs to restart the configuration process.'
68	68	},{
69	69	'title': 'Controlled recovery',
70	70	'icon': 'unlock-alt',
71		- 'content': 'Resetting the setup removes the authenticator configuration, recovery codes and trusted devices for that user.'
	72	+ 'content': 'Resetting MFA removes the authenticator setup, recovery codes and trusted devices for that user.'
72	72	}])
73	73
74	74	#set ($rolloutItems = [{
...	...	@@ -75,17 +75,17 @@
75	75	'title': 'Start with a pilot group',
76	76	'content': 'Test the extension with administrators or a small user group before enabling it widely.'
77	77	},{
78		- 'title': 'Define the rollout policy',
79		- 'content': 'Decide whether additional verification should be optional at first or required for all users.'
	79	+ 'title': 'Define the MFA policy',
	80	+ 'content': 'Decide whether MFA should be optional at first or required for all users.'
80	80	},{
81	81	'title': 'Configure recovery options',
82	82	'content': 'Choose the number of recovery codes and whether trusted devices should be allowed.'
83	83	},{
84	84	'title': 'Inform users',
85		- 'content': 'Explain how users configure the authenticator app, save recovery codes and manage trusted devices.'
	86	+ 'content': 'Explain how users configure MFA, save recovery codes and manage trusted devices.'
86	86	},{
87	87	'title': 'Monitor adoption',
88		- 'content': 'Use the administration overview to identify users who still need to configure protection.'
	89	+ 'content': 'Use the administration overview to identify users who still need to configure MFA.'
89	89	}])
90	90
91	91	{{html clean="false"}}
...	...	@@ -94,14 +94,14 @@
94	94	<div class="container hero-inner">
95	95	<div class="hero-kicker">
96	96	<i class="fa fa-lock" aria-hidden="true"></i>
97		- XWiki 2FA with MFA rollout support
	98	+ XWiki 2FA and MFA
98	98	</div>
99	99
100		- <h1 id="product-title">XWiki Two-Factor Authentication</h1>
	101	+ <h1 id="product-title">XWiki Two-Factor Authentication (2FA/MFA)</h1>
101	101
102	102	<p class="lead">
103		- Protect XWiki logins with authenticator app verification, recovery codes,
104		- trusted devices and administration controls for a safer rollout.
	104	+ Protect XWiki logins with a second verification step using authenticator app codes,
	105	+ recovery codes and trusted devices.
105	105	</p>
106	106
107	107	<div class="hero-actions">
...	...	@@ -118,15 +118,15 @@
118	118	<h2 id="overview-title">Two-factor authentication built into XWiki</h2>
119	119
120	120	<p>
121		- XWiki Two-Factor Authentication adds an additional verification step to the standard
122		- XWiki login flow. Users continue to sign in with their normal username and password,
123		- then confirm access with a time-based code from an authenticator application.
	122	+ XWiki Two-Factor Authentication adds MFA support to the standard XWiki login flow.
	123	+ Users continue to sign in with their normal username and password, then confirm access
	124	+ with a time-based verification code from an authenticator application.
124	124	</p>
125	125
126	126	<p>
127		- The application has evolved beyond a simple login-code screen. It also supports
128		- global enforcement, recovery codes, trusted devices, user self-service management,
129		- administrator reset actions and an administration overview for monitoring adoption.
	128	+ The extension is designed for organizations that want stronger access protection for
	129	+ internal knowledge bases, intranets, documentation platforms, customer portals and other
	130	+ XWiki-based applications.
130	130	</p>
131	131	</article>
132	132
...	...	@@ -135,7 +135,7 @@
135	135	<ul>
136	136	<li>Works with the standard XWiki login flow</li>
137	137	<li>Supports TOTP authenticator applications</li>
138		- <li>Can require additional verification for all users</li>
	139	+ <li>Can require MFA for all users</li>
139	139	<li>Includes one-time recovery codes</li>
140	140	<li>Can remember trusted browsers or devices</li>
141	141	<li>Includes user self-service controls</li>
...	...	@@ -151,8 +151,7 @@
151	151	<h2 id="capabilities-title">Main capabilities</h2>
152	152
153	153	<p class="section-intro">
154		- A focused set of authentication protection features for stronger XWiki account security
155		- without replacing the familiar login experience.
	155	+ A focused set of MFA features for stronger XWiki account protection without replacing the familiar login experience.
156	156	</p>
157	157
158	158	<div class="product-feature-grid">
...	...	@@ -180,7 +180,7 @@
180	180
181	181	<p>
182	182	Many organizations use XWiki to store internal documentation, procedures, operational
183		- knowledge and business-critical information. Adding an additional authentication factor helps
	183	+ knowledge and business-critical information. Adding a second authentication factor helps
184	184	reduce the risk of account compromise when a password is exposed or reused.
185	185	</p>
186	186
...	...	@@ -210,8 +210,7 @@
210	210	<h2 id="admin-experience-title">Administrator configuration and monitoring</h2>
211	211
212	212	<p class="section-intro">
213		- Administrators can configure the policy, define recovery options and monitor adoption
214		- from the XWiki Administration section.
	213	+ Administrators can configure the MFA policy, define recovery options and monitor adoption from the XWiki Administration section.
215	215	</p>
216	216
217	217	<div class="product-feature-grid">
...	...	@@ -240,7 +240,7 @@
240	240	{{html clean="false"}}
241	241
242	242	<p class="product-gallery-caption">
243		- Administration screens for configuring the policy and reviewing adoption across users.
	242	+ Administration screens for configuring MFA and reviewing MFA adoption across users.
244	244	</p>
245	245	</div>
246	246	</section>
...	...	@@ -250,8 +250,7 @@
250	250	<h2 id="user-experience-title">User setup and login verification</h2>
251	251
252	252	<p class="section-intro">
253		- Users can configure the authenticator app from their profile or during the enforced setup flow,
254		- then verify future logins with a generated code.
	252	+ Users can configure MFA from their profile or during the enforced setup flow, then verify future logins with their authenticator app.
255	255	</p>
256	256
257	257	<div class="product-feature-grid">
...	...	@@ -280,7 +280,7 @@
280	280	{{html clean="false"}}
281	281
282	282	<p class="product-gallery-caption">
283		- User setup, enforced configuration and login verification screens.
	281	+ User setup, enforced MFA configuration and login verification screens.
284	284	</p>
285	285	</div>
286	286	</section>
...	...	@@ -321,7 +321,7 @@
321	321	{{html clean="false"}}
322	322
323	323	<p class="product-gallery-caption">
324		- User profile screens for recovery codes, trusted devices and self-service management.
	322	+ User profile screens for recovery codes, trusted devices and MFA self-service management.
325	325	</p>
326	326	</div>
327	327	</section>
...	...	@@ -331,7 +331,7 @@
331	331	<h2 id="admin-support-title">Administrator support and user recovery</h2>
332	332
333	333	<p class="section-intro">
334		- Administrators can help users recover from lost devices or restart setup when needed.
	332	+ Administrators can help users recover from lost devices or restart MFA setup when needed.
335	335	</p>
336	336
337	337	<div class="product-feature-grid">
...	...	@@ -358,91 +358,20 @@
358	358	{{html clean="false"}}
359	359
360	360	<p class="product-gallery-caption">
361		- Administrator view for checking and resetting a user setup.
	359	+ Administrator view for checking and resetting a user MFA setup.
362	362	</p>
363	363	</div>
364	364	</section>
365	365
366		-<section aria-labelledby="faq-title">
	364	+<section aria-labelledby="rollout-title">
367	367	<div class="container">
368		- <h2 id="faq-title">Frequently asked questions</h2>
369		-
370		- <p class="section-intro">
371		- Common questions about how the extension works, how users configure it and how administrators can manage rollout and recovery.
372		- </p>
373		-
374		- <div class="resource-content">
375		- <details class="resource-faq-item">
376		- <summary>Does this extension replace the standard XWiki login?</summary>
377		- <p>
378		- No. Users still sign in with their normal XWiki username and password. The extension adds
379		- an additional verification step after the standard login check.
380		- </p>
381		- </details>
382		-
383		- <details class="resource-faq-item">
384		- <summary>Which verification method is used?</summary>
385		- <p>
386		- Users verify access with time-based codes generated by an authenticator application.
387		- The setup page provides a QR code and a manual setup key.
388		- </p>
389		- </details>
390		-
391		- <details class="resource-faq-item">
392		- <summary>Can the second verification step be required for all users?</summary>
393		- <p>
394		- Yes. Administrators can make the verification step optional or required for all users
395		- from the XWiki Administration section.
396		- </p>
397		- </details>
398		-
399		- <details class="resource-faq-item">
400		- <summary>What happens if a user loses access to the authenticator app?</summary>
401		- <p>
402		- Recovery codes can provide backup access when enabled. Administrators can also reset
403		- the user setup so the configuration process can be restarted.
404		- </p>
405		- </details>
406		-
407		- <details class="resource-faq-item">
408		- <summary>Can trusted browsers or devices be disabled?</summary>
409		- <p>
410		- Yes. Administrators can configure how long trusted devices remain valid. Setting the
411		- trusted-device duration to 0 disables this option.
412		- </p>
413		- </details>
414		-
415		- <details class="resource-faq-item">
416		- <summary>Is this only a basic 2FA login-code screen?</summary>
417		- <p>
418		- No. The main login mechanism is two-factor authentication, but the application also includes
419		- features needed for a safer organization-wide rollout: enforcement policy, recovery codes,
420		- trusted devices, user self-service, administrator monitoring and administrator reset actions.
421		- </p>
422		- </details>
423		-
424		- <details class="resource-faq-item">
425		- <summary>Is this enough for compliance on its own?</summary>
426		- <p>
427		- No. This extension provides an important access-protection control, but it should be part
428		- of a broader security and compliance approach that includes permissions, upgrades,
429		- infrastructure, monitoring and operational procedures.
430		- </p>
431		- </details>
432		- </div>
433		- </div>
434		-</section>
435		-
436		-<section class="product-section-muted" aria-labelledby="rollout-title">
437		- <div class="container">
438	438	<div class="product-layout">
439	439	<article class="product-summary-card">
440	440	<h2 id="rollout-title">Rollout recommendations</h2>
441	441
442	442	<p>
443		- For a smooth rollout, start with a small administrator or pilot group before requiring
444		- the additional verification step for everyone. This helps validate the configuration,
445		- prepare user communication and reduce support issues.
	371	+ For a smooth rollout, start with a small administrator or pilot group before requiring MFA for everyone.
	372	+ This helps validate the configuration, prepare user communication and reduce support issues.
446	446	</p>
447	447
448	448	<ol class="process-list">
...	...	@@ -466,7 +466,7 @@
466	466	<li>XWiki version</li>
467	467	<li>Single wiki or wiki farm with subwikis</li>
468	468	<li>Current authentication setup</li>
469		- <li>Optional or required rollout policy</li>
	396	+ <li>Optional or globally required MFA policy</li>
470	470	<li>Trusted-device policy</li>
471	471	<li>Recovery-code policy</li>
472	472	<li>Rollout communication needs</li>
...	...	@@ -482,7 +482,7 @@
482	482	<h2 id="cta-title">Interested in using this extension?</h2>
483	483
484	484	<p>
485		- Send a short message with your XWiki version, current authentication setup and rollout goal.
	412	+ Send a short message with your XWiki version, current authentication setup and MFA rollout goal.
486	486	</p>
487	487
488	488	<a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Contact Agnease</a>