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 ForumsAuthenticationAuthenticationAD Authentication and child portalAD Authentication and child portal
Previous
 
Next
New Post
10/16/2007 1:47 PM
 

I have no problem getting the AD authentication to work if I browse to the windowssignon.aspx file but, I really want automatic authentication and constrained to select child portals only. I have DNN installed in our Intranet. The parent site is anonymous to the organization (WAN).  The child site should be AD authenticated automatically to the facility (LAN).  Is this possible?

I have configured the child site to use authentication with AD and set the config file appropriately but it doesn't just log me in nor can I do it manually. Also, navigating to windowssignon.aspx does tell the application which portal you're signing into and it authenticates me to the parent site..

 
New Post
10/16/2007 3:55 PM
 

I'll have to hunt back through the posts (and test it myself this evening) but I think all you have to do is copy windowssignin.aspx to the child portal folder that's been created in the root of your DNN install.

 
New Post
10/16/2007 4:13 PM
 

I've tried that. No luck but I'll give it another shot.

I am under the impression that once you finish moving the provider from the core all these authentication problems will go away. Am I understanding your posts correctly?  It seems to me that both the DNN and AD should be completely seperate and have their own specific web config keys. That would be a true mixed mode setup correct? This is what I need. The ability to use one and/or the other as I may login with the default admin account for editing so I can use my windows account for viewing purposes only.

 
New Post
10/16/2007 6:00 PM
 

Sure it's my hope that it happens but I'll never guarantee that all the authentication problems will go away and it's never been my intention to convey that. What I've meant in my posts is that now that the AD provider is separate from the Core DNN code it'll me much easier to fix bugs and implement features. Previously any changes done to the AD code would have required a new release of DNN. Now I can fix bugs and/or add features, package it up, and submit it to the Release Tracker. I'm not depend on when the next core release is going to be and they don't have to wait for me to make changes before they can do a release.

I'm not sure what you mean by specific web.config keys. The AD Provider uses a specific key and it only affects autologin. If you want the choice of how users login (mixed-mode) then you just need to comment out <add name="Authentication..... /> under httpModules in your web.config.

 
New Post
10/16/2007 10:57 PM
 

mikeh wrote

I'll have to hunt back through the posts (and test it myself this evening) but I think all you have to do is copy windowssignin.aspx to the child portal folder that's been created in the root of your DNN install.

Yup, it doesn't work. I've got an idea on how to fix it though but have to do some testing first.

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationAD Authentication and child portalAD Authentication and child portal


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