Changes for page XWiki Two-Factor Authentication
Last modified by Agnease on 2026/06/29 13:22
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 12 added, 0 removed)
- mfa-admin-configuration.png
- mfa-admin-full.png
- mfa-admin-overview.png
- mfa-admin-user-management.png
- mfa-login-verification-code.png
- mfa-login-verification-setup.png
- mfa-recovery-codes-generated.png
- mfa-recovery-codes-not-generated.png
- mfa-trusted-devices.png
- mfa-user-profile-full.png
- mfa-user-profile-overview.png
- mfa-user-setup-qr.png
-
Objects (0 modified, 1 added, 0 removed)
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 - xwiki-two-factor-authentication1 +XWiki Two-Factor Authentication - Content
-
... ... @@ -1,26 +1,110 @@ 1 1 {{velocity}} 2 2 #set ($discard = $xwiki.ssx.use('PublicWebSite.WebHome')) 3 3 #set ($discard = $xwiki.ssx.use('products.WebHome')) 4 + 5 +#set ($mainCapabilityItems = [{ 6 + 'title': 'Second verification step', 7 + 'icon': 'key', 8 + 'content': 'Add an additional verification screen after the normal XWiki username and password login.' 9 +},{ 10 + 'title': 'Authenticator app codes', 11 + 'icon': 'mobile', 12 + 'content': 'Let users verify access with time-based TOTP codes generated by authenticator applications.' 13 +},{ 14 + 'title': 'Recovery and trusted devices', 15 + 'icon': 'shield', 16 + 'content': 'Provide backup access with recovery codes and reduce repeated prompts on trusted browsers.' 17 +}]) 18 + 19 +#set ($adminExperienceItems = [{ 20 + 'title': 'MFA policy', 21 + 'icon': 'cog', 22 + 'content': 'Make MFA optional or required for all users from the XWiki Administration section.' 23 +},{ 24 + 'title': 'Configuration options', 25 + 'icon': 'sliders', 26 + 'content': 'Set the authenticator issuer name, recovery-code count and trusted-device duration.' 27 +},{ 28 + 'title': 'Administration overview', 29 + 'icon': 'table', 30 + 'content': 'Review MFA adoption with summary indicators and a filterable Live Data table.' 31 +}]) 32 + 33 +#set ($userExperienceItems = [{ 34 + 'title': 'Self-service setup', 35 + 'icon': 'qrcode', 36 + 'content': 'Users configure MFA from their profile by scanning a QR code or entering the setup key manually.' 37 +},{ 38 + 'title': 'Login verification', 39 + 'icon': 'sign-in', 40 + 'content': 'After the normal login, users enter the code generated by their authenticator app.' 41 +},{ 42 + 'title': 'Trusted browser option', 43 + 'icon': 'desktop', 44 + 'content': 'Users can trust the current browser for the configured duration after successful verification.' 45 +}]) 46 + 47 +#set ($selfServiceItems = [{ 48 + 'title': 'Recovery codes', 49 + 'icon': 'life-ring', 50 + 'content': 'Recovery codes provide backup access when a user loses access to the authenticator application.' 51 +},{ 52 + 'title': 'Trusted devices', 53 + 'icon': 'desktop', 54 + 'content': 'Trusted devices can be reviewed and removed from the user profile.' 55 +},{ 56 + 'title': 'Profile management', 57 + 'icon': 'user', 58 + 'content': 'Users can review MFA status, generate recovery codes, manage trusted devices and reset MFA.' 59 +}]) 60 + 61 +#set ($adminSupportItems = [{ 62 + 'title': 'User MFA status', 63 + 'icon': 'user', 64 + 'content': 'Administrators can open a user profile and check the MFA status for that account.' 65 +},{ 66 + 'title': 'MFA reset', 67 + 'icon': 'refresh', 68 + 'content': 'Administrators can reset MFA when a user needs to restart the configuration process.' 69 +},{ 70 + 'title': 'Controlled recovery', 71 + 'icon': 'unlock-alt', 72 + 'content': 'Resetting MFA removes the authenticator setup, recovery codes and trusted devices for that user.' 73 +}]) 74 + 75 +#set ($rolloutItems = [{ 76 + 'title': 'Start with a pilot group', 77 + 'content': 'Test the extension with administrators or a small user group before enabling it widely.' 78 +},{ 79 + 'title': 'Define the MFA policy', 80 + 'content': 'Decide whether MFA should be optional at first or required for all users.' 81 +},{ 82 + 'title': 'Configure recovery options', 83 + 'content': 'Choose the number of recovery codes and whether trusted devices should be allowed.' 84 +},{ 85 + 'title': 'Inform users', 86 + 'content': 'Explain how users configure MFA, save recovery codes and manage trusted devices.' 87 +},{ 88 + 'title': 'Monitor adoption', 89 + 'content': 'Use the administration overview to identify users who still need to configure MFA.' 90 +}]) 91 + 4 4 {{html clean="false"}} 5 5 6 -<section class="hero hero-centered product-hero" aria-labelledby="product-title">94 +<section class="hero hero-centered" 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 securityextension98 + XWiki 2FA and MFA 11 11 </div> 12 12 13 13 <h1 id="product-title">XWiki Two-Factor Authentication</h1> 14 14 15 15 <p class="lead"> 16 - Add a second verification step to the standard XWiki login flow. 104 + Protect XWiki logins with a second verification step using authenticator app codes, 105 + recovery codes and trusted devices. 17 17 </p> 18 18 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 - 24 24 <div class="hero-actions"> 25 25 <a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Ask about this extension</a> 26 26 <a class="btn btn-secondary" href="$xwiki.getURL('products.WebHome')">View all products</a> ... ... @@ -32,25 +32,19 @@ 32 32 <div class="container"> 33 33 <div class="product-layout"> 34 34 <article class="product-summary-card"> 35 - <h2 id="overview-title"> Strongerlogin protectionforXWiki</h2>119 + <h2 id="overview-title">Two-factor authentication built into XWiki</h2> 36 36 37 37 <p> 38 - TheXWikiMFA /Two-Factor Authenticationextensionaddsadditionalverificationafterthe standard39 - XWiki username and passwordlogin. Itstrengthensaccount protection withoutreplacing thefamiliar40 - XWiki authenticationflow.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. 41 41 </p> 42 42 43 43 <p> 44 - The extension s upportsauthenticatorappcodesusingTOTP,email-deliveredone-timeverificationcodes,45 - and stricterconfigurationswhere both verificationmethodsare required.Thisallowsorganizationsto46 - choosebetweenasimpler2FA setup orastronger multi-stepMFApolicy.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. 47 47 </p> 48 - 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. 53 - </p> 54 54 </article> 55 55 56 56 <aside class="product-info-card" aria-labelledby="quick-facts-title"> ... ... @@ -57,12 +57,12 @@ 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 codes using TOTP</li>61 - <li> Supportsemail-deliveredone-timeverificationcodes</li>62 - <li> Canrequire appcode and emailcodetogetherforstricterMFA</li>63 - <li>Can remember trusted browsers or devices beyond the current session</li>64 - <li>Includes wiki administration anduserprofile controls</li>65 - <li> Canbeusedonthe mainwikiandsubwikis</li>138 + <li>Supports TOTP authenticator applications</li> 139 + <li>Can require MFA for all users</li> 140 + <li>Includes one-time recovery codes</li> 141 + <li>Can remember trusted browsers or devices</li> 142 + <li>Includes user self-service controls</li> 143 + <li>Includes an administration overview</li> 66 66 </ul> 67 67 </aside> 68 68 </div> ... ... @@ -69,190 +69,256 @@ 69 69 </div> 70 70 </section> 71 71 72 -<section aria-labelledby=" features-title">150 +<section aria-labelledby="capabilities-title"> 73 73 <div class="container"> 74 - <h2 id="features-title">Main capabilities</h2> 152 + <h2 id="capabilities-title">Main capabilities</h2> 153 + 75 75 <p class="section-intro"> 76 - The extension focuses on adding a practical second authentication step while keeping the standard XWiki login 77 - process and administration experience understandable. 155 + A focused set of MFA features for stronger XWiki account protection without replacing the familiar login experience. 78 78 </p> 79 79 80 80 <div class="product-feature-grid"> 81 - <article class="product-feature"> 82 - <div class="feature-icon"> 83 - <i class="fa fa-key" aria-hidden="true"></i> 84 - </div> 85 - <h3>Second login step</h3> 86 - <p> 87 - After the username and password are verified, users are asked to enter an additional verification code 88 - before accessing the wiki. 89 - </p> 90 - </article> 159 + #foreach ($entry in $mainCapabilityItems) 160 + <article class="product-feature"> 161 + <div class="card-heading"> 162 + <div class="feature-icon"> 163 + <i class="fa fa-$entry.icon" aria-hidden="true"></i> 164 + </div> 165 + <h3>$entry.title</h3> 166 + </div> 91 91 92 - <article class="product-feature"> 93 - <div class="feature-icon"> 94 - <i class="fa fa-mobile" aria-hidden="true"></i> 95 - </div> 96 - <h3>Authenticator app codes</h3> 97 - <p> 98 - Users can verify access with TOTP codes generated by authenticator applications on a mobile device or desktop. 99 - </p> 100 - </article> 168 + <p>$entry.content</p> 169 + </article> 170 + #end 171 + </div> 172 + </div> 173 +</section> 101 101 102 - <article class="product-feature"> 103 - <div class="feature-icon"> 104 - <i class="fa fa-envelope-o" aria-hidden="true"></i> 105 - </div> 106 - <h3>Email verification codes</h3> 107 - <p> 108 - Users can receive one-time verification codes by email, useful when an authenticator app is not available or preferred. 109 - </p> 110 - </article> 175 +<section class="product-section-muted" aria-labelledby="security-title"> 176 + <div class="container"> 177 + <div class="product-layout"> 178 + <article class="product-summary-card"> 179 + <h2 id="security-title">Useful for XWiki security and access protection</h2> 111 111 112 - <article class="product-feature"> 113 - <div class="feature-icon"> 114 - <i class="fa fa-plus-circle" aria-hidden="true"></i> 115 - </div> 116 - <h3>Combined verification</h3> 117 117 <p> 118 - The extension can also require both an authenticator app code and an email code for stricter multi-factor verification. 182 + Many organizations use XWiki to store internal documentation, procedures, operational 183 + knowledge and business-critical information. Adding a second authentication factor helps 184 + reduce the risk of account compromise when a password is exposed or reused. 119 119 </p> 120 - </article> 121 121 122 - <article class="product-feature"> 123 - <div class="feature-icon"> 124 - <i class="fa fa-qrcode" aria-hidden="true"></i> 125 - </div> 126 - <h3>User setup screen</h3> 127 127 <p> 128 - Users can configure their verification code setup during login or from their XWiki profile when needed. 188 + The extension is especially useful for protecting administrator accounts, remote users, 189 + private knowledge bases and customer or partner portals. 129 129 </p> 130 130 </article> 131 131 132 - <article class="product-feature"> 133 - <div class="feature-icon"> 134 - <i class="fa fa-laptop" aria-hidden="true"></i> 135 - </div> 136 - <h3>Remember trusted clients</h3> 137 - <p> 138 - Known browsers or devices can be remembered for a configured period, reducing repeated MFA prompts from trusted clients. 139 - </p> 140 - </article> 193 + <aside class="product-info-card" aria-labelledby="use-cases-title"> 194 + <h3 id="use-cases-title">Typical use cases</h3> 195 + <ul> 196 + <li>Administrator account protection</li> 197 + <li>Internal knowledge base security</li> 198 + <li>Private documentation platforms</li> 199 + <li>Remote user access protection</li> 200 + <li>Customer or partner portals</li> 201 + <li>Security review, MFA rollout and compliance readiness</li> 202 + </ul> 203 + </aside> 204 + </div> 205 + </div> 206 +</section> 141 141 142 - article class="product-feature"> 143 - <div class="feature-icon"> 144 - <i class="fa fa-sliders" aria-hidden="true"></i> 145 - </div> 146 - <h3>Administration controls</h3> 147 - <p> 148 - Administrators can configure MFA behavior, manage user activation, and reset user setup when required. 149 - </p> 150 - </article> 208 +<section aria-labelledby="admin-experience-title"> 209 + <div class="container"> 210 + <h2 id="admin-experience-title">Administrator configuration and monitoring</h2> 151 151 152 - <article class="product-feature"> 153 - <div class="feature-icon"> 154 - <i class="fa fa-user" aria-hidden="true"></i> 155 - </div> 156 - <h3>Profile integration</h3> 157 - <p> 158 - The extension adds user profile controls so the second-factor setup can be reviewed or reset from XWiki. 159 - </p> 160 - </article> 212 + <p class="section-intro"> 213 + Administrators can configure the MFA policy, define recovery options and monitor adoption from the XWiki Administration section. 214 + </p> 161 161 162 - <articleclass="product-feature">163 - <divclass="feature-icon">164 - <i class="fa fa-random" aria-hidden="true"></i>165 - < /div>166 - < h3>Fallback behavior</h3>167 - < p>168 - Theextensioncan fall back to standard XWiki authentication when the feature is not enabled or not configured.169 - </ p>170 - </ article>216 + <div class="product-feature-grid"> 217 + #foreach ($entry in $adminExperienceItems) 218 + <article class="product-feature"> 219 + <div class="card-heading"> 220 + <div class="feature-icon"> 221 + <i class="fa fa-$entry.icon" aria-hidden="true"></i> 222 + </div> 223 + <h3>$entry.title</h3> 224 + </div> 171 171 172 - <article class="product-feature"> 173 - <div class="feature-icon"> 174 - <i class="fa fa-sitemap" aria-hidden="true"></i> 175 - </div> 176 - <h3>Main wiki and subwikis</h3> 177 - <p> 178 - The extension is designed to support XWiki environments using the main wiki and subwikis. 179 - </p> 180 - </article> 226 + <p>$entry.content</p> 227 + </article> 228 + #end 181 181 </div> 230 + 231 +{{/html}} 232 + 233 +{{gallery}} 234 +[[image:mfa-admin-configuration.png]] 235 +[[image:mfa-admin-overview.png]] 236 +[[image:mfa-admin-full.png]] 237 +{{/gallery}} 238 + 239 +{{html clean="false"}} 240 + 241 + <p class="product-gallery-caption"> 242 + Administration screens for configuring MFA and reviewing MFA adoption across users. 243 + </p> 182 182 </div> 183 183 </section> 184 184 185 -<section aria-labelledby="use-c ases-title">247 +<section class="product-section-muted" aria-labelledby="user-experience-title"> 186 186 <div class="container"> 187 - <div class="product-layout"> 188 - <article class="product-summary-card"> 189 - <h2 id="use-cases-title">When this extension is useful</h2> 249 + <h2 id="user-experience-title">User setup and login verification</h2> 190 190 191 - <p> 192 - Two-factor authentication is especially relevant when XWiki contains internal documentation, procedures, 193 - customer information, project knowledge, administrative pages, or business-critical content. 194 - </p> 251 + <p class="section-intro"> 252 + Users can configure MFA from their profile or during the enforced setup flow, then verify future logins with their authenticator app. 253 + </p> 195 195 196 - <p> 197 - It can also support organizations that need MFA as part of their cybersecurity controls, including companies 198 - working toward NIS 2 readiness. NIS 2 focuses on stronger cybersecurity risk management across essential and 199 - important entities in the EU, and MFA is often expected as part of enterprise access protection programs. 200 - </p> 255 + <div class="product-feature-grid"> 256 + #foreach ($entry in $userExperienceItems) 257 + <article class="product-feature"> 258 + <div class="card-heading"> 259 + <div class="feature-icon"> 260 + <i class="fa fa-$entry.icon" aria-hidden="true"></i> 261 + </div> 262 + <h3>$entry.title</h3> 263 + </div> 201 201 202 - <p> 203 - It is also useful when many users access the wiki remotely, when administrator accounts need stronger protection, 204 - or when the organization wants to reduce the risk of compromised passwords. 205 - </p> 206 - </article> 265 + <p>$entry.content</p> 266 + </article> 267 + #end 268 + </div> 207 207 208 - <aside class="product-info-card" aria-labelledby="good-fit-title"> 209 - <h3 id="good-fit-title">Good fit for</h3> 210 - <ul> 211 - <li>Private XWiki knowledge bases</li> 212 - <li>Company intranets</li> 213 - <li>SOP and controlled-document platforms</li> 214 - <li>Documentation portals with sensitive content</li> 215 - <li>Wikis with several administrators or remote users</li> 216 - </ul> 217 - </aside> 270 +{{/html}} 271 + 272 +{{gallery}} 273 +[[image:mfa-user-setup-qr.png]] 274 +[[image:mfa-login-verification-setup.png]] 275 +[[image:mfa-login-verification-code.png]] 276 +{{/gallery}} 277 + 278 +{{html clean="false"}} 279 + 280 + <p class="product-gallery-caption"> 281 + User setup, enforced MFA configuration and login verification screens. 282 + </p> 283 + </div> 284 +</section> 285 + 286 +<section aria-labelledby="self-service-title"> 287 + <div class="container"> 288 + <h2 id="self-service-title">Recovery codes and trusted devices</h2> 289 + 290 + <p class="section-intro"> 291 + Recovery codes and trusted devices help balance stronger access protection with a smoother user experience. 292 + </p> 293 + 294 + <div class="product-feature-grid"> 295 + #foreach ($entry in $selfServiceItems) 296 + <article class="product-feature"> 297 + <div class="card-heading"> 298 + <div class="feature-icon"> 299 + <i class="fa fa-$entry.icon" aria-hidden="true"></i> 300 + </div> 301 + <h3>$entry.title</h3> 302 + </div> 303 + 304 + <p>$entry.content</p> 305 + </article> 306 + #end 218 218 </div> 308 + 309 +{{/html}} 310 + 311 +{{gallery}} 312 +[[image:mfa-user-profile-overview.png]] 313 +[[image:mfa-recovery-codes-not-generated.png]] 314 +[[image:mfa-recovery-codes-generated.png]] 315 +[[image:mfa-trusted-devices.png]] 316 +[[image:mfa-user-profile-full.png]] 317 +{{/gallery}} 318 + 319 +{{html clean="false"}} 320 + 321 + <p class="product-gallery-caption"> 322 + User profile screens for recovery codes, trusted devices and MFA self-service management. 323 + </p> 219 219 </div> 220 220 </section> 221 221 222 -<section class="product-section-muted" aria-labelledby=" compliance-title">327 +<section class="product-section-muted" aria-labelledby="admin-support-title"> 223 223 <div class="container"> 329 + <h2 id="admin-support-title">Administrator support and user recovery</h2> 330 + 331 + <p class="section-intro"> 332 + Administrators can help users recover from lost devices or restart MFA setup when needed. 333 + </p> 334 + 335 + <div class="product-feature-grid"> 336 + #foreach ($entry in $adminSupportItems) 337 + <article class="product-feature"> 338 + <div class="card-heading"> 339 + <div class="feature-icon"> 340 + <i class="fa fa-$entry.icon" aria-hidden="true"></i> 341 + </div> 342 + <h3>$entry.title</h3> 343 + </div> 344 + 345 + <p>$entry.content</p> 346 + </article> 347 + #end 348 + </div> 349 + 350 +{{/html}} 351 + 352 +{{gallery}} 353 +[[image:mfa-admin-user-management.png]] 354 +{{/gallery}} 355 + 356 +{{html clean="false"}} 357 + 358 + <p class="product-gallery-caption"> 359 + Administrator view for checking and resetting a user MFA setup. 360 + </p> 361 + </div> 362 +</section> 363 + 364 +<section aria-labelledby="rollout-title"> 365 + <div class="container"> 224 224 <div class="product-layout"> 225 225 <article class="product-summary-card"> 226 - <h2 id=" compliance-title">Usefulfor MFA adoptionand NIS 2readiness</h2>368 + <h2 id="rollout-title">Rollout recommendations</h2> 227 227 228 228 <p> 229 - Many organizations now need multi-factor authentication for enterprise software, including internal 230 - knowledge bases, documentation platforms, intranets and systems that contain operational procedures 231 - or sensitive business information. 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. 232 232 </p> 233 233 234 - <p> 235 - For organizations using XWiki, adding MFA directly to the standard XWiki login flow can help close a 236 - practical access-control gap. The extension can support simple 2FA with one additional verification method, 237 - or a stricter MFA setup where both authenticator app and email verification are required. 238 - </p> 375 + <ol class="process-list"> 376 + #foreach ($entry in $rolloutItems) 377 + <li> 378 + <strong>$entry.title</strong> 379 + $entry.content 380 + </li> 381 + #end 382 + </ol> 383 + </article> 239 239 240 - <p>241 - ThiscanberelevantfororganizationspreparingforNIS 2, wheremulti-factor authenticationor242 - continuous authentication is part of cybersecurity risk-management measures, where appropriate.243 - MFA supportin XWiki is only one part of a broadercompliance andsecurityprogram, butitcanbean244 - importanttechnical controlforprotectingaccessto the wiki.385 + <aside class="product-info-card" aria-labelledby="planning-title"> 386 + <h3 id="planning-title">Useful information before installation</h3> 387 + 388 + <p class="product-card-note"> 389 + These details help evaluate compatibility, rollout scope and configuration options. 245 245 </p> 246 - </article> 247 247 248 - <aside class="product-info-card" aria-labelledby="mfa-readiness-title"> 249 - <h3 id="mfa-readiness-title">Security controls supported</h3> 250 250 <ul> 251 - <li>Second-factor verification after password login</li> 252 - <li>Authenticator app or email-based verification codes</li> 253 - <li>Reduced repeated prompts for trusted clients</li> 254 - <li>Administration controls for user-level MFA management</li> 255 - <li>Better protection for administrator and remote-access accounts</li> 393 + <li>XWiki version</li> 394 + <li>Single wiki or wiki farm with subwikis</li> 395 + <li>Current authentication setup</li> 396 + <li>Optional or globally required MFA policy</li> 397 + <li>Trusted-device policy</li> 398 + <li>Recovery-code policy</li> 399 + <li>Rollout communication needs</li> 256 256 </ul> 257 257 </aside> 258 258 </div> ... ... @@ -259,31 +259,15 @@ 259 259 </div> 260 260 </section> 261 261 262 -#* 263 -<section aria-labelledby="gallery-title"> 264 - <div class="container"> 265 - <div class="product-gallery-panel"> 266 - <h2 id="gallery-title">Screenshots</h2> 267 - <p class="gallery-note"> 268 - Use this area to show the login verification screen, first-time setup, user profile controls, 269 - and administration configuration. 270 - </p> 271 - 272 - <div class="product-gallery-placeholder"> 273 - Replace this placeholder with the XWiki gallery macro and 3-5 screenshots from the application. 274 - </div> 275 - </div> 276 - </div> 277 -</section> 278 -*# 279 279 <section class="cta-section" aria-labelledby="cta-title"> 280 280 <div class="container"> 281 281 <div class="cta-panel"> 282 282 <h2 id="cta-title">Interested in using this extension?</h2> 410 + 283 283 <p> 284 - Send a short message with your XWiki version, authentication setup, and whether you use a single wiki 285 - or a main wiki with subwikis. 412 + Send a short message with your XWiki version, current authentication setup and MFA rollout goal. 286 286 </p> 414 + 287 287 <a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Contact Agnease</a> 288 288 </div> 289 289 </div>
- mfa-admin-configuration.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Admin - Size
-
... ... @@ -1,0 +1,1 @@ 1 +125.3 KB - Content
- mfa-admin-full.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Admin - Size
-
... ... @@ -1,0 +1,1 @@ 1 +184.3 KB - Content
- mfa-admin-overview.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Admin - Size
-
... ... @@ -1,0 +1,1 @@ 1 +64.7 KB - Content
- mfa-admin-user-management.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Admin - Size
-
... ... @@ -1,0 +1,1 @@ 1 +26.9 KB - Content
- mfa-login-verification-code.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Admin - Size
-
... ... @@ -1,0 +1,1 @@ 1 +23.6 KB - Content
- mfa-login-verification-setup.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Admin - Size
-
... ... @@ -1,0 +1,1 @@ 1 +115.9 KB - Content
- mfa-recovery-codes-generated.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Admin - Size
-
... ... @@ -1,0 +1,1 @@ 1 +38.5 KB - Content
- mfa-recovery-codes-not-generated.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Admin - Size
-
... ... @@ -1,0 +1,1 @@ 1 +27.0 KB - Content
- mfa-trusted-devices.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Admin - Size
-
... ... @@ -1,0 +1,1 @@ 1 +59.1 KB - Content
- mfa-user-profile-full.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Admin - Size
-
... ... @@ -1,0 +1,1 @@ 1 +197.5 KB - Content
- mfa-user-profile-overview.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Admin - Size
-
... ... @@ -1,0 +1,1 @@ 1 +193.4 KB - Content
- mfa-user-setup-qr.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Admin - Size
-
... ... @@ -1,0 +1,1 @@ 1 +176.6 KB - Content
- Agnease.Code.SEODetailsClass[0]
-
- metaDescription
-
... ... @@ -1,0 +1,1 @@ 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,0 +1,1 @@ 1 +XWiki Two-Factor Authentication with 2FA and MFA Support | Agnease