WIP attempt to do non anonymous ldap connect #908
Inga granskare
Etiketter
Inga etiketter
A: API
A: Backend
A: Federation
A: Front-End
A: I18N
A: Meta
A: Security
Build
C: Bug
C: Discussion
C: Enhancement
C: Feature
Compatibility
Dependency
Design
Documentation
Good first issue
Help welcome
Mobile
Rendering
S: Blocked
S: Duplicate
S: Incomplete
S: Instance specific
S: Invalid
S: Needs Voting/Discussion
S: Ready for review
Suggestion
S: Voted on Loomio
S: Wontfix
Ingen milstolpe
Inget projekt
Inga tilldelade
2 Deltagare
Notiser
Förfallodatum
Inget förfallodatum satt.
Beroenden
No dependencies set.
Reference: Plume/Plume#908
Laddar…
Lägg till tabell
Hänvisa till i nytt ärende
No description provided.
Delete branch "ldap-non-anon"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
attempt at fixing #902
@pwFoo could you test if it works for you?
I have to finish some other tasks and need to learn how to compile project based on a pull request first...
If you know how to compile from sources, you can run
git checkout ldap-non-anon
before running cargo commands. You might need to rungit fetch
before git checkout if it does not find the branchFirst a binddn is connected and than in a second step verify the real user.
Build is done, how to configure the additional LDAP parameters for bind?
it's
LDAP_USER
andLDAP_PASSWORD
, as environment variables or in .envLogin works, but I think need some improvements.
I see the ldap query and can compare it with a working one. Looks like your implementation do two bindings instead of one?
plume ldap
Working application
ToDo
1. Rename bind user ENV
2. That part should be removed! Second bind!
3. search filter
Binded user need to search for the "real" user. And the search filter need to be configurable like that filter part
LDAP_FILTER example. search attribute is given by
(uid=%u)
part and%u
is replaced by the login user name.Configurable search base and search filter would be most flexible I think?
Hi @trinity-1686a,
what do you think about the suggested changes?
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.