| Eric Clutario wrote
Thanks for the reply, Mike
I had it working already and looks like it wasn't AD provider problem after all. Setting the scope of my AD groups to Universal did the trick. I wonder if Al who first reported this AD forest sync problem had his problem sorted out already. Al?
Eric
|
Eric,
sorry a long time has passed, but finally I could manage to get the latest beta work in the AD forest I deal with.
I already had universal groups, so didn't need to do changes there. I actually had only to... configure things the right way 
What I did was just to setup impersonation in web.config (RTFM!), using a user that has permissions to talk to all domains in the forest:
<identity impersonate="true" userName="mydomain\myuser" password="pwd" />
That is I just had to check permissions in AD, and logging-on to the right domain when accessing the Windows pc: whatever user in whatever domain I have in the forest, this way I can successfully logon to my DNN host, which is now running (PERFECTLY) with latest AD provider 1.0.4.
More: I can even login using users from an external, trusted, domain! Once users from this domain are given rights to see the portal (put in the right AD groups), they also can logon to DNN. Even if the trusted domain is not visible in DNN, under authentication configuration (there I only see domains in the forest).
Great job Mike 