goauthentik / goauthentik/authentik

Restrict user visibility/searchability in LDAP Outpost

Open
#14,082 5 comments 8 reactions 0 assignees View on GitHub
enhancement enhancement/confirmed
Dominant language
Python
Stars
25.6k
Forks
2k
Avg merge
1d 2h
Merged PRs (30d)
651

Description

Hi Authentik team 👋

Thanks for your great work on Authentik — it's been working really well for me so far!

I have a question (or maybe a feature request) regarding the LDAP Outpost. I'd like to know if it's currently possible to restrict the set of users that the LDAP Outpost exposes or makes searchable to LDAP clients.

More concretely, I'm looking to:
- Limit the visibility of users returned via LDAP searches to only a specific subset, such as those in a specific group or with a certain attribute set.
- Prevent all users in Authentik from being visible to any client that binds to the LDAP Outpost — only the filtered set should be visible/searchable.

I've looked through the documentation and UI, and while I see how we can filter users by group for authentication via LDAP, it's not clear whether those same filters apply to search results or user enumeration.

Is this currently possible with some config option, or would this require a feature request?

Thanks again — happy to provide more details if needed!

Contributor guide

Open the contributing guide

Research direction

Start by reviewing the LDAP Outpost's existing group filters and the documentation and UI paths mentioned in the report. Verify whether those filters affect LDAP search results and user enumeration; done means documenting the current behavior or defining configuration for restricting visibility to a selected group or attribute set.

Written by the indexing model from the issue text.

Assessment

Tech stack
python
Domain
authentication, authorization, security
Issue type
Feature
Difficulty
4/5
Estimated time
3-5 days
Activity status
Active
Clarity
Needs clarification
Newbie friendliness
42/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.