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 ForumsAuthenticationAuthenticationDNN AD Fix:  UPDATEDDNN AD Fix: UPDATED
Previous
 
Next
New Post
11/1/2006 3:00 PM
 
slhilbert wrote

Dennis,

 

Good point I do leave it in mixed-mode.  That wasn't my intention.  Thanks for pointing that out.

 

Stuart

I would say that there is a difference between "pure" AD integration mode, and "not-so-pure" integrated mode.  If you uncomment the authentication line in the web.config, but leave it using "forms" authentication, then in "theory" you are in mixed mode, but everyone (including the general public) would prompted to log into AD upon visiting your website.  Intranet AD users wouldn't see the prompt, but the public would.  If they hit cancel, they might be able to log in using the DNN login, but it is disconcerting to first-time visitors that they need to log in to use the website (many won't return).

I would refer to that configuration as an AD-Integrated method, even if not quite "pure", as by default everyone is prompted to log into AD first.

In a true "mixed-mode" setup, you'd want to leave that line in the web.config commented out, and then redirect local users to the windowssignin.aspx file.  This allows non-AD users to browse the website unauthenticated, but allows people to log in (by either AD or forms login method) whenever necesssary.

 

 
New Post
11/2/2006 9:16 AM
 

So, I did a completely new installation of DNN 4.3.5 on a 2003 server with IIS6 using your manual. Sadly, the results are the same. As long as forms authentication is enabled AD accounts are automatically created but the display name is empty and the groups are not synchronised. Even after applying the AD fix. When I enable windows authentication I run into exactly the same problems as before.
I had a look with SQL profiler and I can see the request:

exec <SQLaccount>.DNN_GetUserByUsername @PortalId = 0, @Username = N'<domain>\<AccountName>'

When I manually run this SQL procedure the result is an empty table. This is correct as the account is obviously not (yet) available in DNN/SQL. I hoped to see other request from DNN to SQL to create this account but it just retry's above request over and over again.

I'm a complete newbie regarding dotnet programming but is there anyway I can debug and/or manually run the request DNN is doing when opening the website? It would be great to be able to view the process to see at which step is goes wrong.

Just to be sure, has anyone DNN 4.3.5 running succesfully with only Windows Authentication enabled?

 
New Post
11/2/2006 10:00 AM
 

Without going into indepth details about the source and not knowing how much a dotNet newbie you really are I will give you a brief run down of what you will need to do to modify the source.

  1. Download DNN 4.3.x Source. 
  2. Setup Dotnetnuke like you normally would on your local computer. 
  3. Browse to DNNInstall/Solutions/DotnetNuke.All folder.
  4. Double Click DotNetNuke.All.sln
  5. Visual Studios should now open with all of the Dotnetnuke core solutions.
  6. In Visual Studios.Net modify Dotnetnukes Web.config so that

    <compilation debug="false" />

    looks like

    <compilation debug="true" />

  7. Then if you want to check the Display name open up the code view for ADSIProvider.vb in the Provider.Authentication.ADSI solution.

  8. Find the sub;

    FillUserInfo(ByVal UserEntry As DirectoryEntry, ByVal UserInfo As Authentication.UserInfo)

  9. Add this line of code between the "With Block"

    .DisplayName = CheckNullString(UserEntry.Properties(ADSI_CNAME).Value)

 

That is the basics. 

For real details take a look at the videos on DNN regarding setting up DNN for module creation.

 

Stuart


Hilbert Solutions, LLC
Owner, Hilbert Solutions, LLC
http://www.HilbertSolutions.com
A DNN Service Provider
From Module Development to DNN Upgrades, your one stop DNN Shop
 
New Post
11/3/2006 10:34 AM
 
Hello,

Thanks Mike for the 4.3.5 AD Fix, i was waiting for it for a long time. So I put it on my intranet on DNN 4.3.5 and it works good, my roles are updated, my new users are well created, but ....

But since i install your 3 dlls i got a bug on the HtmlEditorProviders, (the same one that i'm writing on) when i click on  insert image or insert smiley or create a link, i got an error

I tried on a second one dnn site and the problem is the same, if i restore the originals dlls it works fine, but with yours i got the error.

Here is the error message

Server Error in '/' Application.

Runtime Error

Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".

<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="Off"/>
</system.web>
</configuration>

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.

<!-- Web.Config Configuration File -->

<configuration>
<system.web>
<customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
</system.web>
</configuration>


Is anyone experiment the same problem ? Take a look please, the editor is used in a lot of modules, it's very anoying

Thanks in advance
 
New Post
11/3/2006 12:46 PM
 

Yah know...  Someone pointed out this morning that they couldn't insert images, and I haven't had time to trouble-shoot it yet.  So, that might make the trouble-shooting much quicker...

 

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationDNN AD Fix:  UPDATEDDNN AD Fix: UPDATED


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