Skip to Content
Last modified by Agnease on 2026/05/23 18:56
From version 6.2
edited by Agnease
on 2026/05/22 08:50
Change comment: There is no comment for this version
To version 6.7
edited by Agnease
on 2026/05/22 14:34
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -3,7 +3,7 @@
3 3  #set ($discard = $xwiki.ssx.use('products.WebHome'))
4 4  {{html clean="false"}}
5 5  
6 -<section class="hero hero-centered product-hero" aria-labelledby="product-title">
6 +<section class="hero hero-centered" aria-labelledby="hero-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>
... ... @@ -67,26 +67,32 @@
67 67   <h2 id="features-title">Main capabilities</h2>
68 68  
69 69   <p class="section-intro">
70 - A focused set of MFA/2FA features for organizations that want stronger XWiki account protection
71 - without changing the standard login experience.
70 + A focused set of MFA/2FA features for stronger XWiki account protection without changing the standard login experience.
72 72   </p>
73 73  
74 74   <div class="product-feature-grid">
75 75   <article class="product-feature">
76 - <div class="feature-icon">
77 - <i class="fa fa-key" aria-hidden="true"></i>
75 + <div class="feature-heading">
76 + <div class="feature-icon">
77 + <i class="fa fa-key" aria-hidden="true"></i>
78 + </div>
79 + <h3>Second verification step</h3>
78 78   </div>
79 - <h3>Second login step</h3>
81 +
80 80   <p>
81 - After username and password verification, users must complete an additional verification step before accessing XWiki.
83 + After username and password verification, users complete an additional step before accessing XWiki.
84 + The flow can require one verification method or both app and email codes.
82 82   </p>
83 83   </article>
84 84  
85 85   <article class="product-feature">
86 - <div class="feature-icon">
87 - <i class="fa fa-mobile" aria-hidden="true"></i>
89 + <div class="feature-heading">
90 + <div class="feature-icon">
91 + <i class="fa fa-mobile" aria-hidden="true"></i>
92 + </div>
93 + <h3>Authenticator app codes</h3>
88 88   </div>
89 - <h3>Authenticator app codes</h3>
95 +
90 90   <p>
91 91   Users can verify access with TOTP codes generated by authenticator applications on mobile or desktop devices.
92 92   </p>
... ... @@ -93,24 +93,17 @@
93 93   </article>
94 94  
95 95   <article class="product-feature">
96 - <div class="feature-icon">
97 - <i class="fa fa-envelope-o" aria-hidden="true"></i>
102 + <div class="feature-heading">
103 + <div class="feature-icon">
104 + <i class="fa fa-envelope-o" aria-hidden="true"></i>
105 + </div>
106 + <h3>Email verification codes</h3>
98 98   </div>
99 - <h3>Email verification codes</h3>
108 +
100 100   <p>
101 101   Users can receive one-time verification codes by email when an authenticator app is not available or preferred.
102 102   </p>
103 103   </article>
104 -
105 - <article class="product-feature">
106 - <div class="feature-icon">
107 - <i class="fa fa-plus-circle" aria-hidden="true"></i>
108 - </div>
109 - <h3>Combined verification</h3>
110 - <p>
111 - The login flow can require both an authenticator app code and an email code when stricter verification is needed.
112 - </p>
113 - </article>
114 114   </div>
115 115   </div>
116 116  </section>