mirror of
https://github.com/abbas-gheydi/radotp.git
synced 2026-04-26 11:35:51 +03:00
[GH-ISSUE #22] Help with sAMAccountName #16
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#16
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 @Zamana on GitHub (Sep 19, 2025).
Original GitHub issue: https://github.com/abbas-gheydi/radotp/issues/22
Hi!
We enabled
ForceSearchForSamAccountName = truebecause our users log in our VPN with "user.name" and not "user.name@company.com".Unfortunately this is not working. We always receive Access-Reject at the active directory stage.
The only way to make radotp works is by using
ForceSearchForSamAccountName = false, but this implies that our users need to login by using "user.name@company.com" as username, what we don't want.Is it possible to identify the cause of this issue? Is there a "debug" mode that we can use?
Thanks.
Regards.
@abbas-gheydi commented on GitHub (Sep 20, 2025):
Hi there,
radotp can automatically handle three types of username formats:
· user
· user@domain
· domain\user
This is a default feature and doesn't need any configuration to enable it.
Have you tried it with the default settings?
@Zamana commented on GitHub (Sep 22, 2025):
Hi!
Thanks for replying.
I guess, yes, we are using pretty much the default configuration. But it would be nice if you could validate it for us:
Thanks.
Regards.
@abbas-gheydi commented on GitHub (Sep 22, 2025):
Are you using Microsoft Active Directory or a different LDAP server?
@Zamana commented on GitHub (Sep 22, 2025):
We are using Microsoft Active Directory, and our VPN/Firewall server is Hillstone (if that matters).
@abbas-gheydi commented on GitHub (Sep 22, 2025):
Could you please try this configuration: set
EnableMessageAuthenticator = True
@Zamana commented on GitHub (Sep 22, 2025):
Sure.
With:
here are the results:
@abbas-gheydi commented on GitHub (Sep 22, 2025):
I wanted to clarify that the ForceSearchForSamAccountName setting was added to fix issue #9 . To help us debug further, I'll be adding a debugging mode option and will let you know as soon as it's ready.
@zamana-7comm commented on GitHub (Oct 24, 2025):
Hi!
Any news on this?
Thanks.