Re: Update TTT.Authentication module with core Authentication

TAM thanks for the info :) However this method leaves some old files laying around. I suggest you delete the "Authentication" folder from DesktopModules once you got it working as the last step.

Re: Update TTT.Authentication module with core Authentication

Tam could you take a look at my post here on the forum and tell me if there is a fix or work around: http://forums.asp.net/1110516/ShowPost.aspx

Re: Update TTT.Authentication module with core Authentication

This worked well... thanks Tam.

Re: Update TTT.Authentication module with core Authentication

I dont see an Admin/Authentication.. what can be the reason and how to solve it?

Re: Update TTT.Authentication module with core Authentication

I already installed DNN 3.2 for the first time in my Intranet (this is not an upgrade issue). DNN 3.2 works pretty well right now. I just realize that I can use Windows Authentication with this version (3.2). So I logged in as Admin and I click into Admin/Authentication page, I checked the checkbox and the checkbox, as well. I selected the only available provider from the Provider Listbox. The Authentication Type is . I left the root domain blank. I typed a username and password with permissions to access my Active Directory. When I clicked , I received some OKs lines, indicating that everything worked fine. What else should I do in order to use Windows Authentication? (currently, I have to continue typing username and password !!!)

Re: Update TTT.Authentication module with core Authentication

I meant, I would really appreciate a procedure to active Windows Authentication for DNN 3.2 Installations.

Re: Update TTT.Authentication module with core Authentication

I have tried all the above and have not been able to get the admin feature enabled even though I can see it. It has given the error:

The default authentication provider specified in web.config is not configured properly. Authentication settings are disabled.

I have gone through all the web.config changes and verified.

Also, in step 9 you say:
Open IIS Settings, change security setting Admin\Security\WindowsSignin.aspx depends on your Authentication type (the old DesktopModules\Authentication\Logon.aspx is changed to this file)

I'm not really sure what you mean by change security setting. Are you referring to IIS Manager and changing security or someplace else?

Thanks.

Re: Update TTT.Authentication module with core Authentication

After reloading DNN 3.2 and buliding it new I was finally able to get authentication to work from the base code version but never was able to upgrade. Once working it is just as the old version...very nice and very useful. Thanks.

Re: Update TTT.Authentication module with core Authentication

Hello spnkysy,

I strongly appreciate a procedure (or some tips) to get authentication working from DNN 3.2 in an Intranet Environment. Windows 2003 Server / Active Directory. (i.e. What should I do with the web.config file?)

Thanks in advance,

Luis

Re: Update TTT.Authentication module with core Authentication

FYI - Since I already had a tab called "Authentication", when I upgraded, the Admin dropdown never got an Authentication tab created. I had to delete the tab I originally had, and make sure it was cleared out of the recycle bin as well.

Re: Update TTT.Authentication module with core Authentication

I found an issue that has been escaping me for at least a week. This function Public Shared ReadOnly Property DefaultEmailDomain() As String
Get
Dim _portalSettings As PortalSettings = PortalController.GetCurrentPortalSettings
Dim _portalEmail As String = _portalSettings.Email
Return _portalEmail.Substring(_portalEmail.IndexOf("@"))
End Get
End Property

Has been bombing for a week and I just now realized why. This is looking at the e-mail address of the admin account to get the default e-mail domain? ARE YOU KIDDING?

Re: Update TTT.Authentication module with core Authentication

The install build for 3.2.2 does not have a Providers/AuthenticationProviders/ADSIProvider folder while this is present in the source package.

Re: Update TTT.Authentication module with core Authentication

I can add that I have duplicated the "no admin/authentication page" problem on upgrading from 3.0.13 with the TTT auth module working. The problem was that I did not purge the deleted TTT auth pages from the recycle bin prior to the upgrade. Once I had done that prior to the upgrade, the admin/authentication option was present as expected. I will try to enter this in the public area of support.dotnetnuke.com, so the install team might find out and might be able to duplicate and perhaps correct it.

I would also like to mention that step 9 says to "change" the file security in IIS for windowssignin.aspx, but does not go into what the setting should be, anonymous access yes or no or where to find docs for more detail (I think the doc file is still in the old zip at tttcompany.com).

Thanks for the AD support!

Re: Update TTT.Authentication module with core Authentication

After step 10 (the SQL patch) I recommend restarting IIS. Without it, I was getting the oft-reported configuration error ("The default authentication provider specified in web.config is not configured properly. Authentication settings are disabled.") and all authentication options were grayed out. After the restart, I could set the options.

