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

HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Active Directory problem - users not created...Active Directory problem - users not created...
Previous
 
Next
New Post
10/2/2006 4:14 AM
 
The scenario is of a DNN intranet portal requiring auto-login by AD.

The problem is that when I manage to set-up the autologin, the users are not created when they login...

The set-up is as follows

On the windows authentication section of the admin menu:
Windows  authentication - yes
Sync role - yes
Provider - ADSIAuthProvider
Auth type - Delegation
Root domain - dc=domainname
User name - user
pass - pass
e-mail domain - @domain.com
(all ok, when I press update this appears)
Accessing Global Catalog:
OK
Checking Root Domain:
OK
Accessing LDAP:
OK
Find all domains in network:
1 Domain(s):
telecorp (DOMAIN)

so it must be OK

On the web.config I have:
configSections section:
<section name="authentication" requirePermission="false" type="DotNetNuke.Framework.Providers.ProviderConfigurationHandler, DotNetNuke" />

authentication section:
    <identity impersonate="true"/>
    <authentication mode="Windows">

That is Ok and checked throughtfully on this and other forums..

And, on the IIS configuration, I have:

On the site configuration, on the Directory security tab, on the authentication and access control configuration:
Enable anonymous access - disabled
Integrated Windows Authentication - enabled

That is ok and it works if it has the user set-up onto the dotnetnuke database, when it should be like the following: When a user of the domain opens the website it MUST be created onto the application as a "basic user" of the portal.

That is not happening and I can't go asking the domain user's their private passwords and, more on, the passwords change... but the more important thing is that some of them are bosses (sor of things that happen on companies...) and can't change the authentication by now as everything is set-up with this security schema (content access, reporting services security configuration, etc...)

Any help on why the users are not being created would be great...
Thanks a lot!!




 
New Post
10/2/2006 7:47 AM
 
This is the error that gives to a domain user which has not been created on the dotnetnuke module:
that is, if the user is not created on the dnn database... if he has everything, including its domain password, it works fine!
maybe this gives us clues...

Server Error in '/' Application.

Value cannot be null.
Parameter name: value

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.ArgumentNullException: Value cannot be null.
Parameter name: value

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.

Stack Trace:

[ArgumentNullException: Value cannot be null.
Parameter name: value]
System.Web.Caching.CacheEntry..ctor(String key, Object value, CacheDependency dependency, CacheItemRemovedCallback onRemovedHandler, DateTime utcAbsoluteExpiration, TimeSpan slidingExpiration, CacheItemPriority priority, Boolean isPublic) +3503375
System.Web.Caching.CacheInternal.DoInsert(Boolean isPublic, String key, Object value, CacheDependency dependencies, DateTime utcAbsoluteExpiration, TimeSpan slidingExpiration, CacheItemPriority priority, CacheItemRemovedCallback onRemoveCallback, Boolean replace) +88
System.Web.Caching.Cache.Insert(String key, Object value, CacheDependency dependencies, DateTime absoluteExpiration, TimeSpan slidingExpiration) +79
DotNetNuke.Services.Cache.FileBasedCachingProvider.FBCachingProvider.Insert(String CacheKey, Object objObject, CacheDependency objDependency, DateTime AbsoluteExpiration, TimeSpan SlidingExpiration, Boolean PersistAppRestart) +219
DotNetNuke.Common.Utilities.DataCache.SetCache(String CacheKey, Object objObject, TimeSpan SlidingExpiration, Boolean PersistAppRestart) +72
DotNetNuke.Common.Utilities.DataCache.SetCache(String CacheKey, Object objObject, TimeSpan SlidingExpiration) +36
DotNetNuke.HttpModules.DNNMembershipModule.OnAuthenticateRequest(Object s, EventArgs e) +1040
System.Web.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +92



System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +64


Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.42

 
New Post
10/3/2006 3:54 AM
 
I see there's no response on the issue... couldn't be that nobody has found what is happening or this hasn't happened to anybody?

I can't trace it as this looks like an internal issue and I don't know of it and of the internal dll's of DNN...

well, the only response I have for this is leave all the effort put on the configuration of the Unified Login through the Active Directory and doing it by code as needed.

The problem is that the intranet I'm developing interfaces with Reporting Services and was laying on the Domain security by mapping the users to the reporting services
server roles...

Any help could be much appreciated.

thanks..
 
Previous
 
Next
HomeHomeUsing DNN Platf...Using DNN Platf...Administration ...Administration ...Active Directory problem - users not created...Active Directory problem - users not created...


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