Thanks for the clarification Dan. Now I can go to the Powers-That-Be and let them make the final decision though my gut feeling is that if we go ahead with this now before Security Groups sync with the AD it'll come back and bite me in the butt later (because I'm the one that's going to have to fix it).

Good luck, I find that Tam hardly ever responds on the forums.

djbaldwin wrote:

DanBall wrote: Now, if I can figure out how to redirect users to different start pages depending if they are Internet or Intranet, I'll have most of the small quirks worked out.... LOGON_USER will give you the NT Account the user is logged into. Response.Redirect(iif(Request.ServerVariables("LOGON_USER")="", "Internet.aspx", "Intranet.aspx")) I hope this is of some help to you.

It might if I could figure out how to use it... *grin*  Is this something I can put in at the ascx or aspx level?  I don't have any way to compile source code here, not to mention I haven't taught myself .Net programming yet.

JWise72 wrote:

Good luck, I find that Tam hardly ever responds on the forums.

In forum communications, the forum signal-to-noise ratio, often written FS/N or FSNR, is a measure of signal (post quality) relative to background noise (work). The ratio is usually measured in decihillbillies. (dB). If the incoming signal strength in microposts is V_s, and the noise level, also in microposts, is V_n, then the forum signal-to-noise ratio, FS/N or FSN, in decihillbillies is given by the formula FS/N = 20 log₁₀(V_s/V_n)

Ideally, V_s is greater than V_n, so S/N is positive. As an example, suppose that V_s = 10.0 microposts and V_n = 1.00 micropost Then S/N = 20 log₁₀(10.0) = 20.0 dB which results in the signal being clearly readable. If the signal is much weaker but still above the noise -- say 20 microposts in as many days—then FS/N = 20 log₁₀(1.30) = 2.28 dB which is a marginal situation where there might be some reduction in response under these conditions.

If V_s is less than V_n, then FS/N is negative. In this type of situation, reliable communication is generally not possible unless steps are taken to increase the post quality level and/or decrease the noise level at the destination (receiver).

Forum participants always strive to maximize the FS/N ratio, although negative posters create a less than magnetic effort by bombarding the crowd with demanding posts. This repetitive noise is balanced by ignoring the data requests, thereby improving the content and throughput.

ROTFL!!

Although if we are talking in decibawls, the lowder is not always better.

Well put Daniel.

Here Here.  Tired of the negative.  It is difficult if not foolish of the wise to criticize the efforts of a volunteer freely giving to the community of his time, skills and experience.  There should be shame and question (and hopefully introspection) of those who would attempt to level such criticism

sconard wrote:

There should be shame and question (and hopefully introspection) of those who would attempt to level such criticism

level and such are transposed. There is truth in any humor.

Let's get back to collaborating with our 198,393 or so registered users and conquer the planet with our DotNetNukin' efforts!!

Seeing some days of dormancy I thought I would chime in to see if anyone has some suggestions/solutions for the following...
I am using Tam's Auth tools for a company Intranet.  They are working fine in my testing stage but for them to be perfected I need at least two things to happen: 1) I am only getting the login to work with domain\username.  I only have one domain and would prefer to "tack on" the domain so that the user doesn't have to add it.  2) I am wanting to pass on the logged credentials to other modules I will work with.  Any ideas on an easy way to do that?  Does anyone know a way to pass the creditials safely to a link of OWA to have it authenticate automatically?

I have scoured these lists looking for my answers and not found what I've need.  So if I have been repetitive at least point me in the right direction.  Thanks in advance.

mcoulter wrote:

Seeing some days of dormancy I thought I would chime in to see if anyone has some suggestions/solutions for the following... I am using Tam's Auth tools for a company Intranet.  They are working fine in my testing stage but for them to be perfected I need at least two things to happen: 1) I am only getting the login to work with domain\username.  I only have one domain and would prefer to "tack on" the domain so that the user doesn't have to add it.  2) I am wanting to pass on the logged credentials to other modules I will work with.  Any ideas on an easy way to do that?  Does anyone know a way to pass the creditials safely to a link of OWA to have it authenticate automatically? I have scoured these lists looking for my answers and not found what I've need.  So if I have been repetitive at least point me in the right direction.  Thanks in advance.

