Skip to Content
Last modified by Agnease on 2026/05/25 12:52
From version 8.7
edited by Agnease
on 2026/05/25 12:49
Change comment: There is no comment for this version
To version 8.10
edited by Agnease
on 2026/05/25 12:52
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -8,14 +8,11 @@
8 8   <i class="fa fa-lock" aria-hidden="true"></i>
9 9   XWiki authentication and access control
10 10   </div>
11 -
12 12   <h1 id="hero-title">Secure XWiki access, authentication and permissions</h1>
13 -
14 14   <p class="lead">
15 15   Secure XWiki access with LDAP, Active Directory, SSO, OIDC, SAML, MFA, user synchronization,
16 16   group management and maintainable permission policies.
17 17   </p>
18 -
19 19   <div class="hero-actions">
20 20   <a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Discuss access control needs</a>
21 21   <a class="btn btn-secondary" href="#access-control-process">See the approach</a>
... ... @@ -111,12 +111,10 @@
111 111   <section class="services" aria-labelledby="access-needs-title">
112 112   <div class="container">
113 113   <h2 id="access-needs-title">Common authentication and access control needs</h2>
114 -
115 115   <p class="section-intro">
116 116   Authentication and permissions often become more complex as XWiki grows. The right setup depends on your
117 117   identity provider, group structure, security expectations, user volume and internal administration model.
118 118   </p>
119 -
120 120   <div class="services-grid">
121 121   #foreach ($entry in $accessNeedsItems)
122 122   <article class="service">
... ... @@ -123,7 +123,6 @@
123 123   <div class="service-icon" aria-hidden="true">
124 124   <i class="fa fa-$entry.icon"></i>
125 125   </div>
126 -
127 127   <div class="service-body">
128 128   <h4>$entry.title</h4>
129 129   <p>$entry.content</p>
... ... @@ -157,19 +157,16 @@
157 157   <div class="split-grid">
158 158   <div class="split-copy">
159 159   <h2 id="process-title">A practical access control approach</h2>
160 -
161 161   <p>
162 162   Authentication and permissions should be handled with care because small configuration mistakes can affect
163 163   access to the entire platform. The goal is to understand the current setup, clarify the expected access
164 164   model and apply changes in a controlled way.
165 165   </p>
166 -
167 167   <p>
168 168   When possible, authentication and rights changes should first be validated in a staging or temporary clone
169 169   of the instance, especially when directory synchronization, group mappings, SSO or custom rights logic are involved.
170 170   </p>
171 171   </div>
172 -
173 173   <ol class="process-list">
174 174   #foreach ($entry in $accessProcessItems)
175 175   <li>
... ... @@ -183,146 +183,108 @@
183 183   </section>
184 184  
185 185   ## SPECIFIC AREAS
177 + #set ($accessAreasItems = [{
178 + 'title': 'Directory configuration',
179 + 'icon': 'server',
180 + 'content': 'LDAP/AD connection settings, bind users, search bases, user filters, group filters and synchronization behavior.'
181 + },{
182 + 'title': 'Group mapping',
183 + 'icon': 'random',
184 + 'content': 'Mapping external groups into XWiki groups while avoiding unnecessary complexity and performance issues.'
185 + },{
186 + 'title': 'Permission structure',
187 + 'icon': 'lock',
188 + 'content': 'Space and page rights, inheritance, administrative access, edit rights, view rights and application permissions.'
189 + },{
190 + 'title': 'Security-sensitive rights',
191 + 'icon': 'user-secret',
192 + 'content': 'Review of powerful rights such as admin, programming, script and edit rights where they affect security.'
193 + }])
194 +
186 186   <section aria-labelledby="areas-title">
187 187   <div class="container">
188 188   <h2 id="areas-title">Specific areas we can review</h2>
189 -
190 190   <p class="section-intro">
191 191   Access control in XWiki is not limited to the login page. It includes the full chain from identity provider
192 192   to user synchronization, group membership, page permissions and application-level rules.
193 193   </p>
194 -
195 195   <div class="widgets">
196 - <article class="widget">
197 - <div class="icon" aria-hidden="true">
198 - <i class="fa fa-server"></i>
199 - <h4>Directory<br />configuration</h4>
200 - </div>
201 - <p>
202 - LDAP/AD connection settings, bind users, search bases, user filters, group filters and synchronization behavior.
203 - </p>
204 - </article>
205 -
206 - <article class="widget">
207 - <div class="icon" aria-hidden="true">
208 - <i class="fa fa-random"></i>
209 - <h4>Group<br />mapping</h4>
210 - </div>
211 - <p>
212 - Mapping external groups into XWiki groups while avoiding unnecessary complexity and performance issues.
213 - </p>
214 - </article>
215 -
216 - <article class="widget">
217 - <div class="icon" aria-hidden="true">
218 - <i class="fa fa-lock"></i>
219 - <h4>Permission<br />structure</h4>
220 - </div>
221 - <p>
222 - Space and page rights, inheritance, administrative access, edit rights, view rights and application permissions.
223 - </p>
224 - </article>
225 -
226 - <article class="widget">
227 - <div class="icon" aria-hidden="true">
228 - <i class="fa fa-user-secret"></i>
229 - <h4>Security<br />sensitive rights</h4>
230 - </div>
231 - <p>
232 - Review of powerful rights such as admin, programming, script and edit rights where they affect security.
233 - </p>
234 - </article>
203 + #foreach ($entry in $accessAreasItems)
204 + <article class="widget">
205 + <div class="icon" aria-hidden="true">
206 + <i class="fa fa-$entry.icon"></i>
207 + <h4>$entry.title</h4>
208 + </div>
209 + <p>$entry.content</p>
210 + </article>
211 + #end
235 235   </div>
236 236   </div>
237 237   </section>
238 238  
239 239   ## IMPORTANT CONSIDERATIONS
217 + #set ($accessConsiderationItems = [{
218 + 'title': 'Large directory performance',
219 + 'icon': 'tachometer',
220 + 'content': 'Large numbers of users and groups can create synchronization, login-time or permission-management challenges.'
221 + },{
222 + 'title': 'Visibility of groups and users',
223 + 'icon': 'eye',
224 + 'content': 'Group display, permission screens and administration workflows should remain usable even with many directory groups.'
225 + },{
226 + 'title': 'User provisioning strategy',
227 + 'icon': 'user-plus',
228 + 'content': 'Decide when users are created, how profiles are updated and how synchronization behaves after first login.'
229 + },{
230 + 'title': 'Administrator access safety',
231 + 'icon': 'unlock-alt',
232 + 'content': 'Authentication changes should preserve reliable administrator access and avoid accidental lockouts.'
233 + },{
234 + 'title': 'Upgrade compatibility',
235 + 'icon': 'refresh',
236 + 'content': 'Authentication extensions, configuration keys and security behavior should be reviewed during XWiki upgrades.'
237 + },{
238 + 'title': 'Documentation and handover',
239 + 'icon': 'file-text-o',
240 + 'content': 'Access rules, configuration decisions and operational assumptions should be documented for future maintenance.'
241 + }])
242 +
240 240   <section class="services" aria-labelledby="considerations-title">
241 241   <div class="container">
242 242   <h2 id="considerations-title">Important considerations</h2>
243 -
244 244   <p class="section-intro">
245 245   Authentication and access control should be designed for both security and usability. A setup that is too
246 246   permissive creates risk, while a setup that is too complex becomes hard to operate and troubleshoot.
247 247   </p>
248 -
249 249   <div class="services-grid">
250 - <article class="service">
251 - <div class="service-icon" aria-hidden="true">
252 - <i class="fa fa-tachometer"></i>
253 - </div>
254 - <div class="service-body">
255 - <h4>Large directory performance</h4>
256 - <p>
257 - Large numbers of users and groups can create synchronization, login-time or permission-management challenges.
258 - </p>
259 - </div>
260 - </article>
261 -
262 - <article class="service">
263 - <div class="service-icon" aria-hidden="true">
264 - <i class="fa fa-eye"></i>
265 - </div>
266 - <div class="service-body">
267 - <h4>Visibility of groups and users</h4>
268 - <p>
269 - Group display, permission screens and administration workflows should remain usable even with many directory groups.
270 - </p>
271 - </div>
272 - </article>
273 -
274 - <article class="service">
275 - <div class="service-icon" aria-hidden="true">
276 - <i class="fa fa-user-plus"></i>
277 - </div>
278 - <div class="service-body">
279 - <h4>User provisioning strategy</h4>
280 - <p>
281 - Decide when users are created, how profiles are updated and how synchronization behaves after first login.
282 - </p>
283 - </div>
284 - </article>
285 -
286 - <article class="service">
287 - <div class="service-icon" aria-hidden="true">
288 - <i class="fa fa-unlock-alt"></i>
289 - </div>
290 - <div class="service-body">
291 - <h4>Administrator access safety</h4>
292 - <p>
293 - Authentication changes should preserve reliable administrator access and avoid accidental lockouts.
294 - </p>
295 - </div>
296 - </article>
297 -
298 - <article class="service">
299 - <div class="service-icon" aria-hidden="true">
300 - <i class="fa fa-refresh"></i>
301 - </div>
302 - <div class="service-body">
303 - <h4>Upgrade compatibility</h4>
304 - <p>
305 - Authentication extensions, configuration keys and security behavior should be reviewed during XWiki upgrades.
306 - </p>
307 - </div>
308 - </article>
309 -
310 - <article class="service">
311 - <div class="service-icon" aria-hidden="true">
312 - <i class="fa fa-file-text-o"></i>
313 - </div>
314 - <div class="service-body">
315 - <h4>Documentation and handover</h4>
316 - <p>
317 - Access rules, configuration decisions and operational assumptions should be documented for future maintenance.
318 - </p>
319 - </div>
320 - </article>
251 + #foreach ($entry in $accessConsiderationItems)
252 + <article class="service">
253 + <div class="service-icon" aria-hidden="true">
254 + <i class="fa fa-$entry.icon"></i>
255 + </div>
256 + <div class="service-body">
257 + <h4>$entry.title</h4>
258 + <p>$entry.content</p>
259 + </div>
260 + </article>
261 + #end
321 321   </div>
322 322   </div>
323 323   </section>
324 324  
325 325   ## RELATED SERVICES
267 + #set ($relatedServiceItems = [{
268 + 'title': 'XWiki Support & Maintenance',
269 + 'url': 'services.xwiki-maintenance-support',
270 + 'content': 'Ongoing support for production environments, including troubleshooting, maintenance planning and operational review.',
271 + 'linkLabel': 'View support services'
272 + },{
273 + 'title': 'XWiki Security Review',
274 + 'url': 'services.xwiki-security-review',
275 + 'content': 'Security-aware review of versions, extensions, rights, scripting, authentication and upgrade exposure.',
276 + 'linkLabel': 'View security review'
277 + }])
278 +
326 326   <section class="resource-strip" aria-labelledby="related-title">
327 327   <div class="container">
328 328   <h2 id="related-title">Related XWiki services</h2>
... ... @@ -332,21 +332,13 @@
332 332   </p>
333 333  
334 334   <div class="resource-grid">
335 - <article class="resource-card">
336 - <h4>XWiki Support &amp; Maintenance</h4>
337 - <p>
338 - Ongoing support for production environments, including troubleshooting, maintenance planning and operational review.
339 - </p>
340 - <a href="$xwiki.getURL('services.xwiki-maintenance-support')">View support services</a>
341 - </article>
342 -
343 - <article class="resource-card">
344 - <h4>XWiki Security Review</h4>
345 - <p>
346 - Security-aware review of versions, extensions, rights, scripting, authentication and upgrade exposure.
347 - </p>
348 - <a href="$xwiki.getURL('services.xwiki-security-review')">View security review</a>
349 - </article>
288 + #foreach ($entry in $relatedServiceItems)
289 + <article class="resource-card">
290 + <h4>$entry.title</h4>
291 + <p>$entry.content</p>
292 + <a href="$xwiki.getURL($entry.url)">$entry.linkLabel</a>
293 + </article>
294 + #end
350 350   </div>
351 351   </div>
352 352   </section>