Skip to Content
Version 8.6 by Agnease on 2026/05/25 12:47
Show last authors
1 {{velocity}}
2 #set ($discard = $xwiki.ssx.use('PublicWebSite.WebHome'))
3 {{html clean="false"}}
4 ## PAGE HEADER
5 <section class="hero hero-centered service-hero" aria-labelledby="hero-title">
6 <div class="container hero-inner">
7 <div class="hero-kicker">
8 <i class="fa fa-lock" aria-hidden="true"></i>
9 XWiki authentication and access control
10 </div>
11
12 <h1 id="hero-title">Secure XWiki access, authentication and permissions</h1>
13
14 <p class="lead">
15 Secure XWiki access with LDAP, Active Directory, SSO, OIDC, SAML, MFA, user synchronization,
16 group management and maintainable permission policies.
17 </p>
18
19 <div class="hero-actions">
20 <a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Discuss access control needs</a>
21 <a class="btn btn-secondary" href="#access-control-process">See the approach</a>
22 </div>
23 </div>
24 </section>
25 ## WHY ACCESS CONTROL CARDS
26 #set ($accessControlItems = [{
27 'title': 'Connect users securely',
28 'icon': 'sign-in',
29 'content': 'Integrate XWiki with your identity provider so users can access the platform with familiar credentials.',
30 'items': [
31 'LDAP and Active Directory',
32 'OIDC, SAML and SSO',
33 'MFA and authentication extensions'
34 ]
35 },{
36 'title': 'Manage groups clearly',
37 'icon': 'users',
38 'content': 'Keep user and group synchronization understandable, scalable and aligned with the way permissions are used.',
39 'items': [
40 'User synchronization',
41 'Group mapping and filtering',
42 'Large directory considerations'
43 ]
44 },{
45 'title': 'Control access safely',
46 'icon': 'key',
47 'content': 'Review and structure rights so spaces, pages and applications can be maintained without accidental exposure.',
48 'items': [
49 'Wiki and page permissions',
50 'Admin and script rights awareness',
51 'Rights model cleanup'
52 ]
53 }])
54
55 <section aria-labelledby="why-access-title">
56 <div class="container">
57 <h2 id="why-access-title">Access control is central to a reliable XWiki platform</h2>
58 <p class="section-intro">
59 XWiki often contains internal knowledge, procedures, project information, customer data, controlled documents
60 and business workflows. Authentication and permissions need to be configured carefully so users can access
61 what they need without exposing sensitive information or making administration too complex.
62 </p>
63 <div class="pathways">
64 #foreach ($entry in $accessControlItems)
65 <article class="pathway-card">
66 <div class="card-heading">
67 <div class="pathway-icon">
68 <i class="fa fa-$entry.icon" aria-hidden="true"></i>
69 </div>
70 <h3>$entry.title</h3>
71 </div>
72 <p>$entry.content</p>
73 <ul>
74 #foreach ($item in $entry.items)
75 <li>$item</li>
76 #end
77 </ul>
78 </article>
79 #end
80 </div>
81 </div>
82 </section>
83
84 ## COMMON NEEDS
85 #set ($accessNeedsItems = [{
86 'title': 'LDAP and Active Directory integration',
87 'icon': 'address-book',
88 'content': 'Configuration, troubleshooting and optimization of LDAP/AD authentication, user creation and group synchronization.'
89 },{
90 'title': 'SSO, OIDC and SAML',
91 'icon': 'sign-in',
92 'content': 'Integration with identity providers, single sign-on flows and authentication extensions used in enterprise environments.'
93 },{
94 'title': 'Multi-factor authentication',
95 'icon': 'shield',
96 'content': 'MFA setup, licensing, configuration, troubleshooting and review of authentication-related user experience.'
97 },{
98 'title': 'User and group synchronization',
99 'icon': 'users',
100 'content': 'Review of synchronization strategy, group mapping, large-directory behavior and performance implications.'
101 },{
102 'title': 'Rights model review',
103 'icon': 'key',
104 'content': 'Review and cleanup of space, page, group and application permissions to reduce confusion and access risks.'
105 },{
106 'title': 'Access-related troubleshooting',
107 'icon': 'warning',
108 'content': 'Investigation of login failures, missing users, group sync issues, unexpected permissions or denied access.'
109 }])
110
111 <section class="services" aria-labelledby="access-needs-title">
112 <div class="container">
113 <h2 id="access-needs-title">Common authentication and access control needs</h2>
114
115 <p class="section-intro">
116 Authentication and permissions often become more complex as XWiki grows. The right setup depends on your
117 identity provider, group structure, security expectations, user volume and internal administration model.
118 </p>
119
120 <div class="services-grid">
121 #foreach ($entry in $accessNeedsItems)
122 <article class="service">
123 <div class="service-icon" aria-hidden="true">
124 <i class="fa fa-$entry.icon"></i>
125 </div>
126
127 <div class="service-body">
128 <h4>$entry.title</h4>
129 <p>$entry.content</p>
130 </div>
131 </article>
132 #end
133 </div>
134 </div>
135 </section>
136
137 ## APPROACH
138 <section id="access-control-process" class="split-section" aria-labelledby="process-title">
139 <div class="container">
140 <div class="split-grid">
141 <div class="split-copy">
142 <h2 id="process-title">A practical access control approach</h2>
143
144 <p>
145 Authentication and permissions should be handled with care because small configuration mistakes can affect
146 access to the entire platform. The goal is to understand the current setup, clarify the expected access
147 model and apply changes in a controlled way.
148 </p>
149
150 <p>
151 When possible, authentication and rights changes should first be validated in a staging or temporary clone
152 of the instance, especially when directory synchronization, group mappings, SSO or custom rights logic are involved.
153 </p>
154 </div>
155
156 <ol class="process-list">
157 <li>
158 <strong>Review the current access setup</strong>
159 Authentication method, user directory, groups, synchronization behavior, rights configuration and known issues.
160 </li>
161 <li>
162 <strong>Clarify the target model</strong>
163 Expected login flow, user provisioning, group mapping, administration model and permission boundaries.
164 </li>
165 <li>
166 <strong>Validate configuration safely</strong>
167 Test authentication, synchronization and rights behavior before applying changes to production when needed.
168 </li>
169 <li>
170 <strong>Apply controlled changes</strong>
171 Update configuration, extensions, rights or group mappings with attention to rollback and administrator access.
172 </li>
173 <li>
174 <strong>Document the result</strong>
175 Provide practical notes about the final configuration, assumptions, risks and future maintenance actions.
176 </li>
177 </ol>
178 </div>
179 </div>
180 </section>
181
182 ## SPECIFIC AREAS
183 <section aria-labelledby="areas-title">
184 <div class="container">
185 <h2 id="areas-title">Specific areas we can review</h2>
186
187 <p class="section-intro">
188 Access control in XWiki is not limited to the login page. It includes the full chain from identity provider
189 to user synchronization, group membership, page permissions and application-level rules.
190 </p>
191
192 <div class="widgets">
193 <article class="widget">
194 <div class="icon" aria-hidden="true">
195 <i class="fa fa-server"></i>
196 <h4>Directory<br />configuration</h4>
197 </div>
198 <p>
199 LDAP/AD connection settings, bind users, search bases, user filters, group filters and synchronization behavior.
200 </p>
201 </article>
202
203 <article class="widget">
204 <div class="icon" aria-hidden="true">
205 <i class="fa fa-random"></i>
206 <h4>Group<br />mapping</h4>
207 </div>
208 <p>
209 Mapping external groups into XWiki groups while avoiding unnecessary complexity and performance issues.
210 </p>
211 </article>
212
213 <article class="widget">
214 <div class="icon" aria-hidden="true">
215 <i class="fa fa-lock"></i>
216 <h4>Permission<br />structure</h4>
217 </div>
218 <p>
219 Space and page rights, inheritance, administrative access, edit rights, view rights and application permissions.
220 </p>
221 </article>
222
223 <article class="widget">
224 <div class="icon" aria-hidden="true">
225 <i class="fa fa-user-secret"></i>
226 <h4>Security<br />sensitive rights</h4>
227 </div>
228 <p>
229 Review of powerful rights such as admin, programming, script and edit rights where they affect security.
230 </p>
231 </article>
232 </div>
233 </div>
234 </section>
235
236 ## IMPORTANT CONSIDERATIONS
237 <section class="services" aria-labelledby="considerations-title">
238 <div class="container">
239 <h2 id="considerations-title">Important considerations</h2>
240
241 <p class="section-intro">
242 Authentication and access control should be designed for both security and usability. A setup that is too
243 permissive creates risk, while a setup that is too complex becomes hard to operate and troubleshoot.
244 </p>
245
246 <div class="services-grid">
247 <article class="service">
248 <div class="service-icon" aria-hidden="true">
249 <i class="fa fa-tachometer"></i>
250 </div>
251 <div class="service-body">
252 <h4>Large directory performance</h4>
253 <p>
254 Large numbers of users and groups can create synchronization, login-time or permission-management challenges.
255 </p>
256 </div>
257 </article>
258
259 <article class="service">
260 <div class="service-icon" aria-hidden="true">
261 <i class="fa fa-eye"></i>
262 </div>
263 <div class="service-body">
264 <h4>Visibility of groups and users</h4>
265 <p>
266 Group display, permission screens and administration workflows should remain usable even with many directory groups.
267 </p>
268 </div>
269 </article>
270
271 <article class="service">
272 <div class="service-icon" aria-hidden="true">
273 <i class="fa fa-user-plus"></i>
274 </div>
275 <div class="service-body">
276 <h4>User provisioning strategy</h4>
277 <p>
278 Decide when users are created, how profiles are updated and how synchronization behaves after first login.
279 </p>
280 </div>
281 </article>
282
283 <article class="service">
284 <div class="service-icon" aria-hidden="true">
285 <i class="fa fa-unlock-alt"></i>
286 </div>
287 <div class="service-body">
288 <h4>Administrator access safety</h4>
289 <p>
290 Authentication changes should preserve reliable administrator access and avoid accidental lockouts.
291 </p>
292 </div>
293 </article>
294
295 <article class="service">
296 <div class="service-icon" aria-hidden="true">
297 <i class="fa fa-refresh"></i>
298 </div>
299 <div class="service-body">
300 <h4>Upgrade compatibility</h4>
301 <p>
302 Authentication extensions, configuration keys and security behavior should be reviewed during XWiki upgrades.
303 </p>
304 </div>
305 </article>
306
307 <article class="service">
308 <div class="service-icon" aria-hidden="true">
309 <i class="fa fa-file-text-o"></i>
310 </div>
311 <div class="service-body">
312 <h4>Documentation and handover</h4>
313 <p>
314 Access rules, configuration decisions and operational assumptions should be documented for future maintenance.
315 </p>
316 </div>
317 </article>
318 </div>
319 </div>
320 </section>
321
322 ## RELATED SERVICES
323 <section class="resource-strip" aria-labelledby="related-title">
324 <div class="container">
325 <h2 id="related-title">Related XWiki services</h2>
326
327 <p class="section-intro">
328 Authentication and access control often connect with maintenance, upgrades and security review.
329 </p>
330
331 <div class="resource-grid">
332 <article class="resource-card">
333 <h4>XWiki Support &amp; Maintenance</h4>
334 <p>
335 Ongoing support for production environments, including troubleshooting, maintenance planning and operational review.
336 </p>
337 <a href="$xwiki.getURL('services.xwiki-maintenance-support')">View support services</a>
338 </article>
339
340 <article class="resource-card">
341 <h4>XWiki Security Review</h4>
342 <p>
343 Security-aware review of versions, extensions, rights, scripting, authentication and upgrade exposure.
344 </p>
345 <a href="$xwiki.getURL('services.xwiki-security-review')">View security review</a>
346 </article>
347 </div>
348 </div>
349 </section>
350
351 ## CTA
352 <section class="cta-section" aria-labelledby="cta-title">
353 <div class="container">
354 <div class="cta-panel">
355 <h2 id="cta-title">Need help with XWiki authentication or permissions?</h2>
356
357 <p>
358 Send a short description of your authentication setup, identity provider, current XWiki version,
359 user/group volume and the access control issue or improvement you want to address.
360 </p>
361
362 <a class="btn btn-primary" href="$xwiki.getURL('contact.WebHome')">Discuss access control needs</a>
363 </div>
364 </div>
365 </section>
366
367 {{/html}}
368 {{/velocity}}