1. No, sorry, the current incarnation of this module doesn't support.  It is rumored to be in the next release...

2. Create a DNN Security Role with the same name as an AD group the user is in.  Then, when new users log in, they're automatically part of this Security Role, and you can use this to restrict access to modules. Note: The Authentication module (current version) will ONLY populate those Security Roles for new users, it will not syncronize the group membership after the account already exists.

3.  No, you cannot pass logon credentials from DNN to OWA...  But, if you include the URL of the OWA in your "Local Intranet" group within IE it will log onto OWA without prompting.  Of course, that only applies to "Intranet" users...

To help answer,

1) I don't think there is a way to have them tack on a domain in the front.  What I have done for our intranet users is place the site in the
trusted hosts list in Intenet Explorer and it passes the credentials through without any users needing to enter a username/password.

2) Once authenticated, you can work with the user like any other local user for authentication in modules or pages. 
Most of my pages are external aspx pages hooked in from an IFRAME module modification of the Links module I wrote, however I reference the dotnetnuke dll and use the authentication. one of the things I use most is:
Dim WebUser As DotNetNuke.Entities.Users.UserInfo = DotNetNuke.Entities.Users.UserController.GetCurrentUserInfo
then you can reference the WebUser object to grab user information, such as email address in WebUser.membership.email.

As for passing credentials to OWA,that's Outlook Web Access right?  If the OWA site is a trusted site, it should pick up the AD Authenticaion is that is the method you use, other than that passing on query string. but it has to be something that OWA can interpret on its end.

Nathan

Thanks for the quick response Nathan. 

One thing that I probably should have mentioned is that I really want this to work as an Extranet as well.  So I am trying to capture the authentication from the login (Tam's login module) since I want it to operate remotely from the network and domain.  An example of something I would like to authenticate is a WebDav page that we use for a "briefcase/backup" solution.  I would like for users to log into DNN and then hit a link (or IFrame) that would go directly to their backup folder without having to reauthenticate, which is the current scenerio.

Back to the hidden domain question, is there a way to capture the username from Tam's Authentication Login Page, set a variable up, and tack the domain\+username together and pass that on during the submission? 

Regardless I will play with the other ideas Nathan has shared.  Thanks again.

I have the Auth Module running in production (Intranet only).  It works great for some but for some users they get logged off randomly - then if you clear out the cookies it works again.  Has anyone else experienced this issue? 

A more severe case is that some users are getting logged off everytime when clicking on certain page links. I know what you are thinking- the security is not set up correctly - but I can assure you that is not the issue.

Any ideas or suggestions would be helpful!    Thanks in advance 

UPDATE:  See the 2nd post after this for the answer!

NOTE: Please NO negative posts about this module (you know who you are) - I need constuctive help only! 

This has been a gremlin for a while and there are other threads on the subject, but the most common issue is child portals and/or accessing an .aspx page that is not part of the portal.

FYI: http://forums.asp.net/567799/ShowPost.aspx

I honestly don't know if this problem has been resolved in 3.1.1.

Thank djbaldwin for your ideas!   It is a child portal and I have ran into .aspx/.asmx issue before when building my module, but I am 99% sure I am not calling a .aspx/.asmx file but it is a good point to check.

I did notice though that the page it was always blowing on for some indivduals has a client side Javascript check before the postback. I took it out for now and am having the users who has the problem test again.
UPDATE: The javascript is not the problem but I did find out that the users who are having the logout issue have recently had their computer rebuilt- If I find out the cause I will post it.

UPDATE 2: Djbaldwin you know how I said 99% sure- well the 1% bit me.  I was using a pop up calendar date chooser on some of the pages and it was the problem. All I had to do was send in PortalID=Num and the problem was solved.   The reason this one stumped me because it seemed random - when in reality it was the fact that some users used the calendar to choose a data and some just typed it in.  Thanks for help - the module has been working great in a production environment for a month now!