Products

Evoq Content Overview Content Creation Workflow Asset Management Mobile Responsive Personalization Content Analytics SEO Integrations Security Website PerformanceEvoq Engage Overview Community Management  Dashboard  Analytics  Member Profile Gamification Advocate Marketing Community Engagement  Ideas  Answers  Discussions  Groups  Wikis  Events Mobile ReadyDNN Support PackagesEvoq: CMS FeaturesEvoq OnDemandCompare DNN's CMS Products

Solutions

Content Management SystemMulti-Channel PublishingDigital MarketingOnline Community ManagementIntranet Software SolutionOur CustomersPrime

Resources

Test DrivesSchedule A DemoDocumentation CenterWebinarsWhite PapersProduct ManualsRequest PricingData SheetsCase StudiesEvoq Preferred Products Content Management Ecommerce Forms Identity Management and Authentication Site Management Social Themes

Partners

DNN Partners Partner Directory Become a DNN Partner Partner Program Overview  Hosting  Implementation  ISV  Training  Competencies

Community

Participate Ask a Question Forums Community Showcase DNN MVP  Program Overview  Lifetime MVPs  Honorary MVPs Subscribe to DNN Digest Advisory Groups  Awareness Advisory Group  Developer Advisory Group  Partner Advisory Group  Technology Advisory GroupLearn Documentation Wiki Community Blog Video Library Project History Development RoadmapDownload DNN Store Language Packs Manuals Nightly BuildsSecurity Policies Security Center

Blog

About

News Press Releases News Coverage Press KitCareersContact DNN

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
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Extending the logon page.Extending the logon page.
Previous
 
Next
New Post
10/30/2006 12:16 AM
 
Scott Cable

Joined: 12/12/2004
Posts: 8
Our company is in the exploratory stages of a new portal project. One of the requirements will be for claims based (dual factor) authentication. This is where in addition to something the user knows (password) he/she also provides something based on their location (possibly swipe card/rotating password etc etc).

The exact mechansim for this hasn't been fully specced yet but we realise that we'll need to provide this extra data to the logon server for authentication. This additional data would not be seen by the user so there is no requirement to display it.

Is it possible to extend the DNN Logon page ? Or are we looking at writing a logon module using the same ASP 2.0 membership class and somehow using this instead of the DNN page/module ?

Thanks.
Scott
 
New Post
10/30/2006 9:19 AM
 
Craig Walker


medfluent.net
Joined: 7/12/2004
Posts: 240
Most dual factor methods need an authentication server.  Because many times passwords rotate, it would be difficult to use built-in DNN authentication.  That shouldn't stop you from using DNN as your portal framework, though.  You will need a custom authentication solution, but DNN makes this easy to implement (just swap out the provider).  I would treak authentication as a totally separate project.  Figure out how you want to handle that and then get it integrated with DNN.  I have one installation using an enterprise single signon authentication provider.  All we had to do was setup IIS to always require authentication (using an ISAPI filter) and on any page request the user is asked to authenticate (if they haven't already done so).  The user gets sent to the authentication server, that does it's thing and spits back user information.  This is nice because you can have your authentication server return a lot of user information (including custom fields).  Then all you need to do is write a DNN httpmodule to handle the portal login.  That will take a little code, but basically you look to see if the user is already registered, if so, update the profile and let them in, if not, create a new user and profile before letting them in.  It's really not that complicated.  You wouldn't ever user the built-in DNN login or registration pages, but you could use everything else.
 
New Post
10/31/2006 2:37 PM
 
Matthew Christenson

Joined: 10/19/2006
Posts: 164

scottcable wrote
Our company is in the exploratory stages of a new portal project. One of the requirements will be for claims based (dual factor) authentication. This is where in addition to something the user knows (password) he/she also provides something based on their location (possibly swipe card/rotating password etc etc).

The exact mechansim for this hasn't been fully specced yet but we realise that we'll need to provide this extra data to the logon server for authentication. This additional data would not be seen by the user so there is no requirement to display it.

Is it possible to extend the DNN Logon page ? Or are we looking at writing a logon module using the same ASP 2.0 membership class and somehow using this instead of the DNN page/module ?

Thanks.
Scott





 

I've done just what you're talking about...  I'm still pre-production and have a small handful of things i need to fix before I go live (like re-adding support for localization, fixing admin user management pages, etc...).  I went this route because I needed an advanced single sign-on service with what I coudl best describe as "roaming profile subscriptions".

All in all I've spent about 100 hours digging around in the authentication/authorization/userroles/profiles sections of the code in order to figure out what it's doing - identify what I need to be done, and come up with a solid plan for implementation.  I expect to have to spend another 20-40 before I go live with everything so that it's a "fool proof" implementation.

All in all I think it's worth the time; DotNotNuke has a TON of work in other areas that I wouldn't even bother adding to my project if it was going to cost me extra time and money - it's a significant value adder to any website...  Plus it forces a structure that has a little stricter requirements than a plain old ASP.NET application would; this "architecture assistance" can save a ton of time and end up with better more easily managed code...  But in order to really benefit from it you should expect to spend a few hundred hours learning what the DotNetNuke framework is doing and why.

I've made this initial investment and I am glad that I did; but I also have very advanced requirements when compaired to some others.

Matt Christenson

www.RealSkydiving.com
 
 Page 1 of 1
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Extending the logon page.Extending the logon page.


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