mirror of
https://github.com/abbas-gheydi/radotp.git
synced 2026-04-26 19:45:55 +03:00
[GH-ISSUE #24] Help with 389 Directory Server Integration with RadOTP (Without Windows/AD LDAP) #19
Labels
No labels
pull-request
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/radotp#19
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 @sauravsahani007 on GitHub (Jan 15, 2026).
Original GitHub issue: https://github.com/abbas-gheydi/radotp/issues/24
As this application supports authentication using the DN format username@domain.com, which is not supported by 389 Directory Server, the integration does not work.
The 389 Directory Server supports authentication only using full DN, for example:
dn="uid=username,ou=people,dc=domain,dc=co,dc=in"
Kindly advise whether any configuration change or code modification is possible to support DN-based authentication with 389 Directory Server.
Logs for reference:
Failure:
Query sent via RadOTP Server to 389 Directory Server:
dn="username@domain.co.in" method=128 version=3
[30/Dec/2025:15:59:40.594806741 [+051800]] conn=1381462 op=0
RESULT err=49 tag=97 nentries=0
No suffix for bind dn found
Success:
Query sent directly (without RadOTP) to 389 Directory Server:
dn="uid=20269,ou=people,dc=omlogistics,dc=co,dc=in"
method=128 version=3