Howdy folks! This would be my first post. I can't seem to move forward with my current project. In version 2.1.2 and 3.0.7 of DNN I was able to access the Global.asax.vb and change the Authenticate_Request event so that users would be created & validated using
Windows Authentication (used some simple code to do this). With version 3.0.11 however, that all seems to have moved. Where is all this validation (or code) living with this new version? Any help would be most welcome! Thanks in advance, EnriqueL
We ran into the same problem. But, 3.0.11 basically eliminated the need for us to make any core changes. We are now looking and testing the following approach: Since 2.1.2 would crash if WIA was turned on and the user did not exist we wrote code, same as you,
to create the user. They would be dumped to the Home page and could see anything that was general information. We then add new users to specific roles based on existing business rules and requests from various group/departments. DNN3.0.11 allows WIA to be
turned on but does not crash if an account does not exist. The user gets dumped to the Home page and can see general information. Because of our security environment we do not want anything to happen "automatically". We also do not want to modify the core
and we do not want DNN3.0 to crash on a non-existant user. From our initial tests we think the current implementation will meet our needs without the coming AD code from Tamm. We are implementing the "Splash page" and using "out of the box" features to accomplish
our goal. Now to actually answer you question. The logic has moved to HttpModules/DNNMemebership/DNNMembershipModule.vb. At least that is what we have been able to determine. It is not as easy to understand as the DNN2.1.2 code, which is why we changed our
strategy. That's our story anyway. Hope it at least gives some information.... mikez
Allen, If you are referring to DNN2.1.2 code here is a link to a message I posted awhile back. It contains all the code. We have no code for DNN3.0.11. Our intent is to not have to write anything to modify the core.
See this link mikez
Automatically adding users under 3.0.x is a little more difficult. It should become a lot easier when 3.0 is released. One of the core members (TAMM) will be releasing his Active Directory module. Not sure of the exact features but it is supposed to support
both WIA and Forms authentication. WIA is really intended, IMHO, as an intranet solution. Because most network administrators need to know who/what/where they usually do not want anything to happen with regards to user accounts automatically. But, if the account
exists, the user is passed right into DNN and would have access anything the account or role membership has been given access. mikez
I am having trouble with the last point you mention about if the user account exists. Is the account to be created with the domain in front of it or not. So if my windows authentication id is DOMAIN\myuserid Do I create an account with userid of: DOMAIN\myuserid
or just myuserid. Also are there length minimums on the user id field and how can I lower it? Thanks for any help you can give me. Have a great day.
Both DNN2.1.2 & DNN3.0.11 will authenticate with "DOMAIN\myuserid". Under DNN2.1.2 we modified the code to strip the domain name from the userid. This was done only because after authentication the username displays instead of the Firstname Lastname. DNN3.0.11
displays the user's "Firstname Lastname". Because of this there is really no need to strip the DOMAIN part of the username. The user will never see. For sites with multiple domains it would allow the same name to be used with each becoming a unique user. DOMAIN1\joe.user
DOMAIN2\joe.user According to the database tables DNN212_Users username = 100 chars DNN3.x_Users username = 100 chars aspnet_users username = 256 chars Not sure what you mean by lowering the minimum length. But, my first reaction would be to leave it alone...on
either version. mikez
Thanks for the info. I will wait for the TAMM add in; I liked the way it behaves in 2.1.2 especially allowing a Windows user to logout then login using Forms Authentication for administrative purposes.
Thanks for the help. I did get it working finally, must have been doing something else wrong since I thought I had tried the domain\userid before. The problem with the minimum length was I was getting a validation error on the userid field when I entered my
6 character id in the userid field without the domain. but since I need the domain it is a mute point for now. I also would like to see the new version by Tamm that will allow me to log in and log out. Thansk again for the help. Have a great day. Eh.
eleon33
Member
20 Points
4 Posts
Simple Windows Authentication, no more Authenticate_Request?
Mar 04, 2005 02:06 PM|LINK
http://www.zshoppes.com
mzns1
Participant
1025 Points
205 Posts
Re: Simple Windows Authentication, no more Authenticate_Request?
Mar 04, 2005 06:06 PM|LINK
AllegrettoA
Member
225 Points
45 Posts
Re: Simple Windows Authentication, no more Authenticate_Request?
Mar 04, 2005 08:22 PM|LINK
mzns1
Participant
1025 Points
205 Posts
Re: Simple Windows Authentication, no more Authenticate_Request?
Mar 04, 2005 11:05 PM|LINK
AllegrettoA
Member
225 Points
45 Posts
Re: Simple Windows Authentication, no more Authenticate_Request?
Mar 05, 2005 02:25 AM|LINK
mzns1
Participant
1025 Points
205 Posts
Re: Simple Windows Authentication, no more Authenticate_Request?
Mar 05, 2005 04:29 PM|LINK
CanadaBoy
Member
15 Points
3 Posts
Re: Simple Windows Authentication, no more Authenticate_Request?
Mar 05, 2005 07:13 PM|LINK
mzns1
Participant
1025 Points
205 Posts
Re: Simple Windows Authentication, no more Authenticate_Request?
Mar 05, 2005 09:49 PM|LINK
AllegrettoA
Member
225 Points
45 Posts
Re: Simple Windows Authentication, no more Authenticate_Request?
Mar 05, 2005 11:16 PM|LINK
CanadaBoy
Member
15 Points
3 Posts
Re: Simple Windows Authentication, no more Authenticate_Request?
Mar 07, 2005 06:02 PM|LINK