Wiki source code of xwiki-two-factor-authentication
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
| |
1.18 | 1 | {{velocity}} |
| 2 | #set ($discard = $xwiki.ssx.use('PublicWebSite.WebHome')) | ||
| 3 | #set ($discard = $xwiki.ssx.use('products.WebHome')) | ||
| 4 | {{html clean="false"}} | ||
| |
1.2 | 5 | |
| |
1.18 | 6 | <section class="hero hero-centered product-hero" aria-labelledby="product-title"> |
| 7 | <div class="container hero-inner"> | ||
| 8 | <div class="hero-kicker"> | ||
| |
1.2 | 9 | <i class="fa fa-lock" aria-hidden="true"></i> |
| |
1.18 | 10 | XWiki 2FA and MFA |
| |
1.2 | 11 | </div> |
| 12 | |||
| |
1.18 | 13 | <h1 id="product-title">XWiki Two-Factor Authentication</h1> |
| |
1.2 | 14 | |
| |
1.18 | 15 | <p class="lead"> |
| 16 | Add a second verification step to the standard XWiki login flow. | ||
| |
1.2 | 17 | </p> |
| 18 | |||
| |
1.18 | 19 | <p class="hero-support"> |
| 20 | Protect XWiki accounts with authenticator app codes, email verification codes, | ||
| 21 | or a combined setup requiring both. | ||
| 22 | </p> | ||
| |
1.2 | 23 | |
| |
1.18 | 24 | <div class="hero-actions"> |
| 25 | <a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Ask about this extension</a> | ||
| 26 | <a class="btn btn-secondary" href="$xwiki.getURL('products.WebHome')">View all products</a> | ||
| 27 | </div> | ||
| 28 | </div> | ||
| 29 | </section> | ||
| 30 | |||
| 31 | <section aria-labelledby="overview-title"> | ||
| 32 | <div class="container"> | ||
| 33 | <div class="product-layout"> | ||
| 34 | <article class="product-summary-card"> | ||
| 35 | <h2 id="overview-title">Two-factor authentication built into XWiki</h2> | ||
| 36 | |||
| 37 | <p> | ||
| 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 | </p> | ||
| 42 | |||
| 43 | <p> | ||
| 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. | ||
| 46 | </p> | ||
| 47 | |||
| 48 | <p> | ||
| 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. | ||
| 51 | </p> | ||
| 52 | </article> | ||
| 53 | |||
| 54 | <aside class="product-info-card" aria-labelledby="quick-facts-title"> | ||
| 55 | <h3 id="quick-facts-title">Quick facts</h3> | ||
| 56 | <ul> | ||
| 57 | <li>Works with the standard XWiki login flow</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> | ||
| 63 | </ul> | ||
| 64 | </aside> | ||
| 65 | </div> | ||
| 66 | </div> | ||
| 67 | </section> | ||
| 68 | |||
| 69 | <section aria-labelledby="features-title"> | ||
| 70 | <div class="container"> | ||
| 71 | <h2 id="features-title">Main capabilities</h2> | ||
| 72 | |||
| 73 | <p class="section-intro"> | ||
| 74 | A focused set of MFA/2FA features for organizations that want stronger XWiki account protection | ||
| 75 | without changing the standard login experience. | ||
| |
1.2 | 76 | </p> |
| |
1.18 | 77 | |
| 78 | <div class="product-feature-grid"> | ||
| 79 | <article class="product-feature"> | ||
| 80 | <div class="feature-icon"> | ||
| 81 | <i class="fa fa-key" aria-hidden="true"></i> | ||
| 82 | </div> | ||
| 83 | <h3>Second login step</h3> | ||
| 84 | <p> | ||
| 85 | After username and password verification, users must complete an additional verification step before accessing XWiki. | ||
| 86 | </p> | ||
| 87 | </article> | ||
| 88 | |||
| 89 | <article class="product-feature"> | ||
| 90 | <div class="feature-icon"> | ||
| 91 | <i class="fa fa-mobile" aria-hidden="true"></i> | ||
| 92 | </div> | ||
| 93 | <h3>Authenticator app codes</h3> | ||
| 94 | <p> | ||
| 95 | Users can verify access with TOTP codes generated by authenticator applications on mobile or desktop devices. | ||
| 96 | </p> | ||
| 97 | </article> | ||
| 98 | |||
| 99 | <article class="product-feature"> | ||
| 100 | <div class="feature-icon"> | ||
| 101 | <i class="fa fa-envelope-o" aria-hidden="true"></i> | ||
| 102 | </div> | ||
| 103 | <h3>Email verification codes</h3> | ||
| 104 | <p> | ||
| 105 | Users can receive one-time verification codes by email when an authenticator app is not available or preferred. | ||
| 106 | </p> | ||
| 107 | </article> | ||
| 108 | |||
| 109 | <article class="product-feature"> | ||
| 110 | <div class="feature-icon"> | ||
| 111 | <i class="fa fa-plus-circle" aria-hidden="true"></i> | ||
| 112 | </div> | ||
| 113 | <h3>Combined verification</h3> | ||
| 114 | <p> | ||
| 115 | The login flow can require both an authenticator app code and an email code when stricter verification is needed. | ||
| 116 | </p> | ||
| 117 | </article> | ||
| 118 | </div> | ||
| |
1.2 | 119 | </div> |
| |
1.18 | 120 | </section> |
| 121 | |||
| 122 | <section class="product-section-muted" aria-labelledby="security-title"> | ||
| 123 | <div class="container"> | ||
| 124 | <div class="product-layout"> | ||
| 125 | <article class="product-summary-card"> | ||
| 126 | <h2 id="security-title">Useful for XWiki security and NIS 2 readiness</h2> | ||
| 127 | |||
| 128 | <p> | ||
| 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. | ||
| 132 | </p> | ||
| 133 | |||
| 134 | <p> | ||
| 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. | ||
| 138 | </p> | ||
| 139 | |||
| 140 | <p> | ||
| 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. | ||
| 143 | </p> | ||
| 144 | </article> | ||
| 145 | |||
| 146 | <aside class="product-info-card" aria-labelledby="security-controls-title"> | ||
| 147 | <h3 id="security-controls-title">Useful for</h3> | ||
| 148 | <ul> | ||
| 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> | ||
| 155 | </ul> | ||
| 156 | </aside> | ||
| 157 | </div> | ||
| 158 | </div> | ||
| 159 | </section> | ||
| 160 | |||
| 161 | <section class="cta-section" aria-labelledby="cta-title"> | ||
| 162 | <div class="container"> | ||
| 163 | <div class="cta-panel"> | ||
| 164 | <h2 id="cta-title">Interested in using this extension?</h2> | ||
| 165 | <p> | ||
| 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. | ||
| 168 | </p> | ||
| 169 | <a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Contact Agnease</a> | ||
| 170 | </div> | ||
| 171 | </div> | ||
| 172 | </section> | ||
| 173 | |||
| 174 | {{/html}} | ||
| 175 | {{/velocity}} |