You need to Register for free and Login to post a message in the forum.

Forum

How to Limit Access to Administrator Modules in DotNetNuke 5 - issue 50
Last Post 2011-03-18 03:04 AM by Joseph Craig. 24 Replies.
Printer Friendly
  •  
  •  
  •  
  •  
  •  
Sort:
PrevPrev NextNext
You are not authorized to post a reply.
Page 1 of 212 > >>
Author Messages
Lee SykesUser is Offline
DNN Creative Staff
Nuke Master VI
Nuke Master VI
Posts:4945
Avatar

--
2009-11-02 12:42 PM
    Add any comments or questions regarding the How to Limit Access to Administrator Modules in DotNetNuke 5  tutorial from Issue 50


    Lee Sykes
    Site Administrator
    Subscribe to the website : DotNetNuke Video Tutorials : The Skinning Toolkit : DotNetNuke Podcasts

    Twitter: www.twitter.com/DNNCreative

    Lee Sykes's Facebook Profile
    Bart A ZoniUser is Offline
    Posts:10

    --
    2009-11-03 10:00 PM
    If you give the Member Of Staff access to the Security Rolls module, how do you prevent that user to assign himself to the Administrator Role, thereby not limiting him to only the modules you put under the Staff page?


    Joseph CraigUser is Offline
    DNN Creative Support
    Nuke Master VI
    Nuke Master VI
    Posts:9299
    Avatar

    --
    2009-11-04 10:31 AM
    Obviously, you don't! 

    Lee's tutorial was aimed at showing HOW to provide partial access to administrative tools.  You should not think of this as a reason that you SHOULD do it.  In the case that you identified, there is a "security issue."



    Joe Craig, DNN Creative Support

    Subscribe to DNNCreative
    I recommend PowerDNN for DotNetNuke Hosting.
    Bart A ZoniUser is Offline
    Posts:10

    --
    2009-11-04 11:51 AM
    I can see tremendous benefit to opening some of the admin tools to a "staff" member and have specific need for such a thing. This article was excellent in timing for me. I need to give File Manager capability to specific users. I also need to give a specified user the access to enroll new users and assign roles. But I can not allow this user to modify the site (pages, administrator). Is there a way to modify the standard security module to have a security module wherein the administrator role is not exposed for use? Or do you have any suggestion for handling this?


    KamaleshUser is Offline
    Nuker
    Nuker
    Posts:11

    --
    2009-11-04 02:54 PM
    Is it possible to limit the "user accounts" module to only see/update certain users (not all from the domain).


    Joseph CraigUser is Offline
    DNN Creative Support
    Nuke Master VI
    Nuke Master VI
    Posts:9299
    Avatar

    --
    2009-11-04 04:39 PM
    I don't think so.



    Joe Craig, DNN Creative Support

    Subscribe to DNNCreative
    I recommend PowerDNN for DotNetNuke Hosting.
    KamaleshUser is Offline
    Nuker
    Nuker
    Posts:11

    --
    2009-11-04 05:05 PM
    Okay, thanks. Its a very nice tutorial.

    do you know any custom module in the market which will allow to limit the "user accounts" update for non-admin user and modify/show only certain users?


    Lee SykesUser is Offline
    DNN Creative Staff
    Nuke Master VI
    Nuke Master VI
    Posts:4945
    Avatar

    --
    2009-11-06 08:18 PM
    Hello, I have not come across one, thanks,


    Lee Sykes
    Site Administrator
    Subscribe to the website : DotNetNuke Video Tutorials : The Skinning Toolkit : DotNetNuke Podcasts

    Twitter: www.twitter.com/DNNCreative

    Lee Sykes's Facebook Profile
    Beth LancasterUser is Offline
    Nuke Newbie
    Nuke Newbie
    Posts:3

    --
    2009-11-07 05:17 PM

    Lee

    Thanks for the tutorial.  I too was hoping you were going to show how to allow staff to add and edit a user profile but not give them full access to change profile properties and all the other functionality  in this module.   

    Maybe a good OWS tutorial.



    Lee SykesUser is Offline
    DNN Creative Staff
    Nuke Master VI
    Nuke Master VI
    Posts:4945
    Avatar

    --
    2009-11-12 01:48 PM
    Hello everyone,

    I just did some further testing following the questions here. I logged in as a member of staff security role to access the user accounts module and this did actually limit me to not have access to the administrators role.

    Because I am not an adminsitrator I can not assign the adminsitrator role to myself or any other user.


    Lee Sykes
    Site Administrator
    Subscribe to the website : DotNetNuke Video Tutorials : The Skinning Toolkit : DotNetNuke Podcasts

    Twitter: www.twitter.com/DNNCreative

    Lee Sykes's Facebook Profile
    Lee SykesUser is Offline
    DNN Creative Staff
    Nuke Master VI
    Nuke Master VI
    Posts:4945
    Avatar

    --
    2009-11-12 01:51 PM
    Looking closer into this, I also cannot actually edit the profile details for any other user.

    All I have access to do is search for users and add a new user.

    The only account I can view is my own staff user account and from there I do not have access to add the administrators role, I can just add the other security roles to my profile.

    Hope this clears up the questions, thanks,


    Lee Sykes
    Site Administrator
    Subscribe to the website : DotNetNuke Video Tutorials : The Skinning Toolkit : DotNetNuke Podcasts

    Twitter: www.twitter.com/DNNCreative

    Lee Sykes's Facebook Profile
    JudeJosephUser is Offline
    Nuke Newbie
    Nuke Newbie
    Posts:9

    --
    2009-11-13 01:15 PM
    Hi,

    I followed the tutorial and all seems well except that when I login with the user I gave access to the limited site menu, the user can access the newsletter but when accessing tabs from the SiteAdmin menu the following message comes up:

    Access Denied Either you are not currently logged in, or you do not have access to this content.

    I've checked permissions and all seems to be well. Why would the newsletter be accessible but not the tabs?


    Lee SykesUser is Offline
    DNN Creative Staff
    Nuke Master VI
    Nuke Master VI
    Posts:4945
    Avatar

    --
    2009-11-17 02:42 PM
    It could be worth re-watching the tutorial, certain modules need slightly different configurations.

    The tabs module, you need to set permissions for the actual page that the tabs module is added to, you'll need to set edit permissions for the page, rather than the module.

    Thanks,


    Lee Sykes
    Site Administrator
    Subscribe to the website : DotNetNuke Video Tutorials : The Skinning Toolkit : DotNetNuke Podcasts

    Twitter: www.twitter.com/DNNCreative

    Lee Sykes's Facebook Profile
    BarryUser is Offline
    Nuke Newbie
    Nuke Newbie
    Posts:2

    --
    2009-11-18 01:52 PM
    Hey Lee
    Bizaar thing..
    When I create the Staff page and insert 'Users and Roles' module onto the page my registration page appears.
    Clicking on the Staff page menu item returns the Registration page.

    When I first did this yesterday I didn't realize the switching going on and thinking I was editing the Staff page and noticing only the USER ACCOUNT sub-module inserted (again thinking I was editing the Staff page which apparently doesn't really exist as it turns out) and thinking 'well that's not right' and therefore deleting the USER ACCOUNT module (which is actually my active Registration page) in which to start again.

    After some 'head-scratching' and 'shoulder-shrugging' and reinstated the USER ACCOUNT module back into the Registration page and called it a night.

    Tried again this morning, deleted Staff page, created new Staff page, insert USERS and ROLES module and again the Registration page appears and now the Staff menu item directs to the Registration page....????

    Do I hear everyone running for the door??


    Lee SykesUser is Offline
    DNN Creative Staff
    Nuke Master VI
    Nuke Master VI
    Posts:4945
    Avatar

    --
    2009-11-30 11:15 AM
    Hello,

    I'm not sure I fully understand what is happening here. First question is what version of DotNetNuke are you using? When I created the tutorial it was done with 5.1.4, you will want to be using at least 5.1.4 or the latest version which is now 5.2


    Lee Sykes
    Site Administrator
    Subscribe to the website : DotNetNuke Video Tutorials : The Skinning Toolkit : DotNetNuke Podcasts

    Twitter: www.twitter.com/DNNCreative

    Lee Sykes's Facebook Profile
    spedUser is Offline
    Nuke Active Member
    Nuke Active Member
    Posts:29

    --
    2010-02-03 11:40 PM

    Hi,

     

    In the Page/Tabs module, it seems that when a ‘limited user/group’ creates a new page (Add New Page), that new pages cannot be created on the ‘top level’ hierarchy. Also, pages cannot be created below other ‘top level pages’ unless those ‘top level pages’ have Page Settings: Edit Page permissions enabled for the group or user.

    After clicking Add New Page, the Basic Settings page appears, but the only pages that are listed in Parent Page are the ones that have Page Settings: Edit Page permissions enabled (ie. Events page, Admin page - see attached screenshot) even though the site comprises of seven ‘top level’ pages.

     

    Is there any way around this without having to ‘open up’ all pages settings (Page Settings: Edit Page permissions enabled for group/user) I want to avoid opening up the Page permissions as this would also allow the Settings of the Modules on those pages to also be accessed by the user/group?


    For more info on module settings, refer to:
    www.dnncreative.com/Forum/tabid/88/forumid/1/tpage/1/view/topic/postid/22400/Default.aspx

    “Page Settings: Do not give anyone edit page permissions or deny permissions
    Announcement module settings: give edit permissions just to Content Managers

    This will give them access to add announcements and that's all.

    If you give a user edit permissions to a page it opens up more settings for them”

     

    Thank you


    123403644371.gif

    Lee SykesUser is Offline
    DNN Creative Staff
    Nuke Master VI
    Nuke Master VI
    Posts:4945
    Avatar

    --
    2010-02-05 07:48 PM
    I'm not sure I fully follow what you are saying here, but if you are limiting users to just the admin / page/tabs module - try creating a new page in the root of the menu that is just for your limited admin users.

    Then add the tabs module to that page and see if it now allows them to add pages where you require.


    Lee Sykes
    Site Administrator
    Subscribe to the website : DotNetNuke Video Tutorials : The Skinning Toolkit : DotNetNuke Podcasts

    Twitter: www.twitter.com/DNNCreative

    Lee Sykes's Facebook Profile
    spedUser is Offline
    Nuke Active Member
    Nuke Active Member
    Posts:29

    --
    2010-02-07 11:30 PM

    I have tested what you recommended but what I’m trying to achieve still doesn’t work.

     

    I am trying to allow a ‘limited group’ (non Admin group) to add pages the website - add ‘top level pages’ and also ‘sub-level pages’, but also without having access to Module settings.

     

    The limited group is labelled “Content Managers”.

    Pages within the website do not have Page Settings: Edit Page permissions enabled for the Content Managers group. This is so that the Modules within pages can be limited for the Content Managers group – so Content Managers cannot Edit the Module settings – only add content to the modules.

     

    Refer to screenshot in previous post: When a member of the limited group (Content Managers) creates a new page; after clicking Add New Page, the Basic Settings page appears, but pages are not listed in Parent Page dropdown list and therefore ‘top level pages’ and ‘sub-level pages’ pages cannot be added.

    The only way for pages to be listed in the dropdown list is to have Page Settings: Edit Page permissions enabled for Content Managers (ie. Events page, Admin page have permissions enabled so they appear in the list – all other pages do not).

     

    The limited group (Content Managers) cannot add pages to the site unless Page Settings: Edit Page permissions is enabled for pages – this would therefore open up access to the Module Settings on the pages which we are trying to avoid.

     

    Is there any way around this, without allowing all pages to have Page Settings: Edit Page permissions enabled (for the Content Manages group). I want Content Mangers to be able to add new pages, without allowing them to Edit module settings?

     

     


    More info:

    Enabling pages with Page Settings: Edit Page permissions for the Content Mangers group opens up more settings for them and subsequently allows the Content Managers to Edit module settings; which we are trying to avoid. Giving Content Mangers ‘Edit Permissions’ within the Module itself (and not the Page) allows the Content Managers to only add content and not Edit Settings of the module.

    Page Settings: Do not give anyone edit page permissions or deny permissions
    Announcement module settings: give edit permissions just to Content Managers

    This will give them access to add announcements and that's all.

    If you give a user edit permissions to a page it opens up more settings for them”

     

    More info on Modules Settings topic: www.dnncreative.com/Forum/tabid/88/forumid/1/tpage/1/view/topic/postid/22400/Default.aspx

     




    JaumeUser is Offline
    Nuke Newbie
    Nuke Newbie
    Posts:1

    --
    2010-02-09 08:09 AM
    Hi,
    Did you manage to solve the problem? I'm facing the same issue: users with access to add and manage pages cannot create or assing pages to the parent ‘top level’ hierarchy. They only see already existing pages whichj they have edit access. It seems like they don't have access to the "...‘top level’ hierarchy page".

    The only way I've seen to solve this is to give them access to the Tabs module. With the page UP/DOWN arrows they can move the page to the root level.


    129121833471.png

    Lee SykesUser is Offline
    DNN Creative Staff
    Nuke Master VI
    Nuke Master VI
    Posts:4945
    Avatar

    --
    2010-02-09 04:43 PM
    Hello,

    Yes that's the only method I can see to make it work.

    Create a Tabs page - give edit permissions to  that page only
    A user can now create pages (just in that hierarchy)
    Once the page is created they can then move it where they require in the menu using the Tabs module

    This also limits them from having any other edit page / edit module permissions anywhere else

    Of course, one potential problem, is that when a user creates a page, they can assign their own security roles, so they could give themselves full edit permissions to any new page they create

    Thanks,


    Lee Sykes
    Site Administrator
    Subscribe to the website : DotNetNuke Video Tutorials : The Skinning Toolkit : DotNetNuke Podcasts

    Twitter: www.twitter.com/DNNCreative

    Lee Sykes's Facebook Profile
    You are not authorized to post a reply.
    Page 1 of 212 > >>


    Active Forums 4.3

    Latest Forum Posts

    Rename or move site from domain name to subdomain name by Bill Quinn
    Hi, I have an old DNN site on a a TLD like this: websitename.com I have created a portal on
    RE: Deploying dnn by Sameer
    Thanks joeseph glad with your answer it means i can use CE for my site if the traffic are not
    Unable to Create Skin Package by schilders
    Hi, I'm trying to create the skin package and manifest for my new skin. I created the new skin e
    RE: user adding images by Joseph Craig
    I think that you will need to go to the File Manager and give the user and/or security group file up
    RE: lightroom effect for skin by Joseph Craig
    There are modules available that do this. On the commercial side, I've used Mandeeps' Live Conten
    RE: Creating structured page content by Joseph Craig
    Take a look at Ventrian's News Articles module. While commercial, it has a very modest price! Th
    Creating structured page content by Stephen Bugden
    Hi, Can anyone recommend a module for creating and managing page content? The kind of thing I'
    lightroom effect for skin by everett31
    I’m looking for a way to add the lightbox effect to a skin file. I would like the end user to have
    RE: css3-mediaqueries.js and Dynamic Forms Crash Page in IE by WinXnet
    According to my web searching, @font-face references cause crashing in IE7 and IE8 with css3-mediaqu
    user adding images by rod lloyd
    I have set up permissions for certain users to edit a module, but when they log-on and enter Edit Co
    RE: Deploying dnn by Joseph Craig
    The free Community Edition of DotNetNuke is perfectly fine for creating "world class" websites. Whi
    RE: css3-mediaqueries.js and Dynamic Forms Crash Page in IE by WinXnet
    any idea what approach I should take - IE completely locks up. The only cause is the combo of the
    RE: css3-mediaqueries.js and Dynamic Forms Crash Page in IE by Joseph Craig
    If you're up to doing some debugging, you might be able to figure out where the problem lies. That'
    RE: Deploying dnn by Sameer
    Hi Joe Thanks for your reply i am planning to create my own DNN site so for that i have chec
    RE: css3-mediaqueries.js and Dynamic Forms Crash Page in IE by WinXnet
    Thanks for the response, but I was hoping it was something I could fix with some skin tweaks - one i
    RE: Changing Search text by Joseph Craig
    You will want to look here for references about the DotNetNuke skin objects. The document written b
    Changing Search text by Abraham Tameru
    Hi, Instead of having "Search" text near the search text box, I wanted to replace it by an image
    RE: Strange issue with file manager on sub domain (sperate portal) by Web Services
    Just sent it.
    RE: Not able to load my dotnetnuke website on Internet Explorer though it is working fine with other browsers by Joseph Craig
    Did you get this fixed? (Apologies for not getting to this sooner...)
    RE: Web Design Company London by Johnny Gregory
    Hello I am a Manager here at PowerDNN and I would like to see if you are still looking to get the wo
    You are not logged in.
    You must log in to access all 
    650+ videos, tutorials, podcasts, and more.
    RSS Feeds