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...Best practice for protected module controlBest practice for protected module control
Previous
 
Next
New Post
2/4/2009 7:18 AM
 

Hi there,

I'm developing a module with one module control visible to a specific role only. Now I'm searching for a good/better/best solution.

#1: Login link inside view module control, like blog module does. Looks something like

Response.Redirect(Globals.NavigateURL("controlkey for protected module control", "ctl=login"));

Module control can be of type "View", but this isn't limited to the specific role. Therefore the module control is visible to all registered users.

#2: Add a separate module definition and set module control to type "Edit". Tab module has to be editable for specific role. It is guaranteed. that only users from the specific role can access thi module control. "Control Panel Security" should be "Page Editors". But what about security risk? The whole module is editable and not only the module control.

Any other solutions?

Best regards
Niklas

 
New Post
2/4/2009 9:36 AM
 

You could add your own security permissions (see this blog entry) and then inside your module check that they have the permissions you are after.  If they do, let them go to that module (you could even check that security and opt to show it in the module actions or not depending on their permission but you'd still want the control itself to verify they are in the role or not).

Seems like the best of both worlds in this regard -- you don't have to allow the whole module to be "Edit" by the security role you are targeting, you can tie your module down even further.


-- Jon Seeley
DotNetNuke Modules
Custom DotNetNuke and .NET Development
http://www.seeleyware.com
 
Previous
 
Next
HomeHomeOur CommunityOur CommunityGeneral Discuss...General Discuss...Best practice for protected module controlBest practice for protected module control


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