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

HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...DNN Security Issue?DNN Security Issue?
Previous
 
Next
New Post
2/18/2009 5:31 AM
 

 Hi everyone,

I use on my DNN website both the DNN Authentication and Windows Authentication. Windows Aut is used just for a part of the website (administration) which is a module and several "external -> not DNN" aspx pages. This module has it's own DNN page which is visible to everyone but is set in IIS to be visible just for windows authenticated users. When i'm accesing the page via the complete URL (www.mydomain.com/DesktopModules/ ..etc) it requests the username and password -> ok BUT when I access the page from DNN (www.mydomain.com/tabid/100/Default.aspx) it requests the username and password but if I click "cancel" a few times the page and the module are displayed!

I see this as a bug 'cause DNN should check if the user has the right permission. Is there a workaround or somenthing like this?

thanks

Victor

 

P.S: i do not use the dnn aut for administration part for 2 reasons: 1. this cannot protect the external pages; 2. the control panel with Edit/View Mode is annoying.

 
New Post
2/18/2009 6:53 AM
 

you cannot  protect specific dnn "pages" using windows authentication, simply because there is only one DNN page: default.aspx. In order to protect content with windows authentication you would have to protect the full application.

It is a bug alright, but it is a bug in your reasoning :) The proper workaround would be to create a proper admin module and to not rely on windows authentication.

(btw: you can use dnn authentication to protect your external aspx files, you can alsways check if a user is an admin user or not. ALL aspx end points in the application will be authenticated by dnn authentication and you will have a user available in the code behind of the aspx page. )


Erik van Ballegoij, Former DNN Corp. Employee and DNN Expert

DNN Blog | Twitter: @erikvb | LinkedIn: Erik van Ballegoij on LinkedIn

 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...DNN Security Issue?DNN Security Issue?


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