What about setting up a clean core Windows Authentication for DNN 4.0.2?

What about setting up a clean core Windows Authentication for DNN 4.0.2? Do you know where can i find some doc for accomplish that?

Thank you.
Diego.

Windows Authentication for DNN 4.0.2?

I have the same problem of setting up DNN 4.0.2 to support windows authentication.
It would be of great help if someone could tell me how to accomplish this.

Thank you,
vamshi

Re: Update TTT.Authentication module with core Authentication

Please I need the same: Authentication in DNN 4.0.2 ... Can i use the modules TTT.Authentication.3.0.13 and TTT.Authentication.Signin.3.0.13 in DNN 4.0.2 ??

Best regards
Pavel.

Custom Authentication Provider

Can you provide a roadmap for developing a custom authentication provider? From the code I've dug into so far it 'appears' straightforward. However the significance of defining two types and whether or not a custom provider would need to enable 'Windows Authentication' escapes me so far. Also, why is there a checkbox for Windows Authentication if it's required to use the ADSI provider? Hosting situations? So where is the checkbox that says - use a custom provider vs the built in DNN authentication?
Thanks for any guidance you can give.
Toby

Re: Update TTT.Authentication module with core Authentication

I have been looking for directions on how to setup AD authentication on a 4.0.2 clean install and have not been able to find one. Is there one available? and if so could someone point me to the location for this documentation.

Re: Update TTT.Authentication module with core Authentication

Has anybody managed to setup AD on 4.0.2 yet? There does not seem to be much info on this. It would be nice to have an idiots guide on how to setup the server and DNN 4.0.2 for AD

Re: Update TTT.Authentication module with core Authentication

At risk of piling on / a "me too" post, I'm looking for any updates and info about 4.0.2 + AD.

Re: Update TTT.Authentication module with core Authentication

4.0.2 setup info and administration would be most helpful. Thanks!

Re: Update TTT.Authentication module with core Authentication

Also looking for 4.0.2 setup info...

Re: Update TTT.Authentication module with core Authentication

Hi,

I am trying to use AD with DNN 3.2.2
Are there any document which explains these steps in detail and mentions about problems developers might encounter?

For example I suppose step 9 is still not clear?

Re: Update TTT.Authentication module with core Authentication

Recently I've seen release DotNetNuke 4.0.3 ... There have been changes in The Active Directory Project ? Exists an official documentation (install, setting, bugs, etc.) for this Project ? Because exists many information but is disorganized. It's very important for me. Thanks.

Re: Update TTT.Authentication module with core Authentication

Recently I've seen release DotNetNuke 4.0.3 ... There have been changes in The Active Directory Project ? Exists an official documentation (install, setting, bugs, etc.) for this Project ? Because exists many information but is disorganized. It's very important for me.

Thanks.

Where is it?

I don't see the files under project downloads. where are is it?

Carlos K.

Need directions on how to setup AD authentication on DNN 4.0.3

I'm looking for directions on how to setup AD authentication on DNN 4.0.3. Can someone please help? Thanks!

Re: Update TTT.Authentication module with core Authentication

