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

HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationOnUserAuthenticated() -- am I missing something obvious?OnUserAuthenticated() -- am I missing something obvious?
Previous
 
Next
New Post
9/1/2009 6:39 PM
 

I want to put a mini 'login' module on several pages, so that users don't have to go to a special login page. I've created a class cloned from DotNetNuke.Modules.Admin.Authentication.Login (the default Login page), but since I haven't registered a handler for OnUserAuthenticate(), nothing happens.

The reason I'm asking in this forum is that it looks as if the OnUserAuthenticated() handler is created when the Authentication providers are enumerated, but what does that have to do with me? Is it going to take pages of code just to put up a simple login box?

 

 
New Post
9/2/2009 12:32 AM
 

 Why not just place the Account Login module on the pages that you want it on and set the viewing permissions to UnAuthenticated Users only?

 
New Post
9/2/2009 1:07 PM
 

Thanks for answering--I realize now my question is off-topic.

I will try what you suggest, but the layout of the Account Login module is all wrong for what I need. Maybe I can torture the css enough to make it work. (I don't want to change the source for the Account Login module itself if I can avoid it, because I use it [intact] on the 'real' Login page.)

Even so, I know this is going to come up again soon. For example, I want to send out an email containing a link which automatically logs the visitor into a special promotional account. Conceptually this is very simple, but once again: how can I programmatically tell DNN "This is user X whose password is Y, please log them in"?

Thanks again for your time.

 
New Post
9/2/2009 1:45 PM
 

In general are your users going to still login like a regular DNN user (username/password) or just clicking a link that logs them in as a generic user?

As for your original question. Even though you copied the Standard DNN login there's more to it than that. All of the Authentication providers are wrapped by the global DNN authentication. Without looking at your code or trying to step through it, I suspect this is where things are going sideways on you.

 

 

 
New Post
9/3/2009 1:58 AM
 

(Your questions have already been very clarifiying, thanks for sticking with me.)

So far, there will be three kinds of logins:

  • normal (username/password)
  • username/password, but must come from an associated IP block
  • automatic login (encrypted parameters in URL tell who they are)

The third group only get access to a subset of pages, and/or for a limited period of time (specific to the URL they present).

To make this concrete: we have an database for designers which aggregates information from manufacturers. Individuals pay to get access to this database. Schools pay for their students to have access (anyone from their IP block gets in). The manufacturers get free access to pages that let them check on their product info and edit their contact info. I don't want to force one-time visitors to create usernames and passwords just to see a handful of pages.

Still hoping there's a simple answer to my last question ("how can I programmatically tell DNN 'This is user X whose password is Y, please log them in'?").

 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Provider and Extension ForumsProvider and Extension ForumsAuthenticationAuthenticationOnUserAuthenticated() -- am I missing something obvious?OnUserAuthenticated() -- am I missing something obvious?


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