Unable to authenticate if LDAP Signing is enforced
- Dominant language
- Python
- Stars
- 137
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
# 🐛 Summary #
If LDAP Signing is enforced the tool can't bind as it uses only LDAP over 389.
## To reproduce ##
Steps to reproduce the behavior:
Enable LDAP Signing as per Microsoft documentation: https://learn.microsoft.com/en-us/troubleshoot/windows-server/active-directory/enable-ldap-signing-in-windows-server
Try and run the application.
## Expected behavior ##
SnafflePy by @robert-todora
Beginning the snaffle...
[!!!] Unable to bind to ldap://10.10.1.100:389 - cleartext
[!!!] Connection is not established
Contributor guide
No contributing guide indexed for this repository
Research direction
No source files or tests are identified in the issue. Start by tracing the LDAP connection and bind setup, then reproduce the failure with LDAP Signing enforced. Done means the application can establish an authenticated LDAP connection when signing is required.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- authentication, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100