Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ldap - setRecursive #10110

Closed
hyperman1 opened this issue Jun 19, 2020 · 2 comments · Fixed by #13038
Closed

ldap - setRecursive #10110

hyperman1 opened this issue Jun 19, 2020 · 2 comments · Fixed by #13038
Labels
area/security kind/enhancement New feature or request
Milestone

Comments

@hyperman1
Copy link

Description
As described in the chat:
I'm trying to use quarkus LDAP integration withactive directory, and I'm running in some snags:

I started with https://quarkus.io/guides/security-ldap

REMARK 1:
io.quarkus.elytron.security.ldap.LdapRecorder:createRealm seems to have no configuration option to call setRecursive(true)
Hence quarkus requires all users in LDAP to be in the same organizational unit..

This is untenable for all but the smallest organizations: If you have different buildings or even different teams, you'll organize these people in different OUs

Implementation ideas
I assume this is straightforward for someone with basic knowledge of the code base (which is not me, our corporate proxy can't even do git to external orgs, sorry) - add a config flag in application.properties which maps to setRecursive

@hyperman1 hyperman1 added the kind/enhancement New feature or request label Jun 19, 2020
@sberyozkin
Copy link
Member

From the chat: HartiMcWildfly: LdapRecorder under identityMapping() add a .searchRecursive()

@antonwiens
Copy link

@gsmet I would like to contribute this. I would also like to provide the ability to use the CachingSecurityRealm wrapper for caching the ldap results. I would make the caching (enabling it) and caching properties (maxEntries and maxAge) configurable.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/security kind/enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants