Products

Solutions

Resources

Partners

Community

Blog

About

QA

Ideas Test

New Community Website

Ordinarily, you'd be at the right spot, but we've recently launched a brand new community website... For the community, by the community.

Yay... Take Me to the Community!

Welcome to the DNN Community Forums, your preferred source of online community support for all things related to DNN.
In order to participate you must be a registered DNNizen

HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationPlease Help! AD Auto Authentication AD Provider 01.00.04 BetaPlease Help! AD Auto Authentication AD Provider 01.00.04 Beta
Previous
 
Next
New Post
7/2/2008 3:54 AM
 

Mike,

Sorry, i forgot the impersonation question. Yes, we use impersonation on our standard .NET web applications, we don't usually supply a user name and password though as this will authenticate all users of the site as that user i would have thought? Anyway, i am using impersonation in the web config and i have tried both with and without user details.

One thing to note, i have made the home page a link to the windowslogin.aspx page, this still does not seem to authenticate though.

 
New Post
7/2/2008 11:24 AM
 

Impersonation with a username/password as I've laid out in the User Guide just makes the application run under that user account instead of NETWORK SERVICE.

Until we can get you logging in manually don't bother with trying to get the automatic (link to WindowsSignin.aspx) working. Both use the same code to talk to the AD so if one doesn't work the other won't either.

Two things you can try now:
1. Try logging in with a variety of users now that we know the provider is setup correctly. I've seen posts on the forum where for one reason or another a particular user account won't work period (though I've never seen if anyone got that fixed or not).
2. Take a look at LDAPBrowser. If it can't pull the necessary inf0rmation in from the AD to the server then we'll know the problem is somewhere in the network infrastructure and can take the steps to rectify the problem.

 
New Post
7/2/2008 12:57 PM
 

Mike,

I changed the web config impersonation as above, i changed the home page from being a link to the WindowsSignin.aspx, i have tried to login various users with the LDAPBrowser software and had no issues.

SUCCESS! I have just run IISRESET from the command prompt and asked a domain user to login and they get their user name next to a logout link, and their details added to the database in the users table.

It still does not work for me though, is that because it's running on my XP workstation? i have tried logging in from other machines and it still does not work. If it's because i'm using my machine as a server, then it's not really an issue and i won't worry about it, although, it will be difficult to develop personalised modules(user's links etc) and test them locally. If you can fix this, great, if not, no worries.

All i really need to do now then is remove the logout/user name via skinning and i can provide my customer with personalisation from AD as required.

 
New Post
7/2/2008 1:54 PM
 

Okay, now that your clients can manually login, they should also be able to automatically login or follow a link to WindowsSignin.aspx.

It should work just fine from an install on XP/Vista/etc. That's what I do all my development on. Is your workstation part of the domain as well? Or perhaps they've got some restrictions on what will run on a workstation (ie: at work I can run my DNN dev system but group policy prevents any other computers/users from connecting to my dev website).

 
New Post
7/2/2008 3:23 PM
 

Mike,

I should have clarified my last post a little. Users are logging in automatically by browsing to the DNN installation on my XP dev machine from their own machines,. which is what i wanted. The only issue remaining is why it does not automatically log me in when i browse locally on my dev machine, or, when i login to another machine on the doamin and browse the site from there.

I am planning on setting this up on our dev server tomorrow, it's going to be what we deploy on anyway as it's a w2k3 server , so it will be a good test. If my domain users and i can login to that, then it must be something to do with my installation? I'll let you know how i get on. In the mean time, if you have any other suggestions for my dev problem, please let me know.

Thank you very much for your constant support of this issue, it is very much appreciated.

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationPlease Help! AD Auto Authentication AD Provider 01.00.04 BetaPlease Help! AD Auto Authentication AD Provider 01.00.04 Beta


These Forums are dedicated to discussion of DNN Platform and Evoq Solutions.

For the benefit of the community and to protect the integrity of the ecosystem, please observe the following posting guidelines:

  1. No Advertising. This includes promotion of commercial and non-commercial products or services which are not directly related to DNN.
  2. No vendor trolling / poaching. If someone posts about a vendor issue, allow the vendor or other customers to respond. Any post that looks like trolling / poaching will be removed.
  3. Discussion or promotion of DNN Platform product releases under a different brand name are strictly prohibited.
  4. No Flaming or Trolling.
  5. No Profanity, Racism, or Prejudice.
  6. Site Moderators have the final word on approving / removing a thread or post or comment.
  7. English language posting only, please.
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out
What is Liquid Content?
Find Out