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 ForumsAuthenticationAuthenticationActive Directory 01.00.03 BetaActive Directory 01.00.03 Beta
Previous
 
Next
New Post
3/24/2008 1:01 PM
 

It could be two things.

1. It sometimes takes a while especially when you're just testing it to see if it works . Try clearing your cookies and then seeing if it synchronizes. If the cookie is still active and hasn't expired then the login code is bypassed.

2. It could be in the role name itself. The role name in DNN needs to be the same as the pre-Windows 2000 AD Group name. If you look at the properties for the AD group you'll see a box that has the pre-Windows 2000 name. I suspect the problem is in the cookies as this is rarely an issue but it's one I've run across before.

 
New Post
3/25/2008 7:58 AM
 

Hi Mike,

performing a check on my DNN 4.7 and 4.8 hosts, where I installed the beta provider, I find a couple of DLL in the bin directory I'm not sure of: is it correct to have DotNetNuke.Authentication.ADSI.dll and DotNetNuke.Authentication.ADSIProvider.dll in the bin, and DotNetNuke.Authentication.ActiveDirectory.dll and Interop.ActiveDs.dll under bin\Providers ?

I'm trying to add some eventlog write in the DLL, so to "see" what's happening (cannot debug with Visual Studio Express), but never see any of my modifications running, so that I'm wondering whether some other DLL is getting loaded instead!

For example I put the following code in function  WindowsAuthorization (login.ascx.vb) or AuthenticationLogon (authenticationcontroller.vb):

            Dim _portalSettings As PortalSettings = Common.GetPortalSettings
            Dim log As New DotNetNuke.Services.Log.EventLog.EventLogController
            log.AddLog("WindowsAuthorization", loginStatus.ToString, _portalSettings, -1, Services.Log.EventLog.EventLogController.EventLogType.ADMIN)

but I never can see any eventlog entry with my data.

Also, in my web.config, I have:

under httpmodules:

      <add name="Authentication" type="DotNetNuke.Authentication.ActiveDirectory.HttpModules.AuthenticationModule, DotNetNuke.Authentication.ActiveDirectory" />

then:

<authentication defaultProvider="ADSIAuthenticationProvider">
      <providers>
        <clear />
        <add name="ADSIAuthenticationProvider" type="DotNetNuke.Authentication.ActiveDirectory.ADSI.ADSIProvider, DotNetNuke.Authentication.ActiveDirectory" providerPath="~\Providers\AuthenticationProviders\ADSIProvider\" />
      </providers>
    </authentication>

 but Providers\AuthenticationProviders directory does not exist - is this the old path?

 

 
New Post
3/25/2008 11:07 AM
 

Remove the two .dll files that aren't in the bin\providers directory (DotNetNuke.Authentication.ADSI.dll and DotNetNuke.Authentication.ADSIProvider.dll). Your web.config file looks good. I just checked it against mine and it's the same so I think it's those two old .dll files that are causing the problem.

 
New Post
3/25/2008 11:47 PM
 

Mike,

I've got it working to a certain extent.

The authenication test is now coming back successfully, I think the reason it was failing was due to the fact that I had set up an application pool through IIS for the portal. In order to be able to see the CPU usage through task manager and to differentiate it from the other sites on the server, I used the IWAM user identity.

So now the site is authenticating users but it doesn't seem to be synchronising the roles. I've ensured that all roles within the portal have corresponding roles within active directory but it doesn't seem to synchronising them with users within the Active Directory roles.

You can see the settings in the attached pic. (I removed the domain name just for security reasons prior to posting)

 

Accessing Global Catalog:
OK
Checking Root Domain:
OK
Accessing LDAP:
OK
Find all domains in network:
1 Domain(s):




 

 
New Post
3/25/2008 11:50 PM
 

Mike,

I also just discovered that I'm getting an exception thrown when trying to signin.

AssemblyVersion: 04.08.01
PortalID: 0
PortalName: FoneWeb Portal
UserID: -1
UserName:
ActiveTabID: 53
ActiveTabName: Home
RawURL: /desktopmodules/authenticationservices/activedirectory/windowssignin.aspx
AbsoluteURL: /desktopmodules/authenticationservices/activedirectory/windowssignin.aspx
AbsoluteURLReferrer:
UserAgent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; .NET CLR 2.0.50727; .NET CLR 3.0.04506.30)
DefaultDataProvider: DotNetNuke.Data.SqlDataProvider, DotNetNuke.SqlDataProvider
ExceptionGUID: c99fc231-4ee7-463a-8047-1f4a711f98f2
InnerException: Object reference not set to an instance of an object.
FileName:
FileLineNumber: 0
FileColumnNumber: 0
Method: DotNetNuke.Authentication.ActiveDirectory.ADSI.Utilities.SearchNestedGroups
StackTrace:
Message: System.NullReferenceException: Object reference not set to an instance of an object. at DotNetNuke.Authentication.ActiveDirectory.ADSI.Utilities.SearchNestedGroups(DirectoryEntry group, String DistinguishedName) at DotNetNuke.Authentication.ActiveDirectory.ADSI.ADSIProvider.IsAuthenticationMember(GroupInfo AuthenticationGroup, UserInfo AuthenticationUser) at DotNetNuke.Authentication.ActiveDirectory.UserController.AddUserRoles(Int32 PortalID, UserInfo AuthenticationUser)
Source:
Server Name: FONEWEB01

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationActive Directory 01.00.03 BetaActive Directory 01.00.03 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