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
12/20/2006 1:50 PM
 
mikeh wrote

I've got the fix updated for 4.3.7 and the code working so the synching works in both mixed mode and in authentication mode but I need people who can test the package for me. Either reply here with your email or email me directly at mhorton@telus.net

Thanks

Send a copy my way... I'll test it out for ya.  Today is the last school day for the year, so I should have time to upgrade and test it out.

 
New Post
12/20/2006 2:29 PM
 
NetLipe wrote
I don’t know what you have done, but I’m using mixed mode authentication and in my case, I changed de Domain.vb in the Authentication.ADSI project.
 
The Private Sub PopulateChild as commented … some lines, because the attribute Domain.Password is now WriteOnly. So wath I found was that the error was rigth here, someone comment the code and perhaps as not tested…!!!
 
Resolution: The construtor receives the password, so i passed this password to a string in the constructor and use that strin in the Sub PopulateChild
 
Code Line: 128
If (Not Domain.Username Is Nothing) AndAlso (Not strPassword Is Nothing) Then
child = ADSI.Domain.GetDomain(entry.Path, Domain.Username, strPassword, Domain.AuthenticationType)
Else
child = ADSI.Domain.GetDomain(entry.Path)
End If

 mikeh wrote

 

I've got the fix updated for 4.3.7 and the code working so the synching works in both mixed mode and in authentication mode but I need people who can test the package for me. Either reply here with your email or email me directly at mhorton@telus.net

Thanks

NetLipe, what error are you talking about? I found that when using fixed mode the as soon as the person clicks "Login" in the signin.ascx and a the sproc that checks if the user is a valid DNN user that it blows past any chance for Authentication which means no role synchronization was done. I added an If statement to check whether Authentication was set or not and caused the code to go through the authentication procedure if it was. In stepping through the code in mixed mode I never even hit domain.vb unless it was a new user.

Dan, I'm not at my computer at the moment (working in a lab today) so I'll fire it your way either later this afternoon or this evening.

 

 
New Post
12/21/2006 5:08 AM
 

Your right! The domain.vb is only called when a new user login’s. Somehow the function GetDomain throws an exception if I don’t pass the right user and password – rights in accessing AD.

I also changed the mode as the user is “validated”. First validates in AD (check whether Authentication was set) and only after in dnn DB. But I made this change, since I don’t have the AD password saved in bd. I fill de membership password with a random password. Logically if validating first in db will return false and adds a missing attempt in db…blocking account.

 
New Post
12/28/2006 9:14 AM
 

Hi all,

I've done an upgrade to 4.3.7 and yesterday I upgraded to 4.4.0 without to much trouble. Sadly, neither of these upgrades solved the problem with the 'endless loop' when a new user connects to the webpage using only Windows authentication. I tried all of the options and configurations written in lots of different posts on this forum and even (re-)installed DNN on different servers. Currently my free time is limited and as stated earlier I'm a complete newbie regarding dotnet programming en visual studio. So, I'm even not able to do proper debugging. have to give it up for now and switch to using the so called mixed-mode solution. Hopefully some day this problem can be identified and solved.

Thanks all of you for your support!

 
New Post
1/8/2007 2:09 PM
 

I've done the fixes for DNN 4.4.0 and it can be downloaded from http://dnn.gmss.org If anyone runs into any errors please let me know ASAP. Thanks, also, to Dan and Greg for testing the fixes for DNN 4.3.7 even though it was never released (DNN 4.4.0 was released).

 

 
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