DotNetNuke

Re: Update TTT.Authentication module with core Authentication

rfreese — Thu, 16 Feb 2006 17:31:42 GMT

I have noticed that it helped if I restarted IIS after step 10 (the SQL hack on the module settings, "10. Open ModuleSettings table change the value of ProviderTypeName from DotNetNuke.Authentication.ADSIProvider, DotNetNuke.Authentication.ADSIProvider
into DotNetNuke.Security.Authentication.ADSIProvider, DotNetNuke.Authentication.ADSIProvider"). Before I did a restart, I was getting "the default authentication provider specified in web.config is not configured properly," and after the reset I was able to set up the Admin/Authentication page. Makes sense to restart it at that point, in hindsight. It's too soon to change web.config, so the application has no reason to reinitialize yet.

Another step I missed (found this idea on the message boards) is to purge the deleted TTT pages from your recycle bin. This would be after step 3, deleting the pages
:)
and before starting the upgrade ZIP extraction at step 6. Until I got this right, I did not have an Admin/Authentication page at all. I think it's an installation bug, perhaps?

It took me several tries at the upgrade to 3.2.2 from 3.0.13 before I followed the path correctly, but it's up now. Probably just in time for the next release from the team, I bet!

One thing missing from current AD auth docs is the matrix of how to manage anonymous access to the virtual directory and to the windowssignin.aspx file. Unless you remember that it's in the zip of the last release of the module at tttcompany.com, it's a mystery, I'm sure. I got it working by disallowing anonymous access for the Dotnetnuke folder and allowing it for the windowssignin.aspx. I have to bookmark that file in order for AD to work automatically, or I can use my domain credentials at the DNN login form. (using form auth mode).

Happy computing,
Roberta

Re: Update TTT.Authentication module with core Authentication

pwbriggs23 — Fri, 27 Jan 2006 18:02:53 GMT

Ok I need some help. I am trying to upgrade from 3.2.1 to 3.2.2. I used TTT authentication module for 3.2.1 and am trying to switch to the core module. I followed all of steps and still cannot see an Authentication section under Admin. I also get: StartIndex cannot be less than zero. Parameter name: startIndex when I try to uncomment the authentication httpmodule.

Please help me resolve this issue!

Re: Update TTT.Authentication module with core Authentication

timrolands — Fri, 27 Jan 2006 14:24:50 GMT

Thank you for confirming that, Tam. Just what I need to move forward! Please keep us all posted on this support-for-nested-groups feature!

Tim

Re: Update TTT.Authentication module with core Authentication

tamttt — Fri, 27 Jan 2006 05:20:13 GMT

The current version of this module doesn't support nested groups.

I have this concept in mind, but there are something I'm considering & investigating before implement it in future version

1. Performance
2. DNN doesn't support nested groups, what is the best method to apply synchronize for these 2 different structures of group/role membership

Tam

Re: Update TTT.Authentication module with core Authentication

timrolands — Thu, 26 Jan 2006 21:47:32 GMT

I believe I have determined that the role synchronization only works with groups that a user account has direct membership in. For example, let's say my user account is in the "Developers" group (global security) in the AD, but since we have two different domains, there is also a "Developers-U" group (universal) which holds the Developers group from each domain. Then that universal group is a member of what we call a resource group: "WebPortal-R" (domain local security). If I enter that resource group into the DNN site, my account's membership is never recognized. However, if I enter the original "Developers" group, then that gets picked up.

So, it looks like nested groups of different types don't track properly, or nested groups as a whole do not work.

Any thoughts?

Re: Update TTT.Authentication module with core Authentication

timrolands — Thu, 26 Jan 2006 17:59:39 GMT

Any takers on this?

Now it will not synchronize the group membership at all. In experimenting, I switched the groups from being public to private and back again. Now it's not picking up the group memberships at all.

Tim

Re: Update TTT.Authentication module with core Authentication

timrolands — Wed, 25 Jan 2006 21:17:18 GMT

I am starting with a fresh install of DNN 3.2.2 with no previous installs of the TTT modules involved, and I am seeing an issue with the group synchronization. If I add the groups as security roles in DNN and mark them as public, the synchronization works perfectly. However, that also means people can subscribe to groups that they should not have access to. If I make those roles private in DNN, then the AD groups do not synchronize: that is, those .

Anyone else run into this? Anyone know of a fix/workaround?

Re: Update TTT.Authentication module with core Authentication

wetech — Wed, 18 Jan 2006 19:35:47 GMT

Dan,

Thanks but I had removed the Authentication Form and performed the upgrade again, as per instructions in the forum from Tam . It may very well have been in the original form, but it was removed. I may be able to get it back from the undelete. I'll try that.