Here's how I got AD authentication to work in 4.0.3. It's a bit roundabout (Heck, it's a LOT roundabout!), but it worked for me....
1. For a fresh install, just go to the next step. If it's an upgrade, follow Tam Tran's instructions about the database entry, and the file deletion post above. Ignore the rest.
2. In IIS, open Properties on the web site or Virtual Directory > Directory Security tab > Edit button. Uncheck "Anonymous access" and "OK" your way out.
3. In Web.config, comment OUT the Windows Authentication block. Uncomment the Forms Authentication block.
4. Uncomment the "Authentication" item under .
5. Log in with admin account.
6. Go to Admin > Authentication.
7. Check "Windows Authentication?"
8. Check "Synchronize Role?" if you want AD groups sync'ed. (Don't ask me if this doesn't work. Report it as a bug to Tam Tran.)
9. Leave "Provider:" at the default. There's normally only one choice, anyway.
10. Choose "Authentication Type." "Delegation" is a good choice in most cases.
11. "Root Domain:" If you want to authenticate and get groups from the Root forest, then leave this blank. Otherwise, enter the LDAP path to your desired AD tree. Use this format: "LDAP://dc=com,dc=this,dc=that." Using "LDAP://" in the entry overcomes a bug that exists.
12. In most circumstances, you can leave "User Name" and "Password" and "Confirm Password" blank. These are supposed to be for an account that has "Read" access to the active directory. In most cases, EVERY account has read access. So leaving these blank will cause DNN to use your domain account to read the directory.
13. Click "Update." You will get an error message at the next screen. That's OK. Your entries just went into the ModuleSettings table of the database.
14. Log out, and close the browser.
15. Open Web.config, and uncomment the Windows Authentication block. Comment OUT the Forms Authentication block.
16. Save web.config.
17. Open a browser and point it at the site. You should see that the "Login" link says "Logout." This indicates that you were automatically logged in using your AD account. You won't be able to do anything here but browse public pages. But in the background, a user account was created for you, like "domain\username."
18. Close the browser.
19. Open web.config. Disable Windows Authentication and enable Forms Authentication. Save web.config.
20. Open a browser and point it at the site. Log in as Admin.
21. Go to Admin > User Accounts. Click the "all" link. You should see your "domain\username" account in the list.
22. Click the pencil next to that account.
23. Click "Manage Roles for this User."
24. Add this user account to the "Administrators" Role.
25. Log out, and close the browser.
26. Open web.cofig. Last time, I promise. Enable Windows Authentication and disable Forms Authentication. Save web.config.
27. Open a browser and point it at the site. Now you should not only see "Logout" at the Login link, but you should also be able to use the "Admin" menu.

Whenever a user connects to the site, you can now add them to whatever local DNN Role you want to create. If the "Synchronize Roles" feature worked, you should be able to assign AD groups to Roles, too.

Re: Update TTT.Authentication module with core Authentication

For item 4, it should say--
4. Uncomment the "Authentication" item under "httpModules."

Re: Update TTT.Authentication module with core Authentication

There has to be an easier way to get the AD groups sync'ed!

Windows authentication without Active Directory

Hi

Any chance you could shed some light on my forum query please?

http://www.dotnetnuke.com/Community/ForumsDotNetNuke/tabid/795/forumid/110/threadid/41666/scope/posts/Default.aspx

I want to extend the DNN 3.22 code to allow the site to determine the windows logon id of the person logged on and then look this up against the user database table to determine the access permissions it has to give the correct security access.

I do not want to use Active directory windows authentication because my client is a huge corporate network and managing groups in the ACL via helpdesk is a nightmare.

So I want to identify the users by their logon but intergrate that with DNN user table. So I can apply security levels through the admin website.

This is how I have developed corporate websites before and how I would like to amend DNN..

Does anyone have any experience of this and can offer advice? It may also prove to be a good way for DNN to develop in the future..

Regards

Steve

Re: Update TTT.Authentication module with core Authentication

Sorry if i missed it, but can anyone point me to a download location for the latest version of the project?

Thanks!

Re: Update TTT.Authentication module with core Authentication

Hi,
I have a question, I had installed the ADSI module and it work fine, but how can set the dnn users with role for manage the portal navigation? I must use another module? If yes, which module is better?
Thanks,
Simone

Re: Update TTT.Authentication module with core Authentication

Where is the download ? does it work fully with 4.3.1 ?

Re: Update TTT.Authentication module with core Authentication

I have had some progress working with AD and windows authentication.

However, I have a really strange issue, keep in mind - what I have will work but I would like to see if smooth out the bumps and my real goal of pass through windows authentication.
OK here is the issue -
When I - Open Web.config, and uncomment the Windows Authentication block and then comment OUT the Forms Authentication block. IE or any browser will not open the my dotnetnuke (4.3.2)website, the progress/status bar on the browser blinks like crazy - and never times out. I have let this run overnight - and not data is ever returned from the server.

Now, when I use forms authentication (in web.config) and IIS windows intergrated security - a domain user may see the default login page, login to dotnetnuke with his/her network username/password and this info in added to dotnetnukes user tables in the site's SQL database. Then this user's roles can be managed.

Another thing to mention - the user is added to the user table as user@domainname.com not as reported in other posts on this site DOMAIN/username.

I was hoping to use windows authetication, where the user did not have to "login" and his/her creds are passed through.

Have I read too much into the power of this module ???

Re: Update TTT.Authentication module with core Authentication

You don't download this project. It is included in the source.

Re: Update TTT.Authentication module with core Authentication

You don't need to install anything to get this working, just uncomment the portions of the config file indicated in the excellent instructions above.

Re: Update TTT.Authentication module with core Authentication

hi,
I can get this to work locally but when I try to access the website from a remote PC I get a 403 http error, what have I missed?