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

HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Custom Permissions and Module ControlTypeCustom Permissions and Module ControlType
Previous
 
Next
New Post
1/4/2007 10:31 AM
 

For a prayer request/update module (which is much like a highly specialized forum) I have created two custom permissions with PermissionKeys of POST and MODERATE. Although the addition of the custom permissions (in the implementation of  IUpgradable.UpgradeModule) works fine as does the testing of whether the user has one of these custom permissions, I am wondering what values to provide for ControlType in the module's .dnn file.  If, for example a module control would require that the user have MODERATE permission, I can either give the moderator's role BOTH EDIT and MODERATE permission on the module and set the ControlType to Edit OR give the moderator's role only MODERATE permission on the module and set the ControlType to View.  If I set the ControlType to Edit and give the moderator's role only MODERATE permission, the module loading code in Skin.vb recognizes that the user does not have EDIT permission on the module and redirects to the AccessDeniedUrl before my custom code in the module control's page load has a chance to check for MODERATE permission.

So, I'm wondering:

1. Is it better (safer) to set the module definition's ControlType to Edit and provide instructions to administrators of the module that they will need to give the moderators role(s) both EDIT and MODERATE permissions or set the ControlType to View in which case the moderators role(s) will need only MODERATE permission? I'm leaning toward doing the latter to simplify configuring permissions and feel relatively safe as the module control's page load first checks whether the user has MODERATE module permission and immediately redirects to AccessDeniedUrl if he/she does not.

2. Has any consideration at the core level been given to extending a module control's ControlType to include any custom permissions that the module creates? It would be great to be able to set the ControlType in the .dnn file to "MODERATE" for example. Unfortunately, his would require major changes to way that the ControlType is both stored and tested against the SecurityAccessLevel enumeration.


Bill, WESNet Designs
Team Lead - DotNetNuke Gallery Module Project (Not Actively Being Developed)
Extensions Forge Projects . . .
Current: UserExport, ContentDeJour, ePrayer, DNN NewsTicker, By Invitation
Coming Soon: FRBO-For Rent By Owner
 
New Post
1/5/2007 2:43 PM
 

to 1)

Inside UDT we have changed the Control Type of the Edit Dialog from EDIT to VIEW. During page load the custom permissions get checked.

to 2)

This idea was not discussed before. I would suggest entering an enhancement issue at support.dotnetnuke.com inside the public dnn area.

 
New Post
12/20/2007 6:24 PM
 

I was wondering if an enhancement issue was ever entered in support.dotnetnuke.com for this - didn't want to create a duplicate issue if possible. I wasn't able to find any issues with "custom permisson" as keywords when I searched...

 
Previous
 
Next
HomeHomeArchived Discus...Archived Discus...Developing Under Previous Versions of .NETDeveloping Under Previous Versions of .NETASP.Net 2.0ASP.Net 2.0Custom Permissions and Module ControlTypeCustom Permissions and Module ControlType


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