DNNCommunity / DNNCommunity/DNN.ActiveDirectory
DNN_ActiveDirectoryAuthentication can't authenticate AD account Server in different domain
- Dominant language
- Visual Basic .NET
- Stars
- 26
- Forks
- 25
- PR merge metrics
- No merged PRs in 30d
Description
DNN_ActiveDirectory IIS Server in Different Domain than AD Users and users can not authenticate
DNN_ActiveDirectoryAuthentication Extension IIS server in different domain than AD users and LDAP. I can set up DNN_ActiveDirectoryAuthentication Extension but when I try and validate the AD user in the web page it says password is invalid.
IIS Web Server in abc.xxx.com and LDAP is in def.xxx.com Both Domains have a Trust. The set up in the screen shot is successful. But the only domain in the network that shows is the Server domain abc.xxx.com.
When we try and authenticate through the webpage for an AD user in the def.xxx.com we get password is invalid.
Does the both domains need to be shown even though in the screen shot of the Site Settings everything is connection successfully.
[DNNSiteSettings.docx](https://github.com/DNNCommunity/DNN.ActiveDirectory/files/9015338/DNNSiteSettings.docx)
Contributor guide
Research direction
Start with the DNN_ActiveDirectoryAuthentication Extension and its Site Settings validation flow, using the attached DNNSiteSettings.docx as the configuration reference. Reproduce authentication with a user in def.xxx.com while the IIS server is in abc.xxx.com and the domains have a trust. Done means the cross-domain AD account authenticates successfully or the failure is documented with a clear configuration requirement.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- visualbasic
- Domain
- authentication, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100