mirror of
https://github.com/PegaProx/project-pegaprox.git
synced 2026-04-25 18:15:50 +03:00
[GH-ISSUE #70] LDAP Setup fails test with "invalid attribute type dn" #50
Labels
No labels
Approved
Q2-3 2026 Development
bug
documentation
enhancement
help wanted
invalid
pull-request
question
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/project-pegaprox-PegaProx#50
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
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?
Originally created by @abyss1 on GitHub (Feb 22, 2026).
Original GitHub issue: https://github.com/PegaProx/project-pegaprox/issues/70
Originally assigned to: @MrMasterbay on GitHub.
As said I use a "simple" ad setup seems like the bind works as expected but then it throws a DN error in the end failing authentication...
No I played aroudn with using various Attributes but I can not seem to find what is generating this error and can not seme to find any logging that woudl help further , it seems a PegaProx side error , but again not sure, I can not find any usable logging.
The AD works I have it tiedin to proxmox succesfully, again a reason I assuem it is an issue with the request send to the LDAP server.
I am using a Windows 2022 Server based AD Cluster
Logging from the test button :
✗ invalid attribute type dn
✓
Server connection
10.10.10.10:389
✓
Service account bind
CN=pegaprox,OU=ou1,OU=SE-Systems,DC=syseng,DC=local
✗
Connection
invalid attribute type dn
@MrMasterbay commented on GitHub (Feb 22, 2026):
Hi there @abyss1 ,
thank you for testing it!
As we tested the AD connection we used an older Active Directory as I now checked I see indeed here an bug from our side!.
Very sorry for that!
A fix will be implemented for that today!
Best regards,
Nico
@abyss1 commented on GitHub (Feb 22, 2026):
All good , that is why it is a Beta , bugs happen even in release software , thought I was loosing my mind for a bit. But then went through the motions and found it not to be a issue our side rather an interaction issue :)
Looking forward to the fix and testing further , especuially interested in the tenant workings , but for that LDAP needs to work (in our implementation in any case)
@TheLaskY commented on GitHub (Feb 24, 2026):
Up! could be great to have this feature working :)
@smccloud commented on GitHub (Feb 25, 2026):
Any idea when the fix will be released? I would love to integrate AD login, but this is a show stopper for me right now.
@mkellermann97 commented on GitHub (Feb 25, 2026):
Hi @smccloud, @abyss1, @TheLaskY,
Just a quick update – we're currently working on v0.9.0, which will be released this weekend.
Please note that this is a major overhaul, so it's taking a bit longer than a typical update.
Regards,
Marcus
@mkellermann97 commented on GitHub (Feb 27, 2026):
Hi all,
Just a quick update – the latest version should fix this.
Regards,
Marcus
@abyss1 commented on GitHub (Feb 28, 2026):
I can confirm it works now against both a Windwos 2019 and a windows 2024 based AD setup.
Thank you !