Welcome to Strong Coders Community Sign in | Join | Help

Blog ( Of Ryan Olshan)

News

  • About Ryan Olshan

    Join StrongTypes - Free Generics Help By Email
    Join StrongTypes

    Community Credit Winner

    View my MVP profile

    The posts on this weblog are provided "as is" with no warranties and confer no rights. The opinions expressed herin are my own personal opinions and do not represent my employer's view in any way.

    Subscribe to Rolog via My AOL
    Subscribe to Rolog via Bloglines


    Subscribe to Rolog via Feedburner

    Furl Rolog




    Subscribe to Rolog via Newsburst


    Subscribe to Rolog via Pluck

    Add Rolog to Technorati Favorites




    Thycotic Secret Server

.NET Websites

  • => StrongTypes.com <=
  • Community Credit
  • DotNetCharity.com
  • DotNetSlackers
  • EasyListBox
  • SystemNetMail.com
  • SystemWebMail.com

Blogroll

  • Alex Campbell
  • Carlos Magalhaes
  • Chris Taylor
  • Darren Neimke
  • David Betz
  • Eric Smith
  • Rob Caron
  • Rob Howard
  • Sam Gentile
  • Scott Guthrie
  • Scott Mitchell
  • Tess
  • Wesner Moise
  • Jason Alexander
  • Bill Ryan
  • Steve Smith
  • Sahil Malik
  • David Silverlight

Other Websites

  • 911 Pigeon Alert
  • Pacific Wildlife Project

Strong Coder Bloggers

  • Dean Fiala
  • Kevin Jones

Thycotic Bloggers

  • Bryant Smith
  • John Morales
  • Jonathan Cogley

Yahoo! Groups

  • => StrongTypes <=
  • AspNet2
  • AspNet20GridView
  • PayPalDevDotNet
  • RubyOnRails
  • VSTS

Tightenting Community Server Control Panel Security

By default, the web.config file of Community Server allows any registered user access to the Control Panel, including Setup.aspx and 2 pages hidden from the Control Panel UI that have functionality. To prevent registered users from accessing these files and the Control Panel, change web.config in /ControlPanel to the below. Before doing so, it's a good idea to create a role called ResourceOwner and assign it to all blog authors and file and photo gallery owners as the below change will not allow any of them access to modify their blogs and photo and file galleries since they aren't in the list of allowed roles that can access the Control Panel.

 

< configuration >

  < system.web >

    < authorization >

      < allow roles = " SystemAdministrator,BlogAdministrator,ForumsAdministrator,Moderator,GalleryAdministrator,FileAdministrator,ReaderAdministrator,MembershipAdministrator,ResourceOwner " />

      < deny users = " * " />

    authorization >

  system.web >

 

  < location path = " settings.aspx " >

    < system.web >

      < authorization >

        < allow roles = " SystemAdministrator " />

        < deny users = " * " />

      authorization >

    system.web >

  location >

 

  < location path = " Setup.aspx " >

    < system.web >

      < authorization >

        < allow roles = " SystemAdministrator,BlogAdministrator,ForumsAdministrator,GalleryAdministrator,FileAdministrator,ReaderAdministrator,MembershipAdministrator " />

        < deny users = " * " />

      authorization >

    system.web >

  location >

 

  < location path = " license.aspx " >

    < system.web >

      < authorization >

        < allow roles = " SystemAdministrator " />

        < deny users = " * " />

      authorization >

    system.web >

  location >

configuration >

Share this post: | bookmark it! | digg it! | reddit! | kick it! | live it!
Posted: Sunday, September 17, 2006 10:14 AMby Ryan Olshan
Filed under:

Comments

Dave Burke said:

Hey, Ryan! Thanks for this post. I wanted to link to it in today's Daily News but wanted to verify that all registered users had access to setup.aspx and the other items you mentioned before doing so. I'll ping you back on this as soon as I can get to it. Thanks again.
# September 21, 2006 11:36 AM
New Comments to this post are disabled