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
1/18/2007 2:02 PM
 

I can answer some right off the bat but others I'll have to look up and get back to you.

A: Email me at mike@gmss.org and I'll email the 4.3.7 fix to you.

B: Good question and one that would requre further research. It depends on how you're creating this new module I think

C: Domain users should login with Domain\Username. What error do they get when they try to log in and what does the Eventlog on the site say?

D: I believe it's still encrypted in the aspnet_Users or aspnet_Membership table.

 
New Post
1/23/2007 2:03 PM
 

Just released DNN Fix for DNN version 3.3.7.

 http://www.getyourowntots.com/Projects/DNNProjects/DNNADFix/Download/tabid/99/Default.aspx

No changes just an upgrade to latest 3.x version.

 

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
1/31/2007 6:03 PM
 

4.4.1 fix released @ http://dnn.gmss.org. No changes from 4.4.0.

 
New Post
2/19/2007 10:07 PM
 
mikeh wrote

C: Domain users should login with Domain\Username. What error do they get when they try to log in and what does the Eventlog on the site say?

D: I believe it's still encrypted in the aspnet_Users or aspnet_Membership table.

C - I thought that AD users had to navigate to ~/Admin/Security/WindowsSignOn.aspx in order to re-sign on, rather than trying to use the regular Login box. Either that or clear out your cookies, and then hitting the web site will throw you there and set yourself up anyway.

D - From what I understood, the password that is encrypted in aspnet_Membership was a randomly generated one by DotNetNuke (someone said it in one of the threads here), and that it wasn't used as the person logging in was validated against AD.

B sounds quite interesting, I'd like to see some 'OnLogin' style events that we could hook something up to somewhere... Could be useful for something instead of having to hack the code to do so.

 

Is it just my install or is there a problem deleting a domain user from dotnetnuke? I'm running DNN 4.4.1, XP, IIS 5, the usual I think. I have this 'fix' installed also, but this was happening before then. When I first hit the site, it correctly creates the user in all the required tables: aspnet_membership/users, users, userroles, etc. But when I log in as host, and try to delete that user: DOMAIN\username, it removes it from the dnn tables, but not the aspnet ones, and then says 'an error occurred deleting user' or something like that. It's odd because it seems to have deleted the dnn users, but I don't know where this error is then coming from, and whether it is supposed to delete the records from the aspnet tables too.

Excellent module all round though, kudos guys n girls :)

 

 
New Post
2/20/2007 3:25 AM
 
thanks for illustration,
 
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