Any other thoughts?

Thanks,

Gerry

Re: Update TTT.Authentication module with core Authentication

DanBall — Wed, 18 Jan 2006 14:19:25 GMT

This sounds like the same problem I had when I upgraded. In the old Authentication Module, you had to create a page called "Authentication" as part of the setup procedure. I had forgotten about that page when I upgraded but finally stumbled across it accidently. The page appears correctly in any new portals I create, but my main one has it in an alternate location.

Short story: You probably have an Authentication page, it's just not under the Admin menu. Look around your system and find out where it is. Mine was a "hidden" page, so I only found it when I looked in Admin->Pages menu.

Re: Update TTT.Authentication module with core Authentication

wetech — Wed, 18 Jan 2006 11:58:07 GMT

Yes I have followed those, but never got an Authentication form under Admin to work with. I also posted in that forum my issue. Is there a part of that process that is supposed to bring back the Authentication page under Admin, and has it been done successfully done on an already upgraded system, not a system rolled back to a previous version. My system is stuck having to stay in 3.2.2. I cannot roll back to a previous version with a backup as many things have changed. My users that had previously logged into the system under your older modules were still able to login. Maybe this is due to cookie or something. I had no errors when performing upgrade that I could see and I only found out I had a problem when a new user tried to be added to the Intranet. The new user was not automatically added to the system and had no permissions to the area there were trying to get to, which resulted in a call to me to fix the problem. Any thoughts as to what I can try to get back to a stable version...?

Gerry

Re: Update TTT.Authentication module with core Authentication

tamttt — Wed, 18 Jan 2006 09:24:40 GMT

Gerry

Have you followed all steps of the instruction I posted here

http://www.dotnetnuke.com/Community/Blogs/tabid/825/EntryID/234/Default.aspx

Re: Update TTT.Authentication module with core Authentication

wetech — Tue, 17 Jan 2006 16:14:30 GMT

Tam,

If someone has already done the 3.2.2 upgrade and cannot go back to earlier version is there a way to get the AD Authentication to properly work under 3.2.2. I am in this exact situation. I have tried removing all of your former modules etc and recopy over the 3.2.2 upgrade, but still do not get the Authentication form under the Admin section, nor does the Authentication work. This is on an intranet, and therefore crucial to getting it back up & running. I guess anyone who had previously logged into the intranet was not affected, but any new people are.

Thanks in Advance for you help,

Gerry

Re: Update TTT.Authentication module with core Authentication

DanBall — Sun, 13 Nov 2005 03:51:50 GMT

Quoting a post from another thread...

Yay! After several more hours of investigation, I think I finally have an answer as to why I don't have the Authentication option in the Admin menu.

It goes back to the documentation for the 3.0.13 Authentication Module where it says:

Add Authentication Module

Create a new page name Authentication

Add Authentication Amin module to this new page

Access this module, change and save Authentication settings for your portal

I had a page called Authentication, which was a hidden page. The upgrade installed the authentication module to this page instead of creating a new page under the Admin menu. I was unable to move it to where it is supposed to be, but at least it is working, and I don't have to restore the entire website to a pre-v4.0 state...

Re: Update TTT.Authentication module with core Authentication

DanBall — Sat, 12 Nov 2005 02:12:07 GMT

I've redone this system many times over the last many-many hours, I've upgraded to both 3.2 and 4.0 several times each. No matter what I do, I do NOT get an another option under the Admin menu called Authentication. I've went through the procedures in this thread, doing each one "exactly" as listed, no success. What am I doing wrong?

Re: Update TTT.Authentication module with core Authentication

kmotte — Fri, 11 Nov 2005 05:14:11 GMT

I tried all the steps above on a server running Win2K, net framework 1.1 with the latest updates I get the following error when attempting to set up Windows Auth. using the Admin Authentication form. The error pop up as soon as I click update on the form.

Error: Windows Authentication is currently unavailable.
DotNetNuke.Services.Exceptions.ModuleLoadException: Object reference not set to an instance of an object. ---> System.NullReferenceException: Object reference not set to an instance of an object. at DotNetNuke.Security.Authentication.ADSI.Utilities.AddADSIPath(String Path, Path ADSIPath) at DotNetNuke.Security.Authentication.ADSI.Utilities.GetRootEntry(Path ADSIPath) at DotNetNuke.Security.Authentication.ADSI.Utilities.GetRootEntry() at DotNetNuke.Security.Authentication.ADSIProvider.GetNetworkStatus() at DotNetNuke.Modules.Authentication.AuthenticationSettings.cmdAuthenticationUpdate_Click(Object sender, EventArgs e) --- End of inner exception stack trace ---

Help