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...Module ForumsModule ForumsIFrameIFrameProblem with authorization section in web.configProblem with authorization section in web.config
Previous
 
Next
New Post
3/26/2010 4:44 PM
 

Hi sir ,

I am developing a web application using dnn 4.9 , i added a folder to my portal root which contains  .aspx pages  which will  be dispalyed in Iframe moduls

i want certain users and roles to access this folder  so i added a location section  in the web.config file as the following :

<location path="portals/0/(folder name)">
<system.web>
<authorization>
<allow users="(user name)"/>
<allow roles="(user name)"/>
<deny users="(role name)"/>
<deny roles="(role name)"/>
</authorization>
</system.web>
</location>


the problem is that  allow users and deny users elements works well but allow roles and deny roles elements donot work at all

so can you help me please ????

 
New Post
3/29/2010 2:59 PM
 

DNN Roles are not the same as the roles that are recognized by ASP.NET.  There is no out of the box way of doing this.


-Mitchel Sellers
Microsoft MVP, ASPInsider, DNN MVP
CEO/Director of Development - IowaComputerGurus Inc.
LinkedIn Profile

Visit mitchelsellers.com for my mostly DNN Blog and support forum.

Visit IowaComputerGurus.com for free DNN Modules, DNN Performance Tips, DNN Consulting Quotes, and DNN Technical Support Services
 
New Post
3/30/2010 4:12 AM
 

 

thank you Mitchel for reply
So  there is no way to go around this

ok now i will explain to you  my problem
the .aspx pages which i added to the folder will be displayed in iframe moduls, these pages must be viewed by certain users and roles , the problem is that if someone (like a hacker) knows the path of any of these pages he can browse them directly as a normal web page and not under dotnetnuke context or if he right click the iframe module he can also get the path of the page and browse it in the same way
the big problem is that the secuirty model of dotnetnuke works only with  pages which are saved in the database and not with static pages which i add to my web application

so i want to ensure that whenever someone browses any page in my web site ,he is doing that under the dotnetnuke context and preventing him from browsing the page directly by redirecting him to the home page or to an error page

i hope that everything is clear now

so how can i do that

 
New Post
4/4/2010 10:22 AM
 

 

ANY RESPONSE PLEASE ?????

 
New Post
4/4/2010 7:53 PM
 

 I can't think of any way that IFrame can help in achieving your goal - any parameter that will be passed using IFrame will be in a plain view.

You might want to look into using DotNetNuke authentication - may be you can include your pages within the website and extend some page from CDefault class - in either case, start looking at Authentication and Configuration forums. IFrame isn't your tool ...


Vitaly Kozadayev
Principal
Viva Portals, L.L.C.
 
Previous
 
Next
HomeHomeDNN Open Source...DNN Open Source...Module ForumsModule ForumsIFrameIFrameProblem with authorization section in web.configProblem with authorization section in web.